Max 2017 - anybody having success with it?

[kosso_olli]

But if you read the area forum, youll see there are people there who apparently have none of these issues - i guess these are just payed AD trolls

No troll here. I have been using 2017 for 7 months, and I don't get any strange hickups. At least not more than with any other version of Max. Have to say that I am kind of an old school Max user, so I get rid of new style material browser, slate and select by name editor as soon as I install a new release. 2017 is actually quite fast on heavy poly scenes.

[Lupaz]

Same as you really, tried it on a couple of projects earlier in the year and ended up saving as Max 2016. It's just wasn't usable for me.

Same here...

[Morbid Angel]

Working in max is like going to watch a hyped up movie with high expectations only to get disappointed. I think its been ok for us here, I mostly have vray / fp stability issues, but its expected being on a beta

[gandhics]

Guys... please give some more details about 2017 show stopper.
You might have one more chance for SP.

[AJ Jefferies]

2017 is the most unstable version I've used in a long time, and I very rarely have any complaints about Max.

Things that have caught me with 2017 so far :

-Changing the number of segments in any primitive after creation will (randomly) corrupt the object
-Selecting objects can be extremely hit and miss, especially V-ray lights.
-Closing a window will sometimes cause Max to exit without warning - render options, VFB, slate editor...etc.
-Unable to see the edge of thin objects (planes for example) from the side, in any viewport mode.
-Select and Place will randomly ignore geometry

There's more than that, but that's what immediately sprung to mind.

[Ihno]

I crash sometimes when I'm unwarping, especially relax seems to be unstable sometimes.
Also the FBX exporter chrashes sometimes.. I even had to get back to 2016 for export.
But thats all, I like 2017.
Most (by far) crashes here, are related to Vray IPR these days.

[gandhics]

2017 is the most unstable version I've used in a long time, and I very rarely have any complaints about Max.

Things that have caught me with 2017 so far :

-Changing the number of segments in any primitive after creation will (randomly) corrupt the object
-Selecting objects can be extremely hit and miss, especially V-ray lights.
-Closing a window will sometimes cause Max to exit without warning - render options, VFB, slate editor...etc.
-Unable to see the edge of thin objects (planes for example) from the side, in any viewport mode.
-Select and Place will randomly ignore geometry

There's more than that, but that's what immediately sprung to mind.

Do u have SP or PU installed?
May I get HW spec? OS?
Any step to reproduce?

[vlado]

Most (by far) crashes here, are related to Vray IPR these days.

I'd like to know more about these?

Best regards,
Vlado

[Ihno]

Yes I know, but I can't really say when this is happening. If I find way to reproduce it, I'll tell you how.
I had a hard time with a scene with camera texture with animated (tga sequence with alpha) texture. Especially when changing current frame but not allways.
Will try to keep my eyes more open when I come back to that scene again. Which might be this weekend.

[vlado]

Ok. Even crash dumps are super helpful.

Best regards,
Vlado

[viscorbel]

Where would one find these crash dumps? I'm having issues of completely random crashes with ipr as well, stopped using it until it becomes more stable.

Ok. Even crash dumps are super helpful.

Best regards,
Vlado

[Deflaminis]

Where would one find these crash dumps? I'm having issues of completely random crashes with ipr as well, stopped using it until it becomes more stable.

Usually at C:\Users\%username%\AppData\Local\Temp

[gandhics]

https://forums.autodesk.com/t5/3ds-m...018112#M135660
Try to remove GeForce Experience!
You may experience the true force of 2017.