3ds max 2014 crashes

[Morbid Angel]

Just curious, its not a show stopper by any means but I've got a new system, clean install everything. I got max 13 and max 14 installed side by side. Max 13 works just fine. When I try to start max 14, it crashes right away as soon as splash screen appears, I don't even have time to do anything with it

Any idea why this might be happening? Tried reinstall, service pack etc nothing helps...

[MoonDoggie]

I've had problems going to 2014 with a bunch of edit polys (modifiers) in a previously created scene. Make sure you have SP5 installed and for shits and grins collapse your scene and then open in 2014.

[jacksc02]

Find your 3dsmax.ini file and delete it.

[Morbid Angel]

Find your 3dsmax.ini file and delete it.

Yeah did that, no help.

MoonDoggie, max won't even start going past splash screen. Just click 3ds max icon, splash appears, then max crashes.

[Donald2B]

Do you have enough time to read whats loading at the bottom of the splash screen? Is it getting to the point where it's verifying/checking the license? Or earlier? That may help you track down where in the start-up process it's dying.

I think I have had this problem before, but I don't remember what I did to resolve it. For some reason, deleting the entire Max2014 directory in the user folder is jumping into my head. I think you should be able to delete that entire folder as it contains most of the startup information, and it should be automatically recreated once you start Max again.

[Morbid Angel]

So...I had to do a rush job in 3ds max 2014. And I had to use this particular machine as DR slave. Well, I came against this issue once more. After 2 days of banging head I came across this post:

http://forums.autodesk.com/t5/Instal...e/td-p/3929893

It solved the issue.

Shocker.

[Franx]

Hmm, that one is bookmarked.
Thanks Dimitry. Didnt happen yet, but one never knows...

[Morbid Angel]

Another bit of useful info. After getting max 14 to start, the spawner would not. It would just exit after I run it immediately. It turned out that I needed to put on service pack 2, before it started to work and now works as expected!

Onto another issue