'vray_adv_31003_max2015_x64.exe' seems to work in Max 2016 at least, for me.

[RobH22]

One thing I have historically disliked each year was getting Max and then having it take 6-months for all of my plug-in and script vendors to update them so I can use Max.

I've been checking back here looking for an update and have found none and hardly any chat about Max 2016 at all. So, I figured I'd just install 'vray_adv_31003_max2015_x64.exe' and see what happens in Max 2016. I have to say, I've been working all day, and so far, all is well. I've even installed things like ForestPro and a few other plugins. They are all working.

Maybe the Max development team has stopped breaking the base code of Max each year for the time being. I did notice Max 2015 was more friendly to plugins as I was upgrading from Max 2014. So, maybe Max 2016 will accept anything that Max 2015 could use. I've now installed about a dozen ScriptSpot scripts and all of them are fine without exception.

So, do this at your own risk, but if you want to use VRay 3 in Max 2016, give it a try. I'm having no issues as of day one. And if all goes well, you won't see me back here with egg on my face (how many subdivs for egg textures...lol...).

[Deflaminis]

They seem to be doing 2 year increments with plugin compatibility. 2014 uses 2013 plugins, and 2016 can use 2015 plugins.

I would imagine that the issue would crop up maybe with the new autodesk physical camera or things that have changed in that area, but it's cool that this worked for you. You should be able to use all your 2015 plugins in 2016 minus a few according to AD, for what that's worth.

Good on ya for blazing this trail though, kudos.

[RobH22]

You should be able to use all your 2015 plugins in 2016 minus a few according to AD, for what that's worth.

Sure, agreed.

Was there a list you found at AD mentioning compatibilities?

[Deflaminis]

It's been in the general buzz around various forums, I found this link that talked about it too: http://getcoreinterface.typepad.com/...-max-2016.html

[RobH22]

Great info. Thanks...

[krassi]

Hi there!

I also use vray 3 with Max 2016 .. it works good.. but i am having some crazy trouble with old scenes.. some objects cause a crash with irradience calculation that worked for 2 years like a charm and some scenes wont open on another computer wich is bad for me because i have 3 Workstations and only one that i can use..
i think i will carefully install vray again with the new license server because i cant optain a licence on the network on the 2 other computers..

soo i hope the new vray will be out soon because the new 3dsmax is really a good "even number release" .. the odd numbers were usually waste of installation time.. and i hope these crashes will be gone.. could of course be Interaction with forestpack and some other plugins i use.. because some forestpack things that allways work also cause crashes..

best regards, daniel!

[vlado]

Daniel, pls email me to vlado@chaosgroup.com so that we can get you a proper 2016 plugin - I'd very grateful if you can report any issues so that we can fix them.

Best regards,
Vlado

[trixian]

I have been hesitant to install the vray 2015 version, as I tested with the corona alpha initially on my fresh max2016, but there seems to be some issues with direct light (like a really large shadow bias) that doesn't show up in max2015.
This kinda scared me from trying any further and installing vray, and resigned to waiting for the updated build.

[tashko.zashev]

I have been hesitant to install the vray 2015 version, as I tested with the corona alpha initially on my fresh max2016, but there seems to be some issues with direct light (like a really large shadow bias) that doesn't show up in max2015.
This kinda scared me from trying any further and installing vray, and resigned to waiting for the updated build.

Yes, that would be the best option if you are not in a rush.

[krassi]

hiho!

ohh i found something interesting regarding my crashes!

i merged my old scene completely in a empty new 2016 scene... and the stuff was rendering again like it used to.. max 2016 is really a typical "even number release"... a good one as far as i can say..

best regards, daniel

[tashko.zashev]

hiho!

ohh i found something interesting regarding my crashes!

i merged my old scene completely in a empty new 2016 scene... and the stuff was rendering again like it used to.. max 2016 is really a typical "even number release"... a good one as far as i can say..

best regards, daniel

Good to hear that. By the way, did you try to reset the V-Ray settings for the original scene >> assign the Default scan line renderer and then switch back to V-Ray adv.

[krassi]

hiho!

well i of course did not try this ... well right now its working like intended.. all plugs are 2015 versions but run good
but thats a good idea! i will also use this to completly update my standard archviz setups, optimize materials and other stuff...

best regards, daniel!

[alexyork]

How are people finding 2016 so far? Any worthwhile changes? The whole new Layer Manager fills me with dread, along with the usual inevitable process to revert most of the UI back to the old (and superior!) setup.

[trixian]

What's wrong with the new additions to the layer manager?
I have been forced to use it in 2015 after Peter Jansen stopped developing outliner, and yes, in 2015 it is pretty retarded (but workable), but should be improved upon in 2016. The fact that merging and xrefing retains your layer hierarchy is (apart from an obvious must) a great addition.

[alexyork]

What's wrong with the new additions to the layer manager?
I have been forced to use it in 2015 after Peter Jansen stopped developing outliner, and yes, in 2015 it is pretty retarded (but workable), but should be improved upon in 2016. The fact that merging and xrefing retains your layer hierarchy is (apart from an obvious must) a great addition.

I've not used 2016 yet, or 2015 for that matter, so I've no direct experience, but from what I've heard the LM in 2015 is terrible, so I'm really hoping it's been improved in 2016.