3dsMax 2019.1

https://area.autodesk.com/blogs/the-3ds-max-blog/welcome-to-3ds-max-20191/

Alembic/OSL/FBX/Fluid update + Arnold 5.1 + many bug fixes.

Thanks for the info. Just downloading it.

I wouldnt recommend installing it! There seems to be a known issue with the viewport performance.
My viewport performance dropped down from 40fps to 3fp.

Huh, just in time, thanks for the warning!

Best regards,
Vlado

Dang…

Okay, can I just uninstall the update, leaving the previous version of 2019 intact ?

I did a quick search on the internet and couldn’t find anyone else mentioning this. Can you share links with other users sharing the same experience?

You guys can try it, maybe it doesn’t apply to your scenes. But I tested it with a “normal” production scene with like 1k objects and 80mio polys (including FP, RC, Vray Proxies, etc.). The workaround should be applying a mesh select modifier to ALL poly objects.

The issue is also mentioned in the changelog:
https://up.autodesk.com/2019/3DSMAX/3dsMax2019.1\_ReleaseNotes.htm
Known issues:

MAXX-43595
MAXX:Modeling
Performance degradation on playback involving many polymeshes.

@JezUK
Yeah you can, under program and feature the is a button on the left hand side “installed updates”.

So, are the painful `click twice menu ping` interface bugs fixed yet ? I`m betting not.

Thanks dude - worked a charm.

If you are referencing the issue with the dialog boxes not having focus and so you have to click on the box before you can actually make a change or interact with it. NO that remains and I think it has gotten worse. My impression is that previously the render dialog box had this problem, Now the render progress box also has this trouble. Start render>progress dialog box opens>click on “cancel” button in render progress dialog box>nothing happens (but now focus has become active)>click again (painful) and cancel works.

also the crossing window selection remains inconsistent and does not work all the time.

I am astonished by this lack of basic user functionality. A very sophisticated and expensive program that did not used to have these problems. It seems the authors of this have very little self respect. How embarrassing to put out something with such incredible capabilities and power but lacking the basic user functionality common to the simplest text editor. sheeesh I wish they would fix that stuff!

I can`t say I`m surprised but gotten worse ? Yikes. It`s not the main reason we`re not using 2019 but it would certainly help. I think it`s the kind of thing that if you never really notice it won`t bother you but once you do then it`s constantly a pain not knowing if you`ve clicked on anything and have to redo it. It`s a level of frustration you just don`t need as a user, there`s plenty of other annoyances for that ! I can only presume they don`t know about it still although I`ve submitted a report twice myself as I think others have so it could also just be incompetence or laziness as well. I don`t want to presume !

I mean, why roll out an update if it has a known issue for scenes with ‘many’ polymeshes…

Did anyone actually test the viewport performance besides dreidesign ? Because the the known issues page mentions performance degradation on “playback”. That’s not the same as viewport performance.

Here is also a 3dsMax forum thread, where someone confirms that it seems to be a known limitation:
https://forums.autodesk.com/t5/3ds-max-forum/3dsmax-2019-viewport-performance/m-p/8070422/highlight/false

Yes, I did and it was sh*te

I just installed MAX 2019 and my first launch gave me script errors. I immediately installed the first update and that went away. So far, it is pretty laggy when working with splines and so far this morning, three non-responding screens, which caused me to kill MAX. It is basically acting like 2018 did, so I guess I’ll stick with it. The dialog focus continues and so does the sticking window/crossing button. $1920 a year to rent the software is simply a cash cow for them. There are 300,000 MAX seats out there.

Your issue seems more related to nvidia driver.
There has been many report you need to pick “good” driver.

PU1 will have issue when you changes frames.
But, it should be OK when you are working at a frame.
I need to test more I guess.

I was told this requires complete re-write of Render Settings UI as Qt.
Qt doesn’t like tab apparently.
So.. it might take a while.

Yeah, the NVIDIA driver game is getting old.