Multiple 3ds Max instances open + Saving = Lag

[DGTLTWNS]

Hi,

I have a few reports of people with 3ds Max 2020, 2022, 2023 (haven't tested 2021) slowing down our workstations, when multiple instances of 3ds Max are open and (auto)saving.

I have recorded a video of this here: https://youtu.be/zzsiOCMhHr8

First part of the video is me saving with only one instance open. Second part (00:18) is with a second file open in another instance. As you can see my workstation grinds to a halt and my cursor is barely moving. It seems I'm not the only one. This started happening a couple of months ago. Maybe a Windows update caused this or something. I looked at my Windows 10 update history in the last half year and most of them are .NET updates.

Can people with the same experience confirm, and could Autodesk investigate this please, because this is super annoying.

Thank you.

[Diffus3d]

Sure is weird. 

[RobH2]

Would there be any wisdom to just reaching out on ASUS & MSI forums to let them know what's going on over here? There might even be some chatter about Max on their forums, if they have them.

[info2V35E]

Can't hurt!

[DGTLTWNS]

Well things are getting more weird. I just now received a comment on my FB post in stack, someone who mentions having this on an INTEL system. Who swears he didn't have it until he put a second GPU.

And also comments on the same post of 2 people with Ryzen + ASUS motherboard who don't have that problem, or so they say.

So...back to square one. If indeed some people with Intel are now also suffering from this, than I have no clue anymore.

[RobH2]

Quote: "Oh ok. Why do forum replies on this forum not automatically quote the thing I'm replying to?"

It's easy enought to just copy and paste what you want to "Quote" and then write below it as a workaround, like I did with this one. That won't solve it for other users, but at least yours will have the relevent info you want to reference.

[info2V35E]

I know, but why would a forum choose to even allow this behavior? It's nonsensical.

[RobH2]

For over 25-years I've told people the 3ds Max Forum is one of the best on the planet. We have access to some of the best 3d talent in the world because a lot of them cruise through here now and again. And we don't often suffer from the inane and sophmoric banter that destroys a lot of other forums.

So, I for one, am willing to overlook an oddity with the structure of the forum. There could be a good reason for it. Maybe there is a setting in your profile to change it, not sure.

[info2V35E]

Wow. Hit a nerve, did I?

[DGTLTWNS]

Let's not get sidetracked with the flaws of this forum.

You guys might have overlooked my previous post stating that it might not be limited to AMD processors anymore either.

[Diffus3d]

Does anyone with the problem get any info in their windows event viewer logs?

Best Regards,

[DGTLTWNS]

I've checked about anything, even with procmon (although I'm not an expert in this), nothing to find. What worries me is that there are reports of people with Intel too.

[info2V35E]

Just spoke to a colleague of mine with some interesting info. He's NOT using an AMD and confirms this behavior.

Pertinent info:

Windows 10 Pro 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406)

Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz (48 CPUs), ~2.4GHz

262144MB RAM

NVIDIA GeForce RTX 2080

He has a HP Z840 Workstation and I believe the motherboard is HP. 

So neither AMD or Asus/MSI (unless HP source their mobos from one of those two suppliers).

[DGTLTWNS]

Yes I have confirmation on the Facebook stack group that some intel users are experiencing the same problem. So in short we can say this has nothing to do with AMD only. It's something that applies to AMD as well as Intel, and as well as other motherboards. There's no red thread in this whole thing.

And in short: Autodesk's explanation of it's an AMD Ryzen problem is FALSE. 

Which brings us back to square 0. 

[info2V35E]

He did say that his previous install was max 2020 and it did not exhibit
the problem. He is now using 2023

[DGTLTWNS]

In the beginning of 2020, when I was using my 3970x as a daily workstation with 3dsMax 2020 I didn't have these problems either. Although I have one or two reports of users having this problem with 2020 as well.

Honestly I don't know what to do anymore. I'd like to invite Autodesk to look at this whole thread and some of my FB stack posts + comments. I'll open a new ticket with our new findings and hopefully they'll be more inclined to get to the bottom of this.

[DGTLTWNS]

FYI. I've opened a new ticket with our 'new' findings.

[info2V35E]

much appreciated

[DGTLTWNS]

Well, I received a reply back. Besides, we know, we're working on it and thanks for the additional info. Nothing substantial unfortunately, no ETA given due to policies. 

[info2V35E]

Well at least they're aware of it as a real problem and not just forum
whiners...

[Diffus3d]

Having some sort of data (like you all collected) is key to getting something like this looked at because how do you even reproduce something like this if it doesn't happen to devs or beta testers on their machines?  Tough one.  I'd say you all did a good job of being a team and making it happen and knowing they have logged it means it's on the radar.  It's nice to see this level of cooperation. 

Best Regards,