Tweet
I run into the open knife of having had a procedural mesh that caused a 128 GB Ram crash when rending.
The issue was simple: I have quite simple mesh, that had a mirror modifier and was deformed in a group. Now it had like 5 instances in the scene. Rendering frame 0-100 was not a big deal. But at frame 600-800 along motion blur in camera caused a heavy vrscene and the memory issue.
Its really not a big mesh, like a hundred polygons. So I wonder if that's all my fault.
After adding a freeze modifier, V-Ray worked again as expected. So it took my really long to find out, as the file was old and worked well with Modo render.
Now the question is: Could you do something to prevent this from happening? I mean if Modo can do that with freeze modifier in the stack then why can't V-Ray handle it?
I think this is really dead trap for every team work project.
The issue was simple: I have quite simple mesh, that had a mirror modifier and was deformed in a group. Now it had like 5 instances in the scene. Rendering frame 0-100 was not a big deal. But at frame 600-800 along motion blur in camera caused a heavy vrscene and the memory issue.
Its really not a big mesh, like a hundred polygons. So I wonder if that's all my fault.
After adding a freeze modifier, V-Ray worked again as expected. So it took my really long to find out, as the file was old and worked well with Modo render.
Now the question is: Could you do something to prevent this from happening? I mean if Modo can do that with freeze modifier in the stack then why can't V-Ray handle it?
I think this is really dead trap for every team work project.
Comment