3dsmax 2017

[Deflaminis]

Hello everyone,

The best way to get your bugs fixed for max 2017 is to post your problems in The Area. I just recently began working at Autodesk (couple weeks) and it's my job to help people with technical problems and log/verify the bugs. I will do everything I can to help you. They hired me specifically to work on these sorts of things.

I see some people describing errors in this thread that I *know* I don't have a record of, I wish there was some way to get you to share those errors (and how they happen) on The Area. I could attempt to enter them in from what I've read here, but the Vray forums is no place for me to start asking questions about how they happen and how to replicate them. Developer and product managers want this info and I'm spending all day every day collecting it for them on the Area.

For what it's worth SP2 came out recently and fixes a lot of things. No, not the "select by material" bug, however if you don't use the scene explorer and go with the old list select (faster anyways, and better imho), then the problem won't affect you. Also, you can select through transform gizmos, you just have to click twice, with a small hesitation between clicks. Like how windows renames files. (Same exact method really.)

I'm not going to continue to post in this thread, but if you want the bugs fixed or need support, please use the Area Max forums. Thank you.

AJ

[Alex_M]

Another problem for us is you can't select objects anymore if your transform gizmo covers the object when you click to select it. This was possible in Max 2016 and older. Along with the Select by Material bug, this is another big restraint for us. We won't be transitioning until these are fixed.

[Nearl]

I switched over to 2017 SP2 yesterday... no major WTFs yet...minus a registry error that would crash scenes created in 2016, but we seem to have fixed that.

Here is the fix....

Run Command Prompt (Admin)

Paste:

cd "C:\Program Files\Autodesk\3ds Max 2016"

regsvr32 /u MAXComponents.dll

regsvr32 MAXComponents.dll

[jacksc02]

Something sounds wrong there!
Does it save that slowly locally?

[werticus]

I've not installed sp2 yet, but my max 2017 is saving files very slowly. I just got a new router tho, so i need to check that too.

It takes 5 mins to save a file that is under 100mb

[Nicinus]

Are you using SP2?

[alexander.kazandzhiev]

Hello,

I cannot reproduce it here. Can you save a scene with the 3ds Max 2016 that would crash the 2017 and attach it here or send it to alexander.kazandzhiev@chaosgroup.com? Which V-Ray version you are using on both of the 3ds Max?

Best regards,
Alexander

[3dcrgr]

Anyone else experience some odd crashes caused by UI with 3ds max 2017?
For example if I open a fresh scene it will always work ok.
If I open a scene made in 2016 and hit render - 3ds max will crash badly even without letting a chance for V-Ray to load.

If I delete the "2016 - 64bit" folder in "C:\Users\**USER**\AppData\Local\Autodesk\3dsM ax" then the scene will render just fine.
But, if I make the slightest change, for example change custom UI to MAX.vray - ame.light...... once again the same crash.

anyone else??

[glorybound]

http://maxplugins.de/max2017.php

Awesome, thanks!

[Companioncube]

I know V-Ray, Forest Pro, and RailClone are ready for 3DS MAX 2017. is there an active list of plug-ins that work with it?

http://maxplugins.de/max2017.php

[glorybound]

I know V-Ray, Forest Pro, and RailClone are ready for 3DS MAX 2017. is there an active list of plug-ins that work with it?

[jstrob]

Too bad max can't have a journal with daylies publication like Houdini because of all the plugins max is depending on... At least we have daylies for vray!
http://archive.sidefx.com/index.php?...213&page=index

[Dave_Wortley]

well, now that there is a vray version i tired it and so far its not too bad. you have to get used to the interface but thats ok for me, what really bugs me - and this is something i wont get used to - is that i cant use a comma anymore. even tho every value in max show up with a comma it doesnt accept inputs using a comma, i have to use a point - which is very bad cause of the german keyboard layout. this was and is still working in all our previous max versions. sp1 didnt solved the problem
guess i stay away from it till this is solved...

They are aware of this.....

[Olli96]

well, now that there is a vray version i tired it and so far its not too bad. you have to get used to the interface but thats ok for me, what really bugs me - and this is something i wont get used to - is that i cant use a comma anymore. even tho every value in max show up with a comma it doesnt accept inputs using a comma, i have to use a point - which is very bad cause of the german keyboard layout. this was and is still working in all our previous max versions. sp1 didnt solved the problem
guess i stay away from it till this is solved...

[Nearl]

Jesus christ, they call that a service pack? More like a quick patch for some bugs.

HAHAHAHAHA! Agreed