Hello!
I facing some issues with V-Ray that I’m not sure where they come from. Usually this happens when I’m working with materials and previewing some nodes, but I noticed this seems to be also common if I’m using geometry nodes and instancing the object which the material is being modified.
Not sure if it is just a bias or if there’s really something related to geonodes. Here’s a quick record of this error with a very simple scene. Error happens both in the Viewport and using VFB.
The behavior is always the same. It freezes the viewport for a moment and the error happens. Luckily it does not compromise/crash the file, and only requires VRay to be restarted.
Blend file I’m working in case you want to test it on your side.
vaso_sanguineo.zip (477.9 KB)
I was able to reproduce it. We will look into it.
Hi, I have logged the issue (VBLD-2660).
As a workaround, you can split it into two separate objects instead of using the Join Geometry node.
Thanks!
Do you know if this is a particular issue of this node tree or something related to join geometry node? I just want to be aware of possible future issues
I looked at the crash and it looks like it’s a problem with instances in general and the order they are updated in interactive. I will need to look a bit more at what exactly in this setup causes it.
I don’t think this is related to the original problem, but since the latest version of V-Ray for Blender (5.2), I sometimes get this message when launching the software as well.
In my case, it usually happens on the first startup, which takes longer than usual. After that, there are no issues.
I know this might not necessarily help with the original problem, but I’m taking this opportunity to mention it.
This is the message for any crash of the Zmq server(the process where the rendering actually happens). If you encounter such errors there might sometimes be a crash dump in the local appdata - %localappdata%\CrashDumps\VRayZmqServer(pid).dmp. The crash at startup I suspect is from a problem with GPU devices detection which we’ve fixed already.
Are these files somehow useful for you to check the errors? I have 10 of these, but I think only the ones from 30th are related to my post
