3DS MAx 2017 crash on render completion

[OPEN_RANGE]

Hi,

I am using 3ds max 2016 with vray 3.40.02 on Windows 7 64 bit. works great and no problems.

Now I'm trying to use the latest 3ds max 2017 with vray 3.40.02 and it crashes on render completion every time. This is true at low res or high res. Also crashes regardless of save file selected or not. I completed a scene in 2016 and it renders fine. If I open that scene in 2017 it crashes as soon as the render completes.

Anyone else having this trouble? Any suggestions for trouble shooting?

Thanks for any help.

[glorybound]

Does it poof gone crash or freeze crash!

[OPEN_RANGE]

thanks for your reply! It is a poof gone crash.

[glorybound]

I have major issues, in 2017, with a 2016 model. I have to merge each time. Try merging first.

[OPEN_RANGE]

Ok. I had originally started the project in 2017. Once I got to doing some test renders it started crashing on each render so I saved the scene as a 2016 file and went back to using 2016. I'm not desperate to use 2017 but since I'm on the subscription plan and there is now vray release for 2017 I thought I might start using it. Plus I wanted to check out that noise reducing feature.

[glorybound]

I'm having pretty good luck in 2017, but folks over on the Autodesk forum are livid.

[werticus]

I have to run 2017 in windows compatibility mode just to get it to start up on windows 10. It worked fine yesterday too. :-\

[glorybound]

All you MAX beta testers (I'm a beta tester) need to be fired! How can some of this stuff make it through beta testers. Unless you folks are like me and never have time to test, all this stuff should have been vetted out in beta. The broken 'get by material' utility is shameful. I use it on every project; how could that be missed in beta? I got a script in the interim, but come on. Like I said, I'm really enjoying 2017 and haven't crashed in days, but it seems like I'm alone in that.

[werticus]

The general rule is never upgrade before the first service pack. I broke that rule because a client of mine started sending me 2016 files and i was still on 14.

[glorybound]

The first SP came out awhile ago, which is when I took the plunge.

[werticus]

Ahh well look at that, I only installed it three days ago and didn't see the option to auto install the sp1 in the installer, which 2014 had, so im not even sure if i'm running sp1 or not.

[OPEN_RANGE]

I cannot figure out how to find if I installed the 2017 service pack1 or not. do you know where that info can be found within Max?

Bobby Parker - The work shown on your website is A++. Very impressive. I would be keen to ask some questions via email about some of your technique if you are agreeable to that?

[glorybound]

You can see it in your Windows updates, or go to Autodesk's Desktop App and it'll tell you that you need SP1, and I am sure you can see in MAX, but I can't check right now.

[glorybound]

From what I understand, MAX 2017 got ugly with SP1. I know I installed it, but I am not having most of the problems that are reported, so I am going to double check. My Autodesk App says that I am up to date, so I am assuming I am running SP1.

[OPEN_RANGE]

OK I checked the Autodesk App and it says I'm up to date o I guess I also have 2017 sp1 installed. Obviously I can't work with the "poof it's gone" crash at the end of every render so I have gone back to 2016 for now.

Hopefully they will get this sorted out. I wonder if it has to do with the big visual make over of all the icons and interface stuff?

From my brief experience:

Can't add an edit poly modifier to a group of editable polys.
Crash on render end
And, per your comment, can't select by material.

those are pretty big workflow interrupters.