Cant stop GPU render

[glorybound]

If you search the forum, I have been posting this issue for a while now. I think we are having the same problem. Others have said it is easier and faster to kill MAX than wait for the GPU to release the memory, which is what I do.

[francomanko]

Ive submitted a scene via support request id.

This is yet another different scene and the same issue.

[vladimir_krastev]

Thanks for the scene. I have it now and will try to reproduce the freeze.

[francomanko]

Nice one, also, i should have posted this in the suport ticket, but this time it froze when the ipr was running and I renamed a domelight and moved into a container.

[Muhammed_Hamed]

We have a fix on the way, this one was quite tricky to reproduce and fix. Seems to be related to the RTX engine for now

Best,
Muhammed

[francomanko]

awesome, nice work

[santiago_gutirrezdepierespedraza]

Was this fixed? I've been having the same issue.

[Muhammed_Hamed]

Was this fixed? I've been having the same issue.

Yes, what build of V-Ray do you have?
Are you using RTX or CUDA ?

Best,
Muhammed

[Alex_M]

Hello. I'm getting this bug with V-Ray 7. It normally happens after I use the "Pause interactive rendering" feature in conjunction with "Real Zoom". Yesterday it happened in an exterior scene and today it happened in a very simple interior scene. When this happens, the render buttons become inactive (see below). I'm using CUDA. If I start a production render through Max'es render menu (F10), Max crashes to desktop (minidump file attached). The only thing that fixes is restarting Max. BTW, this is an old bug. I remember this happening to me a couple of years ago, but unfortunately it seems that it has not been completely fixed yet.

[glorybound]

It has always been an issue for me and is one thing that keeps me from using GPU.

https://app.screencast.com/nW0XfMVGw1BLI

[Alex_M]

Thanks for confirming, Bobby. So it's not an isolated case. I was really hyped about using GPU for rendering with V-Ray 7, thinking most bugs would be gone, but it's mind boggling to me that they are still there more than 2 years later, and that makes V-Ray GPU really daunting to use for me. I'm wondering whether there's lots of people that actually use V-Ray GPU for serious time-critical production work with all these issues. I can't imagine having to deal with such bugs on a daily basis. Today, for example, I encountered the "700" bug, again, at least 3 times in the span of half an hour in a very simple production scene. V-Ray CPU has been nothing but rock solid for years, whereas V-Ray GPU seems to crumble just after a few minutes of basic use. It's as if two totally different companies worked on these render engines, I don't get it. Every couple of years I get hyped up about trying the new V-Ray GPU, and every single time I am let down.

[glorybound]

GPU doesn't make much sense for my exteriors. If there isn't any issue (there will be - three crashes to the desktop today), a GPU render takes about 45 minutes to clean up 100% with a denoiser of .4. On the CPU, the EST time is insane, but after an hour, with a denoiser at .4, it is just as clean without any issues. It is worth the GPU headache for my interiors since CPU times are way too high. The scene I posted the video of was going great, and then suddenly, I couldn't cancel. I had to kill MAX and try again. It took 2-3 times to get it working again. I had to reset the render engine to standard and back, which lost all of my VFB settings. All in all, I lost about an hour for absolutely no reason. This can happen many times a week. I invested in two 4090 RTX cards to go all in on GPU, and although I think it was worth it, it isn't a home run. Investing in a faster CPU would have been money better spent.