Unsupported features and known issues
General unsupported features
V-Ray RT always performs rendering outside of 3ds Max, through the V-Ray RT render server (which itself is a modified version of V-Ray Standalone). This means that it operates in a completely different way and independently from the 3ds Max rendering API and from the standard V-Ray renderer. This approach allows for improved interactivity and for a great deal of flexibility in the implementation of V-Ray RT, but at the same time means that some differences between the standard V-Ray renderer and V-Ray RT are possible.
The following features are explicitly not supported by V-Ray RT at this time, and may cause the rendered output from the standard V-Ray renderer to be different from the V-Ray RT output in the 3ds Max ActiveShade window. Some of these are not supported for performance reasons, while others will be implemented in a future update.
Note that the list is not exhaustive; there may be other features which are not supported. Whenever applicable, equivalent or similar supported features are noted.
General unsupported features
- Exposure control settings in the 3ds Max Environment dialog. You can use the V-Ray color mapping controls and/or the exposure settings of the VRayPhysicalCamera instead.
- The Legacy sun/sky/camera models option in the V-Ray render settings. This option is always assumed to be off by V-Ray RT.
- Photon-mapped caustics. However, caustics due to indirect illumination are supported.
- Subpixel mapping is currently not supported.
- Render-time hair and fur either through VRayFur primitives, or through the 3ds Max Hair&Fur modifier;
- VRaySphere primitive. Support for this will be added in an update.
- Light include/exclude lists;
- Local per-material environment overrides in VRayMtl. However, general environment overrides in the V-Ray environment rollout are supported. Support for local per-material environment overrides will be added in an update;
- The sub-surface scattering options in VRayMtl. Support for these will be added in an update.
- The following texture maps are explicitly not supported at this time: VRayDirt, VRayMap, Dent, Perlin Marble, Wood, Planet. Support for most of these will be added in an update;
- 3rd party texture maps are not supported, with the exception of the ColorCorrect map (from which only the parameters in the RGB Space (Pre-Process) section and the Source texture slot are supported).
- Atmospheric effects are not supported at this time. Support for these will be added in an update.
- Orthogonal viewports are not supported. Only perspective and camera views are supported. Support for user views and orthogonal cameras will be added in an update.
The following are issues related to the manipulation of the 3ds Max scene while the ActiveShade window is open. Some of these cannot be corrected due to limitations of the 3ds Max API. Others will be corrected in an update.