Lagging behaviour

[lorenzo_spinola]

good afternoon everyone,
I'm experiencing a weird behaviour lately, basically, max get frozen for several second repeatedly during the job.
Initially, I thought was because of Phoenix and the simulation, than I thought was about pulze plugin and the render setting tab open.
Everytime I stopped a render it took about 30 sec before I was able to do anything.

Than, this morning I installed and setup max 2022, because 2021 decided not to open anymore for no reason.
I have a simple scene, 5 blocks and a bunch of lights, 2 materials.
When I do something with the IPR active you can see the problem I have in the video I'm attaching.
I don't want to blame vray, but this kind of lagging are happining only when I'm playing with material node or with the render active.

Could anyone point me in the direction to check if something is wrong in the setting, please?
It's becoming annoying now working in this way

Thanks in advance,
Lorenzo

https://www.dropbox.com/t/RgFPrnokt1uKYCZa

[^Lele^]

What does the task manager look like when the IPR is off and Max open?
And with Max entirely off?

[lorenzo_spinola]

What does the task manager look like when the IPR is off and Max open?
And with Max entirely off?

Hi Lele,
I honestly didn't check.
As soon as I have the problem I'll take a screenshot/grab a video.

Lorenzo

[^Lele^]

I've asked because it could be there's something else doing things in the background, either in max (funky callbacks can do this.), or in the OS proper (say, antivirus being obstinate, auto-defrag, this kind of things.)
Those often end up on the first physical core, just as Max for most of its operations (f.e., duplicating a node triggers a cascade of background messaging.).
IPR, seemingly, is just fine once it starts (as it uses all the free cores), which is why i have this specific suspicion.

[lorenzo_spinola]

I've asked because it could be there's something else doing things in the background, either in max (funky callbacks can do this.), or in the OS proper (say, antivirus being obstinate, auto-defrag, this kind of things.)
Those often end up on the first physical core, just as Max for most of its operations (f.e., duplicating a node triggers a cascade of background messaging.).
IPR, seemingly, is just fine once it starts (as it uses all the free cores), which is why i have this specific suspicion.

Hi Lele,
I tried to keep checking the issue I had during this period of time, I wasn't been able to replicate but seems to happen sporadically.
I usually work with the same software open, same routine, couple of max to get objects or modelling etc etc.

The only thing I "detected", it starts to lag when I stop the render.
This time it went in a loop, max wasn't responding at all.
I checked the task manager but looked normal, cpu was low and ram around 50%

https://www.dropbox.com/t/mnK8psOJyYA97EuH

Lorenzo

[^Lele^]

I can't repro the behaviour, myself.
It looks like issues with video drivers, or something a spacemouse driver would do.