hborre posted at 6:21PM Sun, 25 October 2020 - #4402131

I can sympathize. I ran a render for almost 2 days before pulling the plug and accepting the results. Depending on what you are including in your scene, you may need to re-evaluate each prop and character for mesh density and texture resolution. Using a 4000 x 4000-pixel resolution on a mid- to far-scene object is a waste of computer resources. Great if you are rendering a closeup but needless if you are rendering a landscape. Reduce texture resolution, deconstruct high poly mesh objects, don't use SSS unless it's necessary, use bump or normal mapping instead of displacement, minimize the number of total pixels to achieve what you want, etc. There are many things that can be done pre-render but you will need to spend quite a bit of time tweaking and retexturing. Forget about using Queue Manager between machines for Superfly, it doesn't work and atm it is not supported except on the same computer as your Poser install.

I have adjusted my shaders as you suggested for a while now--unfortunately displacement is going to have to wait until Poser integrates the better sort that does not rely on mesh--but I did not think to reduce my texture resolution on the props that are farther away, so there are 4k textures on EVERYTHING in my scenes and I never reduce polys either. So I will try those things! Lately I've been abandoning the figure or prop textures right away and using 4k PBR texture sets on everything, and they look bomb, but that's also been contributing to my issue with rendering. I've already converted them all to jpegs since they usually come as pngs, and for some reason Poser utterly freaks out at pngs these days and changes their colors (maybe a memory issue). I didn't think of making them smaller! Thank you very much for the suggestion.