Did the lastest Window update fix the slowdowns?

[Joelaff]

After updated Window 10 today with the latest cumulative update it seems to have fixed the slowdowns with Threadrippers, making the systems much more responsive when rendering or using IPR.

Anyone else notice this?

I always suspected it was a Windows update that slowed them down to begin with, as I had no problems before late last year.

[Vizioen]

Which cumulative update do you mean? I didn't have one in the latest week. IPR I rarely use due to the performance being almost just as slow as starting and stopping a new render. Apart from when you're doing a single car or something.

edit: but I have a lot of extreme system slow downs with more than one 3ds max instance open though. Did you experience that? Even with latest updates it's still there.

[Joelaff]

It was cumulative update for 22H2. I am not on that machine to dig through and find more details though. I believe it was the one that came out on the first Tuesday in May. (We have the auto update crap disabled of course.)

Yes, we get slowdowns with multiple instances of Max, but if you minimize the other instances it is negligible. If you leave them in view behind another Max instance than the slowdown can sometimes be profound. I don't think this update solved that, though. Can't say I have specifically tested that because I am in the habit of minimizing the other Max (also keep you from clicking on the wrong material editor on a second monitor and making changes to the wrong scene.. no, never done that...).

[Vizioen]

It was cumulative update for 22H2. I am not on that machine to dig through and find more details though. I believe it was the one that came out on the first Tuesday in May. (We have the auto update crap disabled of course.)

Yes, we get slowdowns with multiple instances of Max, but if you minimize the other instances it is negligible. If you leave them in view behind another Max instance than the slowdown can sometimes be profound. I don't think this update solved that, though. Can't say I have specifically tested that because I am in the habit of minimizing the other Max (also keep you from clicking on the wrong material editor on a second monitor and making changes to the wrong scene.. no, never done that...).

Haha that last part got me. Hmm interesting I'll try and minimize my Maxes from now on, but that makes it all even weirder.

[Joelaff]

Minimizing makes all the difference. Occasionally without it minimized it might take 30sec or a minute to cancel IPR, which is absurd. Keep the others minimized and it has almost no effect (unless one of the BG Max processes gets into that state where it sits there and grinds on one or two cores continuously for no reason, even in the BG).

The update I just installed was KB5026361 Cumulative update for 22H2

[Vizioen]

Minimizing makes all the difference. Occasionally without it minimized it might take 30sec or a minute to cancel IPR, which is absurd. Keep the others minimized and it has almost no effect (unless one of the BG Max processes gets into that state where it sits there and grinds on one or two cores continuously for no reason, even in the BG).

The update I just installed was KB5026361 Cumulative update for 22H2

Yeah I have that one installed already. Will try some IPR to see if it's usable now.

[^Lele^]

listening attentively...

[Pixelcon]

Would be very cool if those suffering from this lag could fill out the form here:
https://forums.autodesk.com/t5/3ds-m...t/true#M207638

[gandhics]

It was cumulative update for 22H2. I am not on that machine to dig through and find more details though. I believe it was the one that came out on the first Tuesday in May. (We have the auto update crap disabled of course.)

Yes, we get slowdowns with multiple instances of Max, but if you minimize the other instances it is negligible. If you leave them in view behind another Max instance than the slowdown can sometimes be profound. I don't think this update solved that, though. Can't say I have specifically tested that because I am in the habit of minimizing the other Max (also keep you from clicking on the wrong material editor on a second monitor and making changes to the wrong scene.. no, never done that...).

Then, have you tried the Qt env var trick?
https://www.autodesk.com/support/tec...core-CPUs.html

[Joelaff]

Then, have you tried the Qt env var trick?
https://www.autodesk.com/support/tec...core-CPUs.html

Yes, I should mention we do have that set up. Didn’t really notice any change when we did it, though.

[Pixelcon]

No this trick hasn't worked for me since it was described.