Long time lurker, first time poster... Have a couple odd questions

Hello,


I've owned CC3 (and CC2) and lurked in the forums for many years without ever signing up. I've always procrastinated about getting into it and really begin working on some of the projects. Now that I am more committed, I am planning to work on a fantasy campaign, a Star Wars campaign, and a Traveler campaign (plus a few others as the muse hits me).

I have some questions that I tried to look up but did have much luck in finding answers (also, part laziness on my part)

  1. Is there any documentation on application maximums for Fractal Terrain and CC3+?
    1. What is more important, Cores, Clock, or RAM?
    2. Are there application display maximums (like it doesn't play well above 4k resolution)
  2. How parallelized is FT3 and CC3+?


Comments

  • CC3+ is 32-bit software. It can only use 4GB of RAM. It is not coded to take much advantage of multiple cores either. Clock speed is probably the most important; however, it really is the RAM that limits things. I think FT is 64 bit and therefore does not have these limits. For whatever reason, the newer styles tend to have far fewer speed or rendering issues than older ones even with all of the sheet effects turned on. Older styles tend to do those more often with me.

    Since this is CAD, it uses an algorithm and each time it needs to redraw, it needs to recalculate things to render. So the CPU is the main things, not the GPU. I have not heard of any issues with 4k display resolutions and I see no reason why it would have any. Mine is UHD at 180 hz and it runs fine.

    I do not know what you mean by parallelized. FT and CC3 are different programs for different purposes. None of the things you do in CC3 is really in FT so it is very different commands. You can export FT to CC3 though.

    DVader
  • Parallelized = optimized for multiple cores. Example of multi thread optimization is breaking down a render into say layers and sections to optimize time to render if say it detects the system can handle 32 threads at once it can split up the work to reduce draw times... Lot's of ways to solution it based on type of work being done, and just interested in understanding some of the "under the hood" gears and gubbins to make sure that my next rig is going to run it well.

    Thank you for the response, that has given me some things to ponder about my next rig, once I get some experience with the UI I think i'm going to have a lot of fun.

Sign In or Register to comment.