I recently built a workstation with an RTX 4090 and started working with V-Ray GPU and Vantage. Unfortunately, the experience has been pretty frustrating. I’m running into a lot of strange bugs, crashes, and long parsing times. This time, my render get stuck at “Building dynamic mesh trees”. It seems to be in an infinite loop, switching between “Building dynamic mesh trees,” “Rendering image,” and then back to “Building dynamic mesh trees.” This happens very frequently.
V-Ray tab, Frame Buffer section. Set Post Effects rate to 0
Performance tab, Textures mode should be set to Full-Size, and Check Use System Memory for Textures option. No need for Compressed Textures with new V-Ray builds
Performance tab, Uncheck the C++/CPU device
Try to use the least amount of render elements. This affects performance considerably
Sent. Feel free to request more information if you need it. I’m really interested in seeing this solved.
Hi Bobby! Thanks for your suggestions! I’ll try some of them out in the meantime. My main goal, though, is to figure out the root cause of the issue—whether it’s hardware-related, a V-Ray bug, or something else. Any additional insights you might have on the cause would be very helpful.
No Alembics loaded with VRayProxy, right? If you Check Use Alembic Offset in these cases it will do what you described. (Uncheck it after checking it once to get the value and it works fine.)
Not sure this applies to you, but if you have a VRayProxy object that is loading an Alembic, and you have the checkbox set to use the Alembic offset (for the start frame) it will do something like what you described. Just pointing out a specific case that is in the bug database already. Sadly, Chaos doesn’t make the bug database public.
The issue appears to be quite specific, where the IPR enters an endless loop on the first run after opening the scene but works as expected once any changes are made to the render settings.
I’ve reported the matter to our developers for further investigation in our internal system (VMAX-13140).
In the meantime, please continue using the workaround: reset the render settings by switching the render engine to Arnold (or another option), then switch back to V-Ray GPU, and then attempt to render with the IPR.
Thank you for the update. Unfortunately, the suggested workaround only resolves the issue for the current session. Once I close and reopen 3ds Max, the problem reappears. Hope the devs can figure it out.
@AyrtonSenna Thanks for notifying us. Unfortunately, VMAX-13140 is still unresolved, and there are no updates here. If you like, you could submit a ticket and send us your scene for investigation so we could see if there is anything else going on with your particular scene.