3dsmax 2017

[Vizioen]

I still wonder why the fck they HAVE to release a version each fcking year, take some goddamn time to polish your product and let the people restore their faith in it. Look at Rhinoceros 3D. While not the same at least they don't go backwards when they release a new version every few years.

[glorybound]

I think if you were on WIN7, without 3rd party plugins, it might work perfectly. Walls and Tiles will not work on MAX 2017 and WIN10, but so far, all the other 3rd party plug-ins work fine for me. When I say plug-ins, I mean the big ones. I have many smaller scripts that don't work. You can always install MAX 2017 along-side MAX 2016 and do some testing. I would love to see a report on 3DS MAX adoption rate. I have a feeling it is still rather low.

[Pixelcon]

- 3dsmax settings reset bug is even more common now

This is frightening...

[kosso_olli]

I can not say it is the worst version ever. I have been using it in production since the release, and it is very stable so far. And in my opinion they have done a good job making things faster. The viewport performance has been increased significantly, especially with many objects and manipulations in subobject level on high poly geometry. Try Maya, now that's a nightmare!

[Moriah]

Hey BBB3, could you tell in what specific cases are you having crashes, or what is actually broken so far in 2017? Me and my company have been "forced" to rent some 2017 licenses, and i'm afraid sooner or later we'll all have to transition to it.

Things i found so far that don't work:

- Certain snapping options are broken
- UV editor is slower than 2015
- Physical Cam is a mess
- 3dsmax settings reset bug is even more common now
- Backburner adapter gives some weird errors sometimes
- Weird new UI (that light grey on darker grey doesn't make the overall reading easier)

Good things:

- Edit Poly sub element is really fast
- IPR with Vray nightlies
- Really fast installation
- Alembic options were updated + Alembic cache

[Alex_M]

Are you guys serious? I was eager to try out 2017 already now that SP3 is out. Is it really that bad? As in worse than 2016? Now I'm afraid to install it and move production on it as I was hoping to do. I'm hearing all kinds of conflicting opinions.

[BBB3]

Max 2017 is the worst version ever. It's severely broken and the worrying thing is Autodesk seems to have no clue what's wrong with it. Half-way through the version's lifetime, we have three SPs that haven't fixed anything but the most superficial problems. But I guess it was to be expected since the move to rental. Why invest anything in developments once you have your captive audience?

[Midiaeffects]

I'm not sure if that's possible to do in max, and how would you evaluate that inactivity? It's based on mouse movement or some other parameter? Maybe mouse movement would be possible but not sure how taxing it would be on the processing side of things... Maybe someone more experienced than me could figure something out of that sort.

Not sure how safe that would be, but maybe by tracking the undo stack size. If it doesn't grow for a while, there's no need to autosave.

-Eugenio

[jstrob]

Back to 2016 for me too! A lot of crashes too. Though I have been working with Forest Pack for my current project and I don't use it often so it could be related but that's the big problem with max. As soon as you are using some plugins (which you always need) it becomes very difficult to troubleshoot.

And the biggest problem I have is not even the crashes (I also disabled autosave crap BTW) it is the fact that I just can't install SP3 on my render nodes. I can't even uninstall sp2 and I can't uninstall max 2017. If I try any of those, the installer will freeze all night. I tried on around 10 computers. In fact it worked on only one which didn't have any plugins installed. So one of my plugins might be interfering so I have to try to uninstall the whole thing. So probably not worth it. Max 2018 is around the corner but I have to renew before and I don't feel like renewing at all!

[Moriah]

I'm not sure if that's possible to do in max, and how would you evaluate that inactivity? It's based on mouse movement or some other parameter? Maybe mouse movement would be possible but not sure how taxing it would be on the processing side of things... Maybe someone more experienced than me could figure something out of that sort.

[JezUK]

Sure, scriptspot isn't loading for me at the moment since the autoback ones are hosted there, but the other one is from Clovis Gay and it's free (this doesn't auto save, just warns you, but does auto incremental save through it) - https://hocuspocus-studio.fr/tools/product/save-button/

When scriptspot is back up i'll link them, if not i can upload them to dropbox or something.

Also it isn't very hard to script a customized autoback up, where you can customize your versioning, where it goes to, how many versions to keep, etc. A simplified version would be a timer-based incremental save.

I just don't get it how autodesk programmers didn't do such thing already... I mean it's so crucial for everyone, specially with such an unstable piece of s... software.


edit - This is one of them and the one i use at home - http://www.scriptspot.com/3ds-max/scripts/auto-save

Thanks

As sod's law would have it, I did do a search on Scriptspot when I saw your message, and as you say, their site is playing up !

One of the annoying things I find with the version of Autoback up which comes with Max is that it saves based on elapsed time - when I'd rather it saved based on actual usage time. For example, I set my AutobackUp to save every 15mins, but if I stop working for 14mins 50secs (say to take a phone call), then the Autosave will back up in the next 10seconds, even though I've not touched the scene for most of that time.

So I'd rather it takes inactivity into account.

[Moriah]

Care to name them ?

Sure, scriptspot isn't loading for me at the moment since the autoback ones are hosted there, but the other one is from Clovis Gay and it's free (this doesn't auto save, just warns you, but does auto incremental save through it) - https://hocuspocus-studio.fr/tools/product/save-button/

When scriptspot is back up i'll link them, if not i can upload them to dropbox or something.

Also it isn't very hard to script a customized autoback up, where you can customize your versioning, where it goes to, how many versions to keep, etc. A simplified version would be a timer-based incremental save.

I just don't get it how autodesk programmers didn't do such thing already... I mean it's so crucial for everyone, specially with such an unstable piece of s... software.


edit - This is one of them and the one i use at home - http://www.scriptspot.com/3ds-max/scripts/auto-save

[JezUK]

Why do people keep using that crappy Autoback "feature", that doesn't even save half the time... When there's a few scripts out there that do the same, better, faster, and don't crash...

Care to name them ?

[glorybound]

I guess we assume since we pay a lot for the software, it'll work like it should. Silly us!

[Vizioen]

Why do people keep using that crappy Autoback "feature", that doesn't even save half the time... When there's a few scripts out there that do the same, better, faster, and don't crash...

Only thing positive about 2017 for me is that the edit poly sub element mode is pretty fast now, 2-3x faster, compared to 2015. Other than that.. meh

I don't use it but I have a script that tells me when to save though. Although not ideal actually. Which ones are you referring to?