Computer Freeze

[^Lele^]

Precisely an example of a discussion Lele and I had the other day. If you are a new reader and search for a topic you'll get ten different people to tell you ten different ways to do something; you'll go batty!

Yeah, but it's ok, batty is great! XD

Try 62 (and i ain't joking!), or two less than it can use.
Then try setting HT off, and try with 34 (again, two less than it can use)

Then try running an AV scan, malware scan, clear the browser cache, format the boot drive, and put fire to the workstation, and one of these will ends your freezing (ah. ah.) issues. (a'ight, pulling your leg in this last bit! But did you reboot? Twice? ^^)

[glorybound]

I did do a total reinstall after a Microsoft update broke my SSD drive, which was a know DELL issue. I think I might try to turn off hyperthreading, just to see what happens. Heck, I might see a speed increase. I remember Vlado saying that there is diminishing return when it comes to hyperthreading.

[glorybound]

I did to a malware and virus scan and all came clean. The burning might become a viable option.

[yavor.rubenov]

Hello,

The environment variable that you need to set is VRAY_NUM_THREADS with underscores between words and it specifies the number of threads not cores. So in your case you could try 71 or 70 with HT enabled.

The warning about having more threads than V-Ray will use is only related to the Light Cache calculation. The rendering itself will use all available.

You can remove the VRAY_USE_THREAD_AFFINITY - it was needed in older V-Ray versions and now it is on by default. It allows V-Ray to use more than 64 threads on Windows.

Best regards,
Yavor

[glorybound]

I turned off multithreading and my benchmark was better and it solved some lagging issues I am having in MAX. My machine is still freezing when I render, so I guess I go to 34 cores. Is a reboot required?

[yavor.rubenov]

You just need to restart Max, no need for full reboot.

[glorybound]

Would it make sense that turning multi-threading off would speed up rendering? Now, it did for the benchmark; I am rendering out a real scene now. It solved some MAX issues. It seems that MAX 2019 has a problem with too many cores.

[yavor.rubenov]

I assume you mean turning HyperThreading off not multithreading

It would be best if you could try some of your scenes with HT on and off. In most cases V-Ray renders faster with HT ON.

[glorybound]

Yes, HyperThreading. I'll try both and report back.

[glorybound]

Yeah, on/off or using the System Environment Variable, it doesn't matter. My machine still locks up.

[glorybound]

Does this look correct?

[glorybound]

I went as far down as 62 with no effect on freezing.

[glorybound]

Progressive works much better. It is bucket rendering that locks everything up. Is this a bug, or just how it is? I can't really complain if vray is using all the resources it can.

[yavor.rubenov]

1. Remove the VRAY_USE_THREAD_AFFINITY variable at all. You don't need it.
2. Add a new variable VRAY_NUM_THREADS=71 - that is the one you need.

That should help with the bucket sampler.

[glorybound]

There isn't an =, correct? The 71 is the value. This is having 0 effects for me. Bucket renders lock up everything and progressive makes it so you can hardly move the mouse.