Is it possible to go 5 minutes without Max 2017 crashing?

[Anonymous]

I'm so over it. Doesn't matter on the job, size, what i'm doing - it will crash. I'm sending bug reports. But man I'm frustrated with this thing.
The other day it was clipping and the object was completely disappearing. I had to start a new scene and copy all the objects into the new scene so it would behave properly.
But that's the least of my frustration. Brand new job today. Very small scene. Open the layer properties -- bang! crash.

Re-doing work is growing tiresome.

[irishman_team_kilber]

what error do you get you get

you submit the bug? did you submit it on here for someone who who work for autodesk can report it to autodesk and autodesk can investigate that and give you answer or who can contact them or via email or through that stupid automatic crash thing which is useless they say they will report the bug/error and get back to you in a email whewn they never do. i don't know why autodesk has that apart of their programs because you never get a reply.

have you deleted the max.ini to see if that is corrpted?

as a last resort have you reinstalled max and it but back your file before doing this?

[Anonymous]

There's really not any one error that I get. It's different every time. A lot of the time it crashes when I go to open the layer properties - which does throw an error message, but a lot of the time it crashes unexpectedly and just asks to wait or close the program.

did you submit it on here for someone who who work for autodesk can report it to autodesk and autodesk can investigate that and give you answer or who can contact them or via email or through that stupid automatic crash thing which is useless they say they will report the bug/error and get back to you in a email whewn they never do

Nope. I've been submitting it through the dialogue that pops up everytime. The last time I opsted on here, I got told that a Service Pack was going to fix a lot of these issues. But it's still riddled with bugs for me. Worst part is I can't go back to 2016 on Windows 10.

have you deleted the max.ini to see if that is corrupted?

No. Never tried or heard of this before.

as a last resort have you reinstalled max and it but back your file before doing this?

Multiple times. I have a brand new system since the last time it ran like **** and it's still spazzing out - with brand new components.

[irishman_team_kilber]

The best thing is to report it on here for someone who works for autodesk to investigate the bug and they can pass the bug on maybe they can find a work around?

max.ini https://knowledge.autodesk.com/support/3ds-max/troubleshooting/caas/sfdcarticles/sfdcarticles/How-to... but i doubt it's a corrupted file

anyway as i am not an expert i cannot really help you with bugs

[spacefrog_]

I just finished an intense 3ds Max project with 10-12h a day shifts. Working in various scenes and tasks (modelling, materials, lighting & rendering, scene xrefs etc..). Over the whole course of those 2 weeks, Max 2017 crashed 3-4 times on me, despite having about 3 sessions open concurrently ( one doing heavy duty rendering , one for object copy&pasting ). So to answer your question: Yes, it's completely possible. But i'm still on Windows 7, and i more and more get the impression that Windows 10 and Max 2017 are no good combo. And i see you indeed are on W10 ...

[Anonymous]

Yes. Windows 10 for me. And to put things into perspective, I was running Max 2016 and Windows 7 before this and it was a dream. Infact, I can't remember it crashing once on me.
But this new version with windows 10 is a nightmare.

[Anonymous]

Yess you can use or work with 3ds max without crash.

If your 3ds max DOWNGRADE to 2016, because 3ds max 2017 too many bugs..

please visit our website, and subscribe our youtube channel, there're a lot tutorials

thank you and goodluck !!!!

[alexnode]

To answer to your initial question ... NO. 

[lightcube]

Yes*, you can run Max for days without a crash.

I moved some projects back to 2016 because there are crashes in my work when using DX shaders. Otherwise, 2017 seems to perform well here on Windows 10. For me, as long as I'm not using DX shaders, I prefer 2017 because of some of the newer functions... but if needing DX it's back to 2016.

Note that if you have problems, I would only reinstall Max as a last resort. In my experience, you will solve more problems by doing this:

1. Close Max
2. Rename this folder: C:\Users\YOURUSERNAME\AppData\Local\Autodesk\3dsMax\2017 - 64bit
3. Restart Max

The thing is that some files in that folder can sometimes get corrupted; when reinstalling Max, that folder is not deleted and updated--and if something in this folder is the source of your problems, reinstalling Max won't affect that. So I would do that before anything else.

Doing this will remove your custom UI settings (shortcuts, menus, etc). So that will need set up again to your needs.

[Anonymous]

I use 3dsMax 2017 and my solution was:

open C4D

model in C4D

render with C4D

close C4D

3dsMax will not crash when you follow these instructions 😄

other solution: 

Someone from Autodesk stand up from his bag of money you and i payed for this piece of software and will fix 3dsMax 2017 but i doubt that this will happen....

regards 

[spacefrog_]

Guys - at least if you post your anger, add your configuration ( GPU, OS, Max update version etc... )

At least then this would make the sense to form some greater picture of the problems

As i wrote Max 2017 works perfectly fine here for me on W7, with a few well known issues. Otherwise it's a great experience because of the viewport end mesh handling speedups. So add your system specs, and of course a short description of the issues you got and when/at which operations the crash happens.

[Anonymous]

There's a big problem with Geforce 900/10 series with 3ds Max 2017.

https://forums.autodesk.com/t5/3ds-max-forum/3ds-max-2017-viewport-freezing-and-stopped-working/td-p...

The "solution" is: Customize - Preferences - Viewports - Choose Driver - Nitrous Direct3D 9.

I don't think you can use vray anymore, but hey... at least it doesn't freeze and crash every 5 minutes. Autodesk needs to get their ass in gear with this one. Nvidia owns, what, 80% of the market? SP3 came out in October, and apparently they don't give a ****. Probably too focused on releasing 3ds Max 2018 and adding different icons again...

[Anonymous]

 yeh I have had this same problem, 2017 MAX must crash at least a dozen times working 10 hours a day and some days even more. I thought it was because I had to many scripts installed etc.. So I did a reformat of my drive with a fresh install and MAX was still crash happy. For me it happens a lot when I am Unwrapping in the UV editor. Also copy and pasting modifiers is really dangerous lol. Instances are dangerous too, The layer bug crash is bad too. It has crashed so much on me lately that almost everything I do I hit the save button, but even the save button seems broken,, takes for ever to save the file, and its so slow when auto backup saves it freezes and then crashes. If I use 2016 I dont have any problems. I like using 2017 because I can work with my PBR materials on the GEO

[alexnode]

Yes please go to 2016 until 2017 passes the beta phase !The fact that we are funding this farce is beyond belief.  

I see that the specs we are all posting are the most mainstream setups, I see quadros having problems, i see titans having problems and i see the mainstream 9xx, 10xx series having problems, i see windows 10 having problems ... so i guess that there is no quality control before the public release of a new version. I also see that what i was saying 4 moths ago is now being reported widely from all sorts of users. 

 I think that Autodesks beta testing program should have an overhaul. I pay the subscription to get a software that works , i spent weeks debugging and trying to figure out where the bugs come from  ...switching cards, machines , drivers etc ... 

 I found the viewport bugs in about two hours of work.  So what has gone wrong ? 

A. There are not enough developers. So they couldn't have time to fix the reported bugs. 

B. The beta testing didn't happen. Or it depends on the good will of people who might bother and have the time to install and test 

C. The developers don't know what they are doing ...

D.Or there are serious organisational faults in the team. 

 Max won't last another year like that so find out what happened. I see some nice changes in 2017 that seem hopeful , and the customer support has improved , but at the end of the day Alfred and the rest  can't write code ! They are just at the receiving end of an unpleasant situation.   

[Anonymous]

yup I defiantly feel for Alfred, he does a great job for what he has to deal with. O yeh I forgot to mention I am on Win 8.1 but like ya say no rhyme or reason to the madness. 

  The wife will be in the kitchen and I am in my office, she will hear the ding audio when MAX crashes and then I hear her laughing. So I even have to deal with that to 🙂 

[dgorsman]

---

@Anonymous wrote:

Guys - at least if you post your anger, add your configuration ( GPU, OS, Max update version etc... )

At least then this would make the sense to form some greater picture of the problems

As i wrote Max 2017 works perfectly fine here for me on W7, with a few well known issues. Otherwise it's a great experience because of the viewport end mesh handling speedups. So add your system specs, and of course a short description of the issues you got and when/at which operations the crash happens.

---

GPU driver version would also be of benefit.

I'm suspecting (aside from the usual program problems) this is going to fall into a gap caused by cumulative problems between Win 7/8 => Win 10, DirectX9 => DirectX11, and old model GPU/new model GPU combined with driver updates (or not).

[Anonymous]

Well i can't speak for anyone else but my configuration has been in my signature since the start of this thread.
All my drivers are up to date.
When i asked, i was told max 17 and windows 10 aren't compatible with one another. Going back to windows 7 isn't a realistic option either considering all the other programs I'm using - and frankly, i shouldn't have to.

[Alfred.DeFlaminis]

I wanted to touch base here and let you know that the developers are now able to repro these problems and are currently working on fixing them.  It's hard to read these threads sometimes because I do want everything to work perfectly for everyone and my goal is to get us all there.  

What is really important to me is that you continue to report issues as you are having them, in whatever manner you feel comfortable.  It wasn't until I had multiple threads about these issues that I started to find the patterns and collect info into that thread that @Anonymous linked in the post above.  I share some of the blame for delays on fixing these issues because I didn't notice the pattern sooner and it's my job to ring the alarm. 

Thank you for your kind words @Anonymous, I am often humbled by the nice things people write about me in these threads.  It makes me want to push even harder and never let up.  I want you all to know that I also use Max outside of work for various projects and it's just as important to me on a freelance level as it is on a support level to find and log issues so that the overall experience is improved for everyone.

I am grateful for all of you taking the time to list details and help me to log all the info possible.  These threads and others that you have taken time to communicate with me in have resulted in many of these things getting fixed and addressed.  Thank you all for sharing your thoughts and experiences with me so I can share that upward.  I am grateful to have a user base that communicates as much as this one.

Best Regards,

[Anonymous]

I've read SO  many things about max 2017 being buggy that iv'e not even downloaded it

i'm sticking with max 2016 until either Autodesk sort this mess out or max 2018 is a better option and i'll skip  it completely.

[gandhics]

I saw at ChaosGroup forum that someone mentioned 970 has vram issue with 2017.

Basically the way nvidia configure vram for 970 is not compatible with 2017.

BTW, it is hard to catch this bug because not everyone is having problem.

We moved to 2017 since last September, and 2017 is rock solid for us(We actually had to move from 2016 to get some bug fixes).

We usually have more then 10,000+ objects in the scene with 2+ millions of polys.

We are mostly using windows 7.

But, we have been running a windows 10 workstation with 1070 for a month. No problem yet.

2 days ago I also got windows 10 + TitanX workstation. I'll see how it goes..