3dsmax 2017

[glorybound]

If it doesn't fix things, there really isn't a point to upgrade. I remember paying the subscription on an AD product for 3 years, without any patches, SP, or upgrades. AD eventually pulled the plug on it, so I paid 3 years for absolutely nothing.

[krassi]

hii!

well that pattern with "uneven suxxs" is like windows versions.
the 2016 works """"ok"""" for me but its still "mehh".
So 2017 cant do anything worse ..

large scenes are of course a total joke with 3dsmax.. 4000+ objects and its dead.

since i will reinstall my workstation with a fresh windows 10 i will try 3smax2017 before wiping it.

[glorybound]

I was skeptical at first but 2016 works fine for us. Still on SP1 out of fear of breaking things that work, after hearing to much bad things about SP2 and 3.
Had high hopes for 2015, but went back to 2014 for production work. The layer manager/scene explorer was a nice idea, but turned out to be a nightmare. At least it works in 2016, even though it isn't exactly smooth and comfortable to rename or move things - it renames the things you want to. Also had loads of trouble with snapping and viewport graphics in 2015.

The pattern is pretty obvious: 2011, 2013, 2015 are versions that we skipped or reverted from. AFAIK they change/break the SDK every other year, and sadly it seems that it comes at a cost. So hopes are very low for 2017. Maybe that is ok though. I mean, I wouldn't mind if they didn't come out with a new version every year. I'd rather have a production safe release every other year. Which is sort of what they are doing, if one chooses to see it that way, it's just not marketed as that way?

The subscription is going to make things awful expensive. Let's say a company has 10 stations of 3DS MAX, it'll cost them $18,000 a year, just to use. If you skip every release because you find no benefit in upgrading, it'll basically cost $36,000 to upgrade. Crazy!

[tzaar]

I was skeptical at first but 2016 works fine for us. Still on SP1 out of fear of breaking things that work, after hearing to much bad things about SP2 and 3.
Had high hopes for 2015, but went back to 2014 for production work. The layer manager/scene explorer was a nice idea, but turned out to be a nightmare. At least it works in 2016, even though it isn't exactly smooth and comfortable to rename or move things - it renames the things you want to. Also had loads of trouble with snapping and viewport graphics in 2015.

The pattern is pretty obvious: 2011, 2013, 2015 are versions that we skipped or reverted from. AFAIK they change/break the SDK every other year, and sadly it seems that it comes at a cost. So hopes are very low for 2017. Maybe that is ok though. I mean, I wouldn't mind if they didn't come out with a new version every year. I'd rather have a production safe release every other year. Which is sort of what they are doing, if one chooses to see it that way, it's just not marketed as that way?

[JezUK]

I used to have 2016 installed at the same time 2014 as I (foolishly) decided it *must* be safe to make the jump (after all, why else pay the maintenance fee...)..... each time I tried using 2016 for production work it let me down (badly) and I'd end up reverting back to using trusty ole 2014.

I then had to do a reformat of my OS hard-disk and reinstall all my software - 2016 didn't make the cut

Surely it'll be safe to jump to 2017, I mean, 3 years later (or am I paying maintenance for nothing here.....) ?

[glorybound]

I will try and see for myself. Everyone have different experiences. I think it wont crash at all for me.

let us know how it goes.

Sent from my iPad using Forum Runner

[Jiri.Matys]

I will try and see for myself. Everyone have different experiences. I think it wont crash at all for me.

[glorybound]

I just watched a "What's new in 2017" and, although it is one man's opinion, he said that it was riddled with bugs and crashes 4/5 times a day. Basically, do not use it in a production environment.

Sent from my iPad using Forum Runner

[glorybound]

Dont using it. I have Vray, Forest Pack and Relink Bitmaps. And 2016 works fine.

I'm not 100% sure that, that's the culprit. However, that's the only thing, other than what you have listed, I have installed. I install it, to use it, and before I know it the scene gets to slow to use. I'll have to experiment. I'm wondering if anyone else has the same issues when Walls&Tiles is installed.

Bobby Parker www.bobby-parker.com

[Jiri.Matys]

Dont using it. I have Vray, Forest Pack and Relink Bitmaps. And 2016 works fine.

[glorybound]

It might very well be a plugin. Do you have Walls & Tiles installed? Sometimes I think my problem start whenever I install it.

[Jiri.Matys]

I work on 2016 without any problems. Even with large scenes, its great and faster in viewports then 2014 or 2015.

[glorybound]

I don't know, but that is what I was told at an Autodesk event, several years ago. I am sure they patch things if they find them and they might mean technical support.

[dlparisi]

The whole subscription deal is so everyone is on the same version, so AD only has to support one release.

Don't they already only support one version? Have they ever came out with a SP for a previous year's version after the new one is released?

[glorybound]

Either you take advantage of AD upgrade offers now, or pay full price later. The whole subscription deal is so everyone is on the same version, so AD only has to support one release. Eventually, you'll have to upgrade and it'll be a subscription. Usually, AD's end of quarter deals are good and they are having them now.

We are thinking of upgrading to 2016, we are still on 2014 ATM.
Do you think it's worth it?
What are your major issues with 2016?

Cheers