3dsmax 2017

[jstrob]

I just tested select by material and it's not working here either.

I had many bugs with max plugins and for sure state sets but many of them have been solved since or at least improved. for example RPManager was not working anymore because of a checkbox that was frozen but it now works but still have some display and slowness problem. Since that was the most important part of my pipeline I couldn't use max 2017 because of that so now I have to test the other plugins one by one or wait until someone test them before me.

As soon as everything works for me in 2016 I will stay with it.

[Ihno]

I am using a scriptthat replaces Select by Material, which works exactly the same. It's a Soulburn script.

Ah, cool. I installed them recently but didnt had the time to dive into yet.

Is it really broken ?? I mean select the hardware still does not work ????

Yes, actually it does nothing. At least it dosnt crash max. I think we should be happy about that^^

[rikou]

Actually the viewport performance is better. But there is a serious bug that might break your workflow; Select by Material isn't working (yet). At least not here...

Is it really broken ?? I mean select the hardware still does not work ????

it's crazy !!! Soulburn script as a great tool but it's more than that !! use it as "a dressing on the wounds" of 3ds max 2017 is not a solution....

[glorybound]

I am using a scriptthat replaces Select by Material, which works exactly the same. It's a Soulburn script.

[Ihno]

Whats IPR?

https://www.youtube.com/watch?v=tK2eYCaMkI0

For Archiviz guys is there any advantage to moving to 2017 (now that SP2 is out) from 2016?
Is it faster? Better viewport performance? Is there anything in it that you think is worth making the jump apart from just having the current version?

Actually the viewport performance is better. But there is a serious bug that might break your workflow; Select by Material isn't working (yet). At least not here...

[mitviz]

Whats IPR?

[Vizioen]

I don't have it but the only thing I can think of is that Vray has IPR in the nightlies in 2017.

[coolhand78]

For Archiviz guys is there any advantage to moving to 2017 (now that SP2 is out) from 2016?
Is it faster? Better viewport performance? Is there anything in it that you think is worth making the jump apart from just having the current version?

[pixelplume]

thanks for the link....I added to it

[glorybound]

AMEN! I have been complaining about the checkerboard from hell, so I have to work in clay mode, for a couple months now. Here's mine rant:

http://forums.autodesk.com/t5/3ds-ma...482080#M116854

[pixelplume]

what section of the area forums is best to post complaints?
- display drivers crashes things a bunch and I wind up working in "clay" mode most of the time
- sometimes it will not render the current view.....It get's stuck on "render last" until I restart max

[jstrob]

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

The only problem is when the bugs are probably related to plugins we must contact each plugin developer first. I will try to go on the Area to see if I get answers about how to make the state sets work.

[jstrob]

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

What do you use for render passes?

[Alex_M]

Awesome, glad to hear that you can help with these issues. By the way, I always log bugs when I spot them. I use the official bug report page. What would you suggest, is it better to also along with logging we mention them on the Area forum? I would certainly do this if it helped speed up the process of fixing the bugs.

Thanks for your help!

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'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

[lukx]

roger that