Did anybody else get bricked by the latest 3DS MAX update?
Seems to be fine for me so far.
What happened?
From what I have read it’s to do with chamfer modifiers not allowing a file to load completely. It seems like rolling back to the previous version is the only workaround.
Yup, if you chamfered anything, your model is bricked. No fix and they still have it in the download sections.
Yes I noticed when I rebooted that it popped up in the list. That is just purely negligence but they are very new to this whole ‘software’ thing, so maybe it’s
a noob error 
We keep a monthly system image for each pc in our studio so after we did some restores and some trial and error, we discovered that Windows update KB5016616 caused some odd issues with 3dsmax.
Specifically causing scenes to freeze on open at 73% and then again at 82%.
Those scenes that we were able to open took an unreasonable amount of time (despite our 10gbe lan) and their viewport performance tanked badly.
Even drag&drop of a single insignificant model from Connecter to a blank scene was unbearably slow.
It was consistent across all workstations in our studio and our bosses were upset because we couldn’t get any work done.
Anyway, we withheld all windows updates and once KB5016688 was out we installed it, and everything was fine ever since.
Their fiverr developer must not be responding to their emails.
Hmm…oddly I have not installed the update but have just realised that even on the previous version, loading does stall at 73%.
The particular heavy scene does load but it seems like an odd coincidence, or in fact something that was troubling even in that version.
Or they are doing things behind the scenes, without user intervention.
Like windows fucking updates that constantly mess with my stuff
Scary but I doubt that tbh.
Did you update anyway?
I removed MAX and reinstalled it from scratch. It took a day to get everything up and running again, but I am sure I’ll be installing things all week, as I need them There are other complaints about the same thing happening to them.
It has beed fixed now with version **2023.2.**2
…guess I’ll take the risk then…see if it cures the coincidence 