i have a problem here.
We are trying to render an image with 12k resolution, this file has a lot of geometries and spend a lot of RAM.
We bought a new computer with 128gb of RAM and 2 processors to save our render times but it dont solve this problem.
When the render starts, it consume around half of memory but the processors works on full capacity and stop on the initial passes. the hour count shows aways the same estimated time and the time used is aways growing up.
How can we fix this?
the processors works on full capacity and stop on the initial passes. the hour count shows aways the same estimated time and the time used is aways growing
I’m sorry. I think I explained it wrong. Let me try that again.
When I fire up the render in 12k it takes quite a lot of time to start rendering due to the displacement calculations. That’s OK and expected. It eats up quite a bit of the available RAM that I have in the system, but we don’t get any messages saying that we are runnning out of resources whatsoever.
Then it starts to render as expected but suddenly it stops refining the image. The last time we tried, it stopped on the 8th pass (from 120). Then even though the processors were fully in use, the elapsed time continues to run while the remainingn time freezes and we don’t go any further.
Are you also experiencing any freezes or crashes with this? Are you able to click “cancel” in the rendering dialog and the rendering stops, or do you have to force close Max?
Actually I had this problem when using displacement with 1px in the setup on 4K images. It takes some time until the process stops after you hit “stop” or “cancel”
I guess it take quite a lot of time to stop processing at 12K.
Tried rendering it in bucket mode, using the settings you suggested.
It started quite well and within one hour it started rendering. I could see that some of the small areas were not rendering, producing these black blocks spreaded out in the image. Got here this morning to see the render and once more the remaining hours was frozen while the elapsed kept running so it seems like the same problem happened again. (see screenshot attached)
I just clicked the CANCEL button but 3dsmax haven’t stopped the render yet. I will wait a few more minutes before trying to force quit it. I will update this thread soon.
And the CANCEL didn’t work. The funny thing is that when I forced quit the scene via Task Manager, 3ds max asked me if I wanted to save the file (?). Weird.
Is this also happening if you render a lower-resolution image?
Can you see if lowering “# of threads” in performance settings changes anything? (to -1 or -2, make sure you are not changing the # of threads for interactive rendering)
Please go to task manager and check:
-what is the process priority of 3dsmax.exe?
-are you able to change affinity of 3dsmax.exe?
