This page provides information on how the latest version of V-Ray handles scenes saved with previous versions of V-Ray.
V-Ray 7 adds a number of rendering optimization features. However, for compatibility reasons, some features and workflows have been adjusted and are discussed in detail below.
V-Ray for Rhino is not forward-compatible, meaning projects done with V-Ray 6 and V-Ray 7 are not guaranteed to work with previous V-Ray versions. If a project is opened using an older V-Ray version than the one it was created with, a prompt message offers wiping all V-Ray data to ensure file stability.
When opening Rhino for the first time right after installing V-Ray, some or all assets of the scene you load may be missing.
If this happens, ensure V-Ray is set as the current renderer and then close Rhino. All assets load correctly from then on.
Starting with V-Ray 7 the CUDA and RTX are replaced with a GPU tab for render engine. V-Ray GPU uses NVidia CUDA or RTX device(s) to perform the raytracing calculations. The GPU engine can be specified from the V-Ray GPU rollout.
The Portal Light option in V-Ray Rectangle light is now a legacy option and is no longer exposed in the UI. Rectangle lights in files saved with previous V-Ray versions and this option enabled will still have it available. Regardless, for best performance consider disabling it and using the Adaptive Dome Light option instead.
Starting with V-Ray 6, the Fresnel formula is now calculated more precisely. As a result, some materials, mainly metallic ones, may render slightly differently (with more physically-accurate reflections).
Starting with V-Ray 6, the V-Ray Preset Material Library is part of the Chaos Cosmos Browser. Materials that have already been downloaded with any earlier V-Ray version remain unchanged and can still be loaded as a custom folder.
Starting with V-Ray 7, the Binding section in the materials is now renamed to Viewport Display.
Scenes set up using Enscape will now render in V-Ray. Materials and even the Enscape assets will be automatically handled by V-Ray providing a great starting point when transitioning from the Enscape design stage to the high-end visualization in V-Ray. For more information, go to Enscape Compatibility.
Starting with V-Ray 5.20.01, V-Ray special objects (Fur/Clipper/Displacement/Mesh Light/Scatter) are not deleted from the Asset Editor, when the last item with the corresponding special object assigned to it, is deleted from the viewport.
Starting with V-Ray 7 there is a new Remove from Selection function. It removes the Special object applied on another object.
Loading Rig components from projects created with V-Ray 6.10.00 into newer versions, requires parameter rewiring. In V-Ray 6.10.01 some input and output parameters of the Grasshopper Rig Light components have been rearranged. Due to this reason, when a project created with the previous version is opened, the parameters appear to not be wired properly. In such cases, rewire the parameters manually for proper project performance.
V-Ray 5 for Rhino licenses also work with V-Ray Next, allowing anyone who purchases an upgrade, to complete unfinished projects using V-Ray Next if needed.
Please note that customer support is available only for V-Ray 7 and V-Ray 6. Earlier versions are no longer supported. |
Materials and other V-Ray data saved with V-Ray older than v2.0 will not be read.
If you need to migrate an outdated scene, you will need to perform a 2-step migration - first one to V-Ray 3.6 and a second one to V-Ray 5.
To do so, first visit download.chaos.com, enable the Show older versions checkbox, and download V-Ray 3.6.
Then, uninstall your current version of V-Ray for Rhino and install v 3.6 instead.
Open your outdated project, inspect the scene materials through the V-Ray Asset Editor, and save the project. This will trigger automatic V-Ray data migration. Repeat the steps for V-Ray 5.
Note that in order to work with V-Ray 5 builds, you need to have the proper License Server. For more information about the License Server, see Installing the License Server.