Install 3.2 along side of 2.4?

Doesn’t appear to be possible. I un-ticked “remove previous versions”, but when I launch max, I get a slew of duplicate class ID warnings. Only 3.2 RT is an option in the renderer selector, along with both flavors or 2.4.

My hope was to be able to keep 2.4 around for some older work on 2014 along side of 3.2. Is this not possible?

Maybe 2 max installs, or maybe a diff login?

Not out of the box. As Deflaminis suggested many people go with the 2 Max Versions approach. You can also deploy VRay seperate from max and then make Versions switchable.
You have to create these deployments yourself though and there are some caveats (e.g. the vrmat editor does not work out of the box, some scripts are broken etc).

See also: Chaos Docs

Cheers,
Thorsten

I decided to keep 2.4 running on 2014 and set my sights on running 3.2 on 2016. Hoping SP1 comes out soon…

I too have decided to download and install Max2016 with VRay 3.2.

Hopefully it won’t cock up my already installed Max2014 with Vray 3.0.

Hope you have better luck with 2016 / 3.2 than me. I can only get two frames out of 280 before it crashes. I’m using DBR across two nodes. Argh.

My crashing issue apparently has to do with BB 2016. I just went back to 2014 / 2.4 and its doing the same thing. I guess I’ll have to revert back to BB 2014.

btw - is there any way to have both BB 2014 and BB 2016 installed? Doesn’t seem like it.

Have you tried to completely remove all BB versions from your machines and install BB2016 again? Do you have any problems with our DR without mixing it with BB?

I seemed to have gotten it working now. It turns out that (I think) it was an issue with the scene itself in that the focal length of the Vray camera was supposed to change during the animation sequence. So I redid my camera moves with the same focal length for the entire sequence and that seems to have fixed it. So I don’t know if that’s a bug, or if you generally can’t do that. The other potential fix would have been ticking “Save strings in legacy non-scene files using UTF8” in Preferences/Files. Out of shear frustration, I was prepping the file to send off to Rebus and their software flagged that as an error that it needed to be checked. So that too might have been something.

Anyhow, single frames that were taking about 23min with 2014/2.4 are now coming in at around 6:15ea with 2016 and 3.22. I’ve put out about 100 frames so far overnight, and I am absolutely blown away by the performance, especially how fast pre-passes are! Thank You!

It turns out that (I think) it was an issue with the scene itself in that the focal length of the Vray camera was supposed to change during the animation sequence. So I redid my camera moves with the same focal length for the entire sequence and that seems to have fixed it. So I don’t know if that’s a bug, or if you generally can’t do that.

Let me check if the crash can be reproduced here.

Anyhow, single frames that were taking about 23min with 2014/2.4 are now coming in at around 6:15ea with 2016 and 3.22. I’ve put out about 100 frames so far overnight, and I am absolutely blown away by the performance, especially how fast pre-passes are! Thank You!

Thanks for sharing your render results. Lot of work has been done by our dev team on V-Ray 3, especially on the render speed improvements and optimizations.

There is no crashes in my render tests. Would it be possible to send me your scene file ?
Could be just the camera and some dummy objects inside.

I just sent you a PM with a link.

Thanks.

Please send us the files to support@chaosgroup.com