Rendering Speed in DS 4.12 compared to DS4.14

kyoto kid

....yeah I see that a lot in MB specs where most of the listed memory speeds have "(OC) "after them.  I never bother with overclocking as I am not into games and it really doesn't help all that much for rendering.

Sadly DDR5 will not only be more pricey, but only be compatible with the newest CPUs which means W10. If I want ECC memory, I'll just get an existing MB that's compatible with it. 

Mark_e593e0a5

So far, I do not see much difference in render speed. I am using an iMac Pro, 10 Core Xeon, 128 GB memory, CPU render. I have to admitvthat 4.15 crashes more often than 4.12, especially when closing the app.

outrider42

The increase in speed that 4.14/4.15 offer is due to how Daz handles normal maps. If you look at the documentation notes for 4.14, one of the changes mentions that it made it more efficient. This note is rather cryptic, like Daz often is as a company, and makes no mention of rendering speed. But the evidence makes it clear they are tied to each other.

So that means the more normal maps you use in your scenes, the more of a difference you will see between 4.12 and 4.14 in render speed. If you use the HD addons for Daz Original characters, most of these by default will not load any normal maps. If by chance your scenes have no normal maps at all, then you not see any difference in render speed. Also, if you only CPU render, then you may not see a difference either. This change effects how normal maps are treated as they are converted to VRAM, so it makes sense that CPU rendering would not see any change. When you render on GPU, all the textures are converted into a compressed format for VRAM. But with CPU rendering there is no compression.

Perhaps some of the crashes we are getting are also a byproduct of this change, and Daz needs to streamline this process better. As I said, all my crashes only happen when I go to start a render. The first couple of steps will begin, but at the step just before memory is reported, the app will report a fatal error has happened and must close. So I really believe at this point all of these things are tied together.

But like I said before, just save frequently. Since these crashes only happen when starting a render, you can simply save before clicking the render button.

Since I built a new PC I have not yet run into this issue. But it was somewhat random and maybe I have just been lucky so far.

kyoto kid

...I've been making intermittent saves since 1.8  as I was working on a 32 bit notebook with 4 GB of DDR RAM and a duo core 1.6MHz processor..  Render crashes were the norm back then.as my ambitions were beginning to exceed the technology's capabilities, so I just got into the rhythm of saving before each render attempt which I've never broken from since.