Backwards compatibility

[Macker]

Hey guys,

There are two of us 3D blokes in our office, both using railclone and forest pro on max 2016 with VRay 3.4, and two render nodes running the same.

I want to upgrade to max 2017, and to the latest versions of railclone, forest pro and Vray, along with the render nodes however my colleague is mid-project and doesn't want to upgrade yet. I am wondering if once the render nodes are updated if they are backwards compatible?

How will the VRay spawner work on the nodes? Will we have to have two spawners running per node? One for 2016 and one for 2017?

[werticus]

2017 isnt there yet, stick with 2016 for at least one more service pack imo.

[Zdravko.Keremidchiev]

I am wondering if once the render nodes are updated if they are backwards compatible?

It will be best to stick with one V-Ray version when doing network/DR rendering otherwise you might end up with an inconsistent output. But you can also have different V-Ray version on different 3ds Max versions. In example V-Ray 3.2 on Max 2016 and V-Ray 3.4 on Max 2017.

How will the VRay spawner work on the nodes? Will we have to have two spawners running per node? One for 2016 and one for 2017?

You can start two V-Ray Spawners on two different ports. In example one on the default 20204 and one on 20205: vrayspawner2016.exe -server -port=20205