Anyone else getting the render frame hanging right at the end, right when message window reports number of rays per pixel changed to 64 total number of samples 0…it hangs here and will not complete the frame.
This was using max 2016 on a bb render. I think I also had this happen with one of the stable 3.6 copies last week. I’ll try and get a test file to send to support when I have some time.
Hm, it is something that I havent seen so far.
Best,
Blago.
I’ll keep testing. Last week on the stable version, I simply cancelled the render and rendered again and it did not hang…that was for a 5 minute render though, so it was nothing. I thought it might get fixed so I didn’t say anything.
When I get some time I’ll try to put together a scene for you..if I can figure how to reproduce it.
Last week when it happened, it was not through bb.
One of my render nodes is randomly crashing, error with 3ds max…not sure yet what it is. I may have to jump back to 3.5 to get the current job done.
So far, 3.6 hybrid has worked well on 5 nodes, a 6th node crashes randomly and my ws hangs on render end and will not complete. I don’t have time to prepare a dump or send a file…I’ll try sometime though.
The vdenoise.exe works well with the frame offset.
ws still hangs on frame end when render outside bb using hybrid
Ok, I was able to reproduce with a reduced scene file and sent to support…tia.
Disabling “Low GPU thread priority” in V-Ray RT’s settings should stop the hanging at the end of the rendering process.
thanks, I’ll try that. Will you still work on a fix for this in the future so we can keep low gpu priority on?
Yes. This is a workaround until the fix is released.
Best,
Blago.