3dsMax 2019.1

[glorybound]

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.

[gandhics]

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.

[gandhics]

Yes, I did and it was sh*te

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.

[gandhics]

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

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.

[glorybound]

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

Yeah, the NVIDIA driver game is getting old.

[JezUK]

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.

No changing frames for my project, it was simply unusable in a perspective viewport - fps were as others had described, before PU1 was around 35-40fps, with PU1 installed was 3-5fps.

[anthonyh]

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.

Well that isn`t gonna happen then. They`ve only just built this interface so I can`t imagine they`ll rebuild it again to fix this issue. I can`t believe nobody at Autodesk noticed, I mean I don`t believe it, at all.

[JezUK]

........ I can`t believe nobody at Autodesk noticed, I mean I don`t believe it, at all.

I believe it. If they are prepared to ship an update with a known issue such as this, my cynical thoughts were that this was more about wanting to be seen to be doing something, anything (shareholders perhaps ?) than it was about delivering a quality update.

[glorybound]

Or maybe simply, they just don't know how to fix it. They have to work from a list and if a critical issue is on that list for years, they probably can't fix it without causing a bigger mess someplace else.

[OPEN_RANGE]

I don't want to minimize how annoying, frustrating and embarrassing the dialog box focus and window crossing issues are. Pathetic is one word that comes to mind.

Otherwise, for me so far 2019 has been very stable and usable. Including using IPR and Forest Pack stuff. I don't use any other plug ins and keep a pretty basic work flow so.... (probably just jinxed myself)

[gandhics]

Yeah, the NVIDIA driver game is getting old.

Well... it is your choice to believe or not.
But, you can not solve problem without knowing where problem is first.

[gandhics]

Well that isn`t gonna happen then. They`ve only just built this interface so I can`t imagine they`ll rebuild it again to fix this issue. I can`t believe nobody at Autodesk noticed, I mean I don`t believe it, at all.

3dsMax has started to adopt Qt since 3dsMax 2017.
3dsMax the entire UI frame is move to Qt.
All new UI since 3dsMax 2017 are written with pure Qt.

But, there are tons of legacy UI written in win32 like Bend modifier.
Also almost all 3rd-party plugin UI is not Qt.
Therefore, 3dsMax dev choose to draw Qt UI on top of legacy UI for smoother transition.
That's why all legacy plugins are automatically supported.
If dev just moved to Qt and force to use only Qt, we would lost a lot of free plugins and had to wait long time until all 3rd party plugins are converted to Qt.

This strategy worked well for most part of UI.
BUT!
Dev found out that the tab UI is not working well with Qt and has been trying to address this issue.
In the end, they conclude that Render Settings portion of UI need to ported to Qt to fundamentally solve this problem.

That's what I heard.

[glorybound]

My biggest issue is panning and zooming. I can no longer just pan and zoom. I have to pick in the viewport once before I can pan or zoom, which is a pain.

[glorybound]

The MAX support guy, over on MAX's support forum, said that they caught the viewport performance issue right before they deployed it, but it was too late. They have a fix and it will come out with the next update. EYE ROLL!!!!

[JezUK]

It’s a good job Autodesk isn’t in the avionics software industry......