Max - Vray when rendering complex scene screen jumps on / off

V-Ray V-Ray for 3ds Max Issues
1

I have a very complex scene using 80gb ram. Loads of scatters / trees / plants etc.

On my old machine i7 64gb my scene occasionally when rendering would freeze and the programs keep jumping on screen off screen. Since getting a dual xeon 72 cores and 128gb ram im still occasionally getting this happening. Its really odd doesnt happen all the time and usually still renders the image although you can never see whats going on. Its like the machine has crashed but hasn’t.

Anyone else experienced this
Vray 3.6.04

2

Am i the only one experiencing this issue. It makes working on very heavy scenes nearly impossible to test render. Cant stop the render as its always not responding until the render completes.

3

I have the same problem, also dual xeon

4

It’s a well-known problem that seems to affect dual Xeons. I got it on my old Z820 too.

5

Thanks for the update - i had this on my i7 - im sure it seemed to be from either Max 2018 or Vray 3.6.04

6

Hello,

This sounds much like this one:

and here are some possible workarounds:

Best regards,
Yavor

7

Honestly, the workarounds don’t do anything for me.
I’ve tried all except the QT settings which some users reported messing up their system in a big way.
The only solution was to go back to 3ds max 2016. The ‘dance’ only happens in 2018 (same vray version)

8

What’s worrying me is that I had it happen once in the Vray Next Beta too, which suggests the problem remains…

9

That’s indeed worrying, would make me think twice about upgrading.

10

It seems to be a general problem and not V-Ray specific - so it is not something we can fix for V-Ray Next.

11

So why doesn’t VFB play nice with 3ds max’s newer versions on my dual xeon system?
I just tried out 2019 in hopes of improvement and it’s a mess. The vfb flickers, jumps around, it’ is impossible to cancel a render without killing max itself.
I convert the same scene to corona and render just fine. Canceling a render is without any problems. What gives?
You say it’s a general problem, but it seems that it happens only with vray.
As it is now, I’m either permanently stuck in the past using max 2016 or have to abandon vray as it is impossible to do any work…