Maya 2022 / V-Ray 5: Lack of stability

[sebbiej]

I seem to be having a lot of stability issues with the latest version of V-Ray GPU and Maya 2022. A lot of the time when I use the IPR renderer the renderer hangs and then it hangs up Maya after it gets past the 'Compiling Kernels' stage, it can also just make Maya disappear without warning.

I've found that I can render still frames ok (mostly), but the IPR render crashes then I get the error message: // Error: line 1: V-Ray : Unhandled exception occurred, will exit render loop.

I'm running the recommended Nvidia Studio driver on an RTX2080Ti, Windows 10 Pro 21H1, AMD Threadripper 1950X.

I've also had issues where the V-Ray GPU won't render unless motion blur is switched off, which can be problematic when it comes to rendering animations. I'm not sure if anything can be done to help all this but thought I ought to make it known...

Edit: Also I'm seeing this message a lot, it's making progress incredibly slow when I need to do is render a super simple scene - basic geo, some fairly simple shaders and dome light. // Error: V-Ray : There was a fatal error rendering the scene.

[Muhammed_Hamed]

Hello sebbiej

Could you try with this stable build here

https://nightlies.chaosgroup.com/mai...5.1.2/20210820

Some of the Optix errors from the official build has been solved. It has been more stable in my experience

[sebbiej]

Hello sebbiej

Could you try with this stable build here

https://nightlies.chaosgroup.com/mai...5.1.2/20210820

Some of the Optix errors from the official build has been solved. It has been more stable in my experience

Thank you, Muhammed, I'll give that a try!

[sebbiej]

I'm still getting Fatal Errors with my scene.

I seem to have narrowed it down to V-Ray being unable to render when I assign a texture to a secondary UVSet on a mesh. This 63k mesh (when '3' smoothed) in my scene renders ok with a basic shader set up on it, but as soon as I assign a texture to a 2nd UV set it gives me the error // Error: V-Ray : There was a fatal error rendering the scene. //

[Muhammed_Hamed]

I seem to have narrowed it down to V-Ray being unable to render when I assign a texture to a secondary UVSet on a mesh

Maybe this about your specific mesh, using a 2nd UV set here works fine

Best is to upload this scene for support, if they reproduce the crash it will get solved

[sebbiej]

Maybe this about your specific mesh, using a 2nd UV set here works fine

Best is to upload this scene for support, if they reproduce the crash it will get solved

It is a little odd, usually, it works fine for me too. I've managed to get around it for the time being by adjusting my default UV set to replicate the secondary one, so I won't bother the support team for help at this time...
Thanks for the replies anyway, Muhammed!

[sebbiej]

The stability of this latest version really is becoming infuriating now... I'm having issues with multiple different scenes and sets ups. Countless failures when trying to render with GPU. Such as:
// Error: line 1: V-Ray : Exception [module=1] : Rendering region (992,864)-(1024,896) //
// Error: V-Ray : There was a fatal error rendering the scene. //

// Error: line 1: V-Ray : Unhandled exception occurred, will exit render loop.

And then of course this one:

t_private
t_opencl_(1556) : CUDA error 700 //
// Error: V-Ray : [MemoryManagerGpu::releaseUnmappedMemoryFromInstanc e] 700: Could not release device buffer //


Can we get a properly stable release soon?!

[sebbiej]

As a guide on how infuriating this really is: I was rendering out a 475 frame long sequence out over the weekend. Nothing overly complicated, simply some Xbox game case models coming in to shot and moving out again. Only 4 of them, so the geo count is pretty tiny: 14000. I sent this to render out via Backburner, and checked on it on Saturday.

Around 300 frames rendered out fine, then Vray had seemingly crashed out on the remaining frames not entirely but randomly over the sequence. Leaving us with about 50 frames this morning that had rendered out without any data, or not been rendered at all.

So this morning we're attempting to render out the random frames via the frame buffer in little segments or singularly. But, V-Ray will render a frame or two alright then it'll bug-out and give us errors like the below.

// Error: line 1: V-Ray : C:CIcgrepovraysdksamplesvray_plugins t_private t_opencl_(1556) : CUDA error 700
t_opencl_(1556) : CUDA error 700 //
// Error: V-Ray : [MemoryManagerGpu::releaseUnmappedMemoryFromInstanc e] 700: Could not release device buffer //
// Warning: line 1: V-Ray : Error 700 while intializing context for device NVIDIA GeForce RTX 2080 Ti! Device will not be used for rendering! //
// Warning: line 1: V-Ray : initDevices() failed. Please check that your system has compatible GPU devices installed. //
// Error: V-Ray : Could not initialize the GPU for rendering! //

This shouldn't be the case daily for a 'production ready' renderer on a really simple scene. I'm running the recommended driver, and the latest 'stable' nightly (as was recommended on another thread.)

[sebbiej]

I'm working tonight on a different computer, different setup, different projects, and scenes. The files worked perfectly well with Vray 4. Now when I open files and try to render a still image of a product with V-Ray GPU I'm given this error:

// Error: V-Ray : There was a fatal error rendering the scene.

I'm losing my mind here just trying to do the simplest of renders. How did the software even make it out the door with constant failures like these?

Edit: I've resorted to rolling back to Vray Next Update 2.2 - The file renders straight away, no issues. Am I to be stuck on using Vray Next now after spending so much on 5?