Persistent modeling crashes with 2017

[Anonymous]

I've been giving Max 2017 another go since installing SP3. Unfortunately, I'm still seeing lots of random modeling crashes. Mostly when using snapping in subobject mode in orthographic view. Max will freeze for a few seconds and crash, but it allows me to save a recovery file, so no work gets lost.

Still, it is deadly for the workflow.

I've been sending reports every time and making sure these are marked with my email address. Can someone at the Autodesk end look into them and let me know what they think?

[Anonymous]

is there any chance to get 2017 fixed and usable before 2018 is out or should i wait for 2018 to be published, wait for 3sp, 1pu, 1 security fix and then hope that the 2019 is somehow usable?

[pokoy]

THAT is a good question. 2017 is broken so badly in so many places, these threads are now months old, almost everyone has issues. The silence from Autodesk can only mean that 2017 is not fixable.

[Anonymous]

Of course it's not getting fixed. The release of Max 2018 is happening any day now. Developers are probably working on SP1 for 2018 by now. Forget 2017. You can write it off. And I'm sure not going to install 2018 for a very long time to make sure it is bug and crash-free when I do.

[Anonymous]

i got the same feelings you have, the only problem is that the bucks we paid for it were not the monopoli ones so Autodesk should refund users for not being able to use the 2018 release in production

[Anonymous]

Absolutely. People should ask. I made my case and got a 90-day extension of my maintenance plan as a partial refund. Not a full refund but not nothing either.

[Anonymous]

i'm gonna talk to my reseller ASAP and link this 3ad

[Anonymous]

I got no luck with my reseller but with AD directly. Prepare to document your inability to use the software. For me, I had tons of CER reports and all my comments here as evidence. 

[jens.gehrcken]

Yes i realized that behavior also with 2017 and mostly with polygon modelling and vertex snapping (3D mode) when snapping in 2D mode its not happening or not often

[jens.gehrcken]

Hoped that it might be resolved in 2018... But yet fear there will be other issues with late rollouts​ of certain plugins my work is based on.

I did send in several crash reports - just today find this forum thread... Well at least I'm not alone

[spacefrog_]

---

@Anonymous wrote:

Of course it's not getting fixed. The release of Max 2018 is happening any day now. Developers are probably working on SP1 for 2018 by now. Forget 2017. You can write it off. And I'm sure not going to install 2018 for a very long time to make sure it is bug and crash-free when I do.

---

Come on Betrand - Its already been confirmed that they work on another service pack for Max 2017

I more and more get the impression that the current silence on all fronts from the 3ds Max team is related to the fact that they can't do anything anyways against that huge backlash and negativity that is caused by the recent pricing and licensing announcements and because of the meager Max 2018 release features. Thus i think they stash the good eggs in the basket for some while to reveal them later on ...

[Anonymous]

@Alfred.DeFlaminis any news on this?

For the record, I have updated my BIOS to the latest version and also changed my GPU, but within 5 minutes of modeling I get the vertex snap sub-object modeling crash again.

[Alfred.DeFlaminis]

This happened in 2018?    

My notes say this is fixed in 2018, can you please submit a CER when it happens next?  I'll look it up... 

Best Regards,

[Anonymous]

Hi Alfred. Nope, I'm not considering upgrading to 2018. This happened into 2017. I did send a CER but forgot to put my email on it. I will do so next time.

[Alfred.DeFlaminis]

Phew, @Anonymous.  Thanks for the clarification.  This hasn't been addressed in 2017 yet, but I really hope to see it updated soon.  Thanks for the update and confirmation about the version.  

Best Regards,

[Anonymous]

Hey @Alfred.DeFlaminis. Any news on this crucial 2017 bug fix? Would still be curious to try it...

[Alfred.DeFlaminis]

It's being worked on which is all I can really say @Anonymous.  I will always go to bat for you and the users of this forum.  Once I've done that, I can only wait for the issue to get resolved.  I am antsy to get this fixed as well because I don't want you or any other users unhappy.

Best Regards,

[Anonymous]

I know I'm being a bit of a broken record here, but does Autodesk still intend to fix the non-usable Max 2017 or has this train left the station?

[pokoy]

I'm sure they are but they first need to figure out a way to make us pay for it.

Frankly, I've given up on this. I have never seen a company handling issues and maintenance of their software in such an incompetent way, it's almost insulting.

[Anonymous]

I'd be curious how many people use 2017 and 2018. Surely just a handful, I would think, given 2017 is broken and virtually no external plugins--which would be the main reason for anyone to use Max--have yet been updated for 2018. 

[Anonymous]

Its a lot worse than just insulting. You should also see the 2018 release
of Acad LT. Its really identical to 2017 - only real difference is we have
to pay to switch a "7" to an "8"