I reported that the latest update of Vray 6 (hotfix 4) creates problems with GPU calculation (Cuda/Rtx). Rhino 8 crashes when rendering via GPU. I thought it was the fault of the latest nVidia drivers, but I verified that it was their update’s fault, since even with the April nVidia drivers Rhino 8 crashes.
Have any of you encountered the same problem?
1 Like
Did you install the Vray recommended driver version? Its version 551.86 - newer versions have problems.
I asked Chaos support directly, they told me to install the April driver version (552.22); I tried, but they didn’t work. You tell me to try with the March drivers (551.86), I don’t want to have to try all the old drivers…
I’ll try! Thank you.
Website says its 551.86
(all the new drivers have always worked up until Vray (hotfix 3). Once the latest update (hotfix 4) has been installed, suddenly the latest nvidia drivers no longer work).
Thank you
I have had problems with newer drivers and V-Ray in the past, no crashes tho…
It’s strange that Vray worked up until update 3 with every driver installed (including the latest ones). I updated Vray to the latest hotfix and nothing works anymore. I would blame the problem on the Vray update and not so much on the drivers.
(I have tested all nVidia drivers, as I always update them).
Having a similar issue here. If rendering on GPU via Grasshopper, Rhino will Crash after 10-30 Frames. Tried different settings., Different Geometries, Materials, …Tried different drivers (also 551.86). It´s the same for Rhino 7 as well. Can anyone successfully render animations on GPU via V-Ray for Grasshopper?
Can you post a simple file+gh definition to try?
Sure, Here you go.
I am rendering some linked Mesh, but I think it does not matter, as long as your object is sufficiently complex. Mine will crash after 12 Frames. Let me know, if it works on your machine. Cheers
240615_vrayGPUtest.gh (35.5 KB)
*Edit: You will not need assigned materials, just delete in case.
Seems like its working here. I am on frame 240 of the Casiopeia supernova remnant you linked in the gh file.
P.S. latest stable Rhino 8 and V-Ray, with the 551.86 driver
1 Like
Interesting! Thanks for testing. Strange though, I have no idea what could be wrong. Using the same versions as you. At the moment I am running the same file on CPU without issues either. Hmm. Any idea how to figure out, why exactly it is crashing?
When rhino crashes, it saves a crash dump file. You can submit that file to Chaos for analysis.
Also you can check the V-Ray logs for clues (or submit them to Chaos for analysis).
Also you can contact Chaos support if you can reproduce the problem reliably
1 Like
Which Card are you using? Chaos is on it and they could reproduce the crash so far, but we could not figure out the cause yet. Anyone else with a RTX 4090 can run the most simple file and reproduce this by “render animation”?
240628_vrayGPUcrashTest.gh (16.6 KB)
- it does not really matter, but I am rendering this mesh:
https://nasa3d.arc.nasa.gov/detail/cassiopeiaA
I tried this on a machine with a 4060
I am a 3080 graphics card and have updated the recommended drivers, but I have also encountered the same problem.
1 Like
Apparently they could track down the bug and about to fix it. Hopefully in the next release. Maybe if you let them know about yours in their forum, it will speed things up.
Thank you for your response. I have followed all the methods mentioned in the forums, including updating to the recommended GPU drivers (which, unfortunately, seemed to make things worse). I also came across posts suggesting that switching the GI settings to BF+BF (Brute Force + Brute Force) could help. However, I couldn’t find where to set this up in Grasshopper, so I tried configuring it directly in Rhino. Unfortunately, this didn’t seem to make much difference, and the crashes continue to occur randomly. Rhino shuts down abruptly without any error messages.
For reference, I currently have 64GB of RAM and an RTX 3080 with 10GB of VRAM. Should I consider upgrading my memory further? It seems like many users are encountering this issue, and I hope the development team can address it soon.
Thank you for your time and assistance.
None of this will fix the issue. As said it it a Bug in VGPU at Vray itself. Your machine certainly does not need an upgrade. AFAIK the bug is related to how secondary rays are calculated. Your two options are 1, wait for the next hotfix or 2, export the animation and run from RH with these settings.
I still don’t know how to export the render files from Grasshopper to Rhino. As a result, when I open the settings, the Animation option you mentioned is not accessible. I would greatly appreciate your guidance on how to properly export the scene and enable this option.
Thank you for your assistance.