Attempting to re-render existing 3.6 scenes with VrayGPU NEXT through Backburner is giving us alot of problems (errors). Most specifically is this error "3dsmax adapter error : Autodesk 20.3 reported error: [V-Ray] [VRayRTMax::Render] Exception during VrayRTMax::Render()". Is anyone else experiencing problems generally with older scenes rendering in VRayGPU NEXT? I'll try to get a scene file sent out, but I was honestly hoping our recent upgrade to NEXT wouldn't be as unsatisfactory as the last updates and GPU rendering since 3.6 (see my other BUG topics). Maybe there's a list of "gotcha" settings which are causing problems for GPU rendering?
Announcement
Collapse
No announcement yet.
Exception during VRayRT
Collapse
X
-
Hello,
Sorry for the inconveniences you are having. We would very much like to help and make sure that there are no such errors no matter the settings.
First of all - do you have any 3rd party plugins installed? Many of them have specific code that depends on the V-Ray version and installing V-Ray Next might be causing incompatibilities if you don't install a new version of those plugins.
Another issue we've been getting reports lately is related to the video card drivers and Windows updates - after some Windows updates the video card driver gets messed up. Reinstalling it and also restarting your computer(that's mandatory) helps.
Finally - when those errors happen - we create crash dumps called VRay.dmp in the %temp% folder - we can examine it for hints to the exact cause of the issue.
Best regards,
Yavor
Yavor Rubenov
V-Ray for 3ds Max developer
-
Hi Yavor,
No, there are no 3rd party plugins used in this scene.
We are currently up-to-date on our Win 7 machines for the GPU render farm. Which NVidia driver version is recommended for Vray?
Is the crash dump also produced on render node machines? I do see a VRay.dmp file, but the time stamp isn't showing the last error on that machine.
Thanks,
Comment
-
Generally the latest nVidia driver should be OK - for example 397.64 but the issue is that the Windows Update messes it up even if it the latest.
Crash dumps are produced on render nodes too - could you try to delete any existing VRay.dmp files and see if a new one is created.
If that fails - a scene would be helpful.
Yavor Rubenov
V-Ray for 3ds Max developer
Comment
-
Hello!
I had the chance to explore the scene and run some tests.
There is a material with name AM141_042_001 assigned to AM141_042_obj_009 (one of the plant blooms) and it causes issues with BB.
Please, check if the issue persists when rendering in your environment after you delete that object or assign the material Multi_PlantWhiteYellow instead - it is used on all other plant blooms. |
I hope this workaround will resolve your issue. Please, write back with the result so we would know how to proceed further with a fix.
Best regards,
MargaritaMargarita Stoeva | chaos.com
Chaos QA (V-Ray for 3ds Max)
Comment
-
Hi Margarita,
I deleted the object and started the render again. It's been running solid now since, so that seams to have fixed the errors. Although I know older assets from other sources often cause problems, this one threw me off as 3.6 RT GPU rendered it without problems. I'll be sure to try and avoid directly using such assets in the future. Thanks for the very quick response and help.
Comment
-
Just to add a note - the problem is indeed with the two sided materials and happens when there is something animated in one of the sub materials. We are working on a fix for the issue and hope it will be ready soon.
Thanks again for the scene and sorry for the inconvenience.Yavor Rubenov
V-Ray for 3ds Max developer
Comment
-
Drop a line to support@chaosgroup.com to give you access to the stable nightlies.If it was that easy, it would have already been done
Peter Matanov
Chaos
Comment
Comment