This page provides information on how the latest version of V-Ray handles scenes saved with previous versions of V-Ray.
V-Ray Next adds a number of rendering optimization features. However, for compatibility reasons, some features and workflows have been adjusted and are discussed in detail below.
If you are migrating from an older version of V-Ray to V-Ray 3.6, visit the Migrating from Previous Versions page for V-Ray 3.6 for Rhino.
V-Ray for Rhino is not forward-compatible, meaning projects done with V-Ray Next will not be read correctly with V-Ray 3.6 or older versions. If a project is opened using an older V-Ray version than the one it was created with a prompt message will offer wiping all V-Ray data to ensure file stability.
V-Ray Next for Rhino licenses also work with V-Ray 3.6, allowing anyone who purchases an upgrade to complete unfinished projects using V-Ray 3.6 if needed.
Opening a Scene
If a project is opened using an older V-Ray version than the one it was created with, a prompt message will offer to wipe all V-Ray data to ensure file stability.
Note that this occurs only when opening projects. Importing or referencing projects with outdated V-Ray data triggers the migration process for the loaded data without any prompt.
When a scene saved with V-Ray version 3.6 or older is loaded in Rhino (using V-Ray Next), an upgrade script will go through all the scene assets and features to account for incompatibilities. All lights, materials, and special objects will be upgraded from groups to a new component definition system. This upgrade can take some time, but only happens the first time the scene is opened in Rhino with V-Ray Next. When the scene is saved, the updates are saved with it.
When opening V-Ray Next for the very first time in Rhino if the scene assets are missing, close Rhino. Open a new scene, set current renderer to V-Ray, and all assets will load correctly from then on.
V-Ray 3 scenes with custom aspect ratio and safe frames enabled may have their width or height size reverted to default values (640/480). This may also cause incorrect output if submitted for Cloud rendering. To account for this inconsistency, it is best to manually set the output size of affected scenes after opening them in V-Ray Next.
The internal material structure used in V-Ray for Rhino is updated and modernized. This in turn leads to the material asset UI being updated.
Reflection, Refraction and Diffuse material layers' Transparency parameters are switched to Opacity controls for consistency. Any old materials containing such layers will be migrated automatically to the new internal structure.
Material Environment Overrides
The material Environment Overrides rollout has been removed. This functionality has been shifted to the Override material which now contains an Environment map slot.
Stochastic Flakes material
The Stochastic Flakes material can no longer be created from the Asset Editor’s Create menu. Create a Generic material, remove its default V-Ray Mtl layer and add a Stochastic Flakes layer to use it.
Due to the deprecation of the MtlASGVIS plugin VRScene files exported with V-Ray 3.6 or earlier are missing material options such as displacement/bump.
The new built-in material(s) make the use of Multi-materials for proxies obsolete, simplifying the workflow process and storing proxy meshes.
Old projects that contain proxy meshes will retain their multi-material and sub-materials, but newly created or loaded proxies will utilize the new ones. There is no automatic migration. However, manually editing the proxy file settings, e.g. toggling the Proxy's "Materials" section off and on, will populate an old proxy list
Randomize Material ID Colors Tool
Found in the Rhino menu V-Ray > Tools, this tool allows assignment of random color IDs to all materials. This provides a workaround for materials from v2.0 scenes which all have their color IDs set to black.
Note that it will not affect Material ID numbers, which by default are set to 0.
Reflection/Refraction Max Depth
Negative material reflection and refraction trace depth values are no longer permitted. Any material parameters with such values are reset to the default value of 5.
Preset Library Assets
The Preset Material Library location in V-Ray Next is changed, which may result in UI markers about missing files of associated Bitmap textures. Despite these warnings, V-Ray automatically resolves each incorrect library file path to make sure the render output remains the same.
Legacy ASGVIS Plugins
In V-Ray Next, Update 1, the legacy TexFalloffASGVIS, TexNoiseASGVIS and MtlAngleBlend plugins are automatically migrated. Some minor blend variations from the original result is expected.
The legacy Two Sided material from V-Ray 2.0 is also migrated automatically to a newer plugin. Functionality remains the same. If a material visible only from one side has previously been achieved by leaving the 2-sided "Back material" slot empty, from V-Ray Next, Update 1 onwards, this is done by leaving the "Front material" slot empty instead.
Material .vismat files
There are two types of legacy .vismat files. The ones created prior to V-Ray 2.0 are in binary format, while the more recent ones are in xml. Support for .vismat files is no longer available. Nevertheless, the newer type of .vismat files can be loaded in V-Ray by renaming their file type extension from .vismat to .vrmat
Rhino Materials Synchronization
In V-Ray Next, Update 1, V-Ray materials can be created from the Rhino UI and Rhino materials can be converted into V-Ray ones by changing the material type. V-Ray materials can be converted back into Rhino ones, however, Rhino does not support any of their additional V-Ray features, thus this is not recommended as it can cause loss of V-Ray data. An example is the V-Ray procedural textures which are not supported and cannot be displayed in Rhino's viewport.
Due to this synchronization, material conflict resolutions (commands and menu UI) are no longer available on V-Ray's side. All is handled automatically by Rhino.
The V-Ray Clipper's Include/Exclude list is no longer available. Including or excluding scene objects is now managed in Rhino’s V-Ray properties panel. Pick objects to be added to the list by selecting them in the viewport or using one of the native Rhino selection functions like ‘By Layer’, ‘By Color’, ‘By Name’ etc. Use the Select Objects function to see what is already in the list even for Clippers migrated from V-Ray 3.
Fur strands in the viewport are now positioned on faces instead of vertices. This change only affects the preview of VRayFur. The actual render output remains unchanged.
Object visibility controls
The "Skip Rendering" and "Visible" object properties are no longer available. The new "Ignore in VP State" option for Fur and Clippers allows the same visibility control between the Rhino viewport and V-Ray render output.
Every imported or linked block saved with V-Ray version 4.00.02 or earlier upon import/insertion into a scene is rendered black.
To avoid this behavior, the block has to be opened separately, which triggers an automatic V-Ray data upgrade. Then, re-save it before it can be successfully referenced or imported.
Render elements are now treated as assets - they can be created or deleted in the Assets list.
The Reflection Glossiness, Refraction Glossiness and Reflection Highlight Glossiness render elements can no longer be created. V-Ray 3 scenes with these channels will still render them correctly.
The Denoiser is now treated as a render setting and not a render element. Find its options in the advanced render settings panel in the Denoiser rollout. The ‘Effects Update Frequency’ control is moved to the Denoiser section for convenience - now called Update Frequency. It still affects both the Denoiser and the VFB Lens Effect updates.
Consistent Lighting Elements
In V-Ray Next Update 1.1 some of the render elements are rendered differently than before. The Lighting render element now contains all direct diffuse illumination and the GI element contains all indirect diffuse illumination. Similarly, all direct reflections of lights now go to the Specular element and all indirect reflections go to the Reflection element.
Previously this depended on the sampling of the lights and not just on the type of the contribution. Some of the direct contributions that should be in the Lighting and Specular elements were written to the GI and Reflection elements instead. In both cases they compose back to Beauty correctly but the different types of contributions are now split between the elements more consistently.
This change makes the elements more consistent but it's also needed for preventing artifacts in these elements with the adaptive dome light (and possibly in the future with other adaptive lights).
The raw elements are affected only when the corresponding normal and filter elements are available, otherwise they're rendered as before. This is because the raw elements have to be derived internally from the corresponding normal elements in order to work with the consistent elements.
The consistent elements are automatically enabled when the scene contains an adaptive dome light so they don't have artifacts. They are also enabled by default for both new and old scenes and can only be disabled via script access. For V-Ray GPU they are always enabled without an option to disable them.
The quality slider presets are changed in V-Ray Next, Update 2.1 for Rhino to ensure consistent results between CPU, CUDA, and RTX engines, and between the Progressive and Bucket image samplers. The presets count is increased to six and the new preset labels are: Low, Low+, Medium, Medium+, High, and High+. All of them provide better quality than their older counterparts.
Advanced Camera Parameters rollout is introduced to the advanced settings panel. All the physical camera controls like F-Number, Shutter Speed and ISO (previously listed in the Camera rollout) are now located there.
Scenes from v3.6 opened with V-Ray Next may contain an extra Environment texture in the Textures category. It is not plugged in any map slot. It can be safely removed or purged.
The Lens Effects were updated with version 4.1 of V-Ray Next. Lens Effects from scenes saved with previous versions of V-Ray will not be loaded and rendered.
Newly created V-Ray Render components have their V-Ray Geometry input automatically flattened.
V-Ray Render in Project
The V-Ray Render in Project component is now always disabled when loaded from an existing project and will need to be manually enabled in order to function.
As good practice, we recommend a reset of all the render settings (‘Revert to Default Render Settings’) when loading a V-Ray 2 scene. Starting fresh is extremely easy thanks to the Quality slider and the new approach. Keep in mind that, being part of the render settings, any Environment textures will also be disconnected and colors reset.
Loading ‘.vropt’ or ‘.visopt’ files created in previous V-Ray versions is not recommended. Some outdated parameters may cause unexpected results. Using the new streamlined quality presets, and then fine-tuning the settings before saving them in a new ‘.vropt’ file is the recommended approach.