V-Ray Next, Update 1.2
Official Release
Date - Mar 27, 2019
Download - Build 4.10.03
New features
V-Ray
- Initial support for 3ds Max 2020
Modified features
V-Ray
- Support for IES files containing the comma (",") symbol in the light's description
Bug fixes
V-Ray
- Blowup and Auto Region Selected produce stretched results
- Crash when exporting vrscene to a non-existing directory
- Direct light selects are always propagated through refractions
- Drop action should fall back to default
- MaxScript error occurs with viewport menus when V-Ray is downgraded to an older version with no viewport IPR support
- Separate VRayCryptomatte REs names are not exported to .vrscene
- Wrong keyframes export to .vrscene, breaking animation rendering
V-Ray GPU
- Viewport IPR has wrong perspective when switching the active viewport from orthographic projection
- VRayDenoiser is not always applied on the complete pass
- VRaySamperInfo render element is not exported
- Wrong Object XYZ texture mapping for Volume grids rendered
VFB
- Color corrections panel is missing when is maximized during IPR session
- Lightness color correction with values close to zero lead to artifacts in Lens Effects results
VRayPhysicalCamera
- Vertical shift is reset in the viewport preview
VRayProxy
- "Expand # to frame number" doesn't work in the viewport
VRayVolumeGrid
- Volume grids loaded from OpenVDB caches that contain internal rotation render clipped with V-Ray GPU
.vrscene exporter
- Crash when trying to export vrscene to a non-existent folder
- Decimal separator changes randomly on every export in a specific scene
Installer
- Silent uninstall does not work for V-Ray Next
V-Ray Next, Update 1.1
Official Release
Date - Dec 18, 2018
Download - Build 4.10.02
Modified features
V-Ray
- Reduce messages about invalid bump normals
V-Ray IPR
- Do not calculate render elements (except denoiser) for viewport IPR
V-Ray GPU
- Consistent lighting render elements
VRayFastSSS2
- Hide "single scatter"'s Raytraced (refractive) and Raytraced (solid) modes when V-Ray GPU is current renderer as they are incompatible
VRayProxy
- Alembic meshes exported from Phoenix for 3ds Max 2019 can now be rendered with motion blur
VRayVolumeGrid
- Add empty grid size and resolution options to the user interface
- Optimize volumetric rendering when Smoke Opacity is modulated by a texture
Bug fixes
V-Ray
- Artifacts in alpha channel with many transparent objects
- Incorrect lighting elements on matte objects when "Consistent lighting elements" option is enabled
- Lighting elements are not propagated through refractions with consistent lighting elements enabled
- Lighting from VRayLightMtl with direct illumination is missing in consistent render elements output
V-Ray IPR
- Crash with VRayProxy when switching rendering between viewport and VFB
- Unhiding by category is not updated
- Viewport IPR option is missing in non-English 3ds Max instances
V-Ray GPU
- Alembic VRayProxy copies randomly disappear (since 4.10.01)
- Artifacts with matte and Adaptive Dome light
- Crash when rendering animation sequence with DR and animated lights
- Crash when stopping viewport IPR during compiling kernels phase
- Gradient Ramp stops working when moving the time slider in V-Ray GPU IPR with motion blur
- Production rendering of a sequence with deleted particle source for VRayInstancer returns error (since 4.10.01)
- VRayProxy updating animation stops when its Object ID is changed during IPR (since 4.10.01)
VRayFur
- Animated parameters are not exported
- Wrong placement with selected faces in .vrscenes
VRayLight
- Some spinners in the UI for disabled properties
VRayMDL
- Materials with material.ior that depends on a material parameter crash in V-Ray GPU IPR
VRayOptionRE
- Crash to desktop when render element is placed last in the list
VRayPluginNode
- Crash to desktop with VRayPluginNodeMtl in 3ds Max 2013 (since 4.10.01)
VRayScannedMtl
- Different buckets in VRayDiffuseFilter and VRayReflection from DR hosts
VRayVolumeGrid
- The warning about DR and local paths is still appearing even when there is no volume grid in the scene
ply2vrmesh.exe
- The -velocityAttrName parameter does not work for Alembic input files
V-Ray Next, Update 1
Official Release
Date - Nov 29, 2018
Download - Build 4.10.01
New features
V-Ray/V-Ray GPU
- Add Nitrous viewport IPR support
V-Ray GPU
- Add bucket rendering support
- Add support for the Cryptomatte render element when in bucket mode
- On-demand texture mode support for IPR
- Support for VRayMtl refraction dispersion
V-Ray Cloud
- Lighting Analysis render element support
VRayGLSL
- Ability to read vertex color and vertex alpha from within shaders
VRayInstancer
- Add instancing mode "By particleInteger"
VRayNoiseTex
- A new texmap based on VRayPluginNode that renders the same both on V-Ray and V-Ray GPU and in V-Ray Standalone
VRayHairNextMtl
- Added Glint and Glitter controls
VRayPhysicalCamera
- Rolling shutter effect for motion blur
VRayVolumeGrid
- Add a .getFrameInfo() MAXScript function that retrieves the currently loaded frame info string
- Add support for NVLink for GPU Volumetrics rendering
- Add support for textures in GPU volumetrics
- Implement render and preview of instanced nodes
- Support for instancing volume grids and Particle Shaders using VRayInstancer in 3ds Max
- Support for Scene and Object XRefs
VFB
- Add "Save in image" option to the LUT color correction
- Add Weight parameter for the LUT color correction
- Add an option to save image color corrections to raw .exr and .vrimg files
- Reworked lens bloom and glare lens effects calculation
Modified features
V-Ray
- Lens effects memory and speed improvements
- Improve lighting render elements consistency, automatically enabled for new scenes and when using the adaptive dome light
- Improve light cache preview
- Hide the legacy VRayMap
- Print a warning when using the irradiance map with full light select elements
- Add Chinese tooltip translations
- Add a parameter for additional control of the auto-exposure (renderers.current.camera_autoExposure_compensation)
V-Ray IPR
- Support for most atmospheric effects in IPR mode
- Improve interactive responsiveness with heavy scenes
V-Ray GPU
- Improved image sampling with many (more than 1k) samples efficiency
- Add support for RGB Tint and RGB Multiply textures
- Faster calculations VRayFastSSS2 materials
- Grey out the unsupported subdivs and cutoff parameters for lights, materials and textures
- Reduce memory usage with motion blur
- Speed up loading of 8-bit textures
- Support for "Affect background" with the bucket sampler
- Faster geometry updates during IPR
- Add a warning if there is an unsupported render/bake element
- Add Alembic visibility_list support for VRayProxy
- Add support for GrowFX
V-Ray Cloud
- Add support for the Waves texmap
- Export color corrections settings in .vrscene files
- Support for Dent Map
VRayDisplacementMod
- Improve "Keep continuity" option to weld seams at vertices too
VRayHDRI
- Support for the <frameNum> tag
VRayInstancer
- Improve speed during scene preparation
VRayGLSL/VRayMDL
- Add support for "C++/CPU" CUDA devices rendering
VRayOrnatrixMod
- Implement Ornatrix v6 support for optimized hair data access
- Utilize the width data from the new OX Change Width modifier
VRayOSL
- Implemented the supported wrap modes
- Add more parameters to the vray_subsurface closure
VRayPluginNode
- Add a short description info based on the plugin description
VRayProxy
- Read proxy files on demand so that only visible proxies are loaded
VRayScene
- Instancer is not shown in the viewport
VRayLightSelect
- Add Include/Exclude list by layer selection
VRayOptionRE
- Ability to update the exr metadata parameter in VRayOptionRE with a per-frame MaxScript callback
VRayUnclampedColor
- Remove the "color mapping" parameter
VRayVolumeGrid
- Expose the grid-based motion blur algorithm from Phoenix FD 3.00.01 for use via the 'mbgrid' script parameter
- Support for the new transformation model of OpenVDB caches from FumeFX 5
VFB
- Add docking support for the main window (enabled by the VRAY_VFB_DOCKABLE environment variable)
- Use text labels for the flyout buttons
- Lens effects size to accept values lower than 1.0
V-Ray Toolbar
- Align the newly created camera from "V-Ray Physical Camera" button
V-Ray Bitmap to VRayHDRI converter
- Improve responsiveness and conversion speed
- The "Half" precision option should be on by default
vdenoise.exe
- Ability to apply lens effects from .vrscene files
VRayDenoiser
- NVIDIA AI denoiser uses less GPU memory for denoising
Bug fixes
V-Ray
- Warning messages about invalid bump normals should be printed just once per material
- Reduce slowdown due to repeating attempts to load missing texture files in case many materials refer them
- Very slow elliptical filtering with tiled textures
- Crash with region rendering, with render elements and Previous render set to Darken
- Crash with Forest Pro with VRayLightMtl with Direct illumination enabled
- Rare crash with infinitely recursive processing of 3ds Max progress bar events
- Different brightness with high-resolution renderings with Auto Exposure enabled
- Crash when rendering VRayLightMtl and VRayExtraTex with the same MultiTexture
- Artifacts with adaptive lights in different situations
- The "Direct visualization" option for caustics doesn't work
- Starting a production render after IPR may cancel immediately in some scenes
- Artifacts with Phoenix FD Ocean with Ocean Displacement
- BerconTile map has wrong mapping rendering from .vrscenes
- Different buckets with DR and Auto Exposure
- DR may have watermarks if network is unstable due to license failure
- Update change of geometry type per object (static or dynamic geometry) from the V-Ray object properties while rendering
- NaN pixels in VRayReflection render element
- Random crash when cancelling a batch render in 3ds Max
- Turning Frame Stamp off in the Render Setup is not working if it's on in the VFB
- Tooltip translations are not applied to VRayLight and the V-Ray render elements
VRayLight
- Artifacts in VRayShadows and VRayGlobalIllumination render elements with adaptive dome light or adaptive lights
- Adaptive dome light artifacts in specular in specific situations with max ray intensity enabled
- Artifacts with matte objects (matte for refl/refr = off) and adaptive dome light
- Artifacts with long and thin (like 7000x3) rectangle light
- Transparent objects with "cast shadows" off render black when there is a dome VRayLight behind them
- Dome light affects objects inside other objects with matte turned on
- Crash when rendering with a MAXScript plugin derived from VRayLight
VRayDenoiser
- Super bright lens effects when using the NVidia AI denoiser with very noisy images
V-Ray IPR
- Crash when removing vertices or polygons while IPR is running and motion blur is enabled
- Crash when modifying a texmap attached to VRayDisplacementMod
- Crash when undoing deletions of geometries with VRayDirt
- 3ds max crash when using VRayMetaball
- Stalling the whole UI in scenes with many VRayScannedMtls
- Crash when scrubbing the timeline in a scene with VRayMetaball
- Changes to VRaySphereFade parameters are not updated
- Random crash when restarting rendering with VRayOSL
- Crashes when modifying geometry during rendering
- Crash with animated Alembic files when dragging the time slider
- "Hidden lights" option is ignored
- Different exposure when using the Physical camera exposure Control and after toggling the Exposure option off-on with VRayPhysicalCamera
- Set focus distance doesn't update the DOF effect with VRayPhysicalCamera
- Rendering gets stuck when rendering XMesh object
- Black output with more than one VRayDenoiser render elements
V-Ray GPU
- Crash on the second frame with scenes containing lots of animated plugins
- When there is just one light in the scene, adaptive lights unnecessarily resets the progressive buffer
- Crash when loading new scene and IPR is still running
- Unhandled exception when aborting IPR during VRayProxy loading
- Crash when view dependent displacement is used with orthographic projection
- Unhandled exception when VRayPlane is shaded with a VRayLightMtl with Direct illumination enabled
- Wrong path expansion for IFL files if the full path to the IFL is not present
- V-Ray raw image file is saved as 16-bit EXR regardless of the saving settings if VRayOptionRE is not present
- IPR with DR hangs if you drag the time slider
- "RGB Level" of Output map has no effect on Mix map unless "Enable color Map" is checked
- VRayMtl with GGX brdf has incorrect glossiness in some situations
- Sequence rendering stops after few frames on scene with Falloff map
- VRayLight set to "Disc" produces wrong intensity when using the lumens unit
- Environment ZDepth color does not match V-Ray
- Black zdepth pass with "use camera clip boundaries" enabled and the physical camera's clipping planes disabled
- Artifacts with VRayScannedMtl with "Edges Displacement"
- Artifacts with adaptive lights
- Artifacts with adaptive lights and animation sequence
- Animated intensity of VRaySun is not taken into account in IPR
- Artifacts with displacement in scene with very narrow faces
- Geometry with VRayEdgesTex with "Show subtriangles" enabled renders black
- ExtraTex with Ramp driven by facing ratio internally uses no interpolation between positions
- Invisible Dome VRayLight is visible through VRay2SidedMtl with refractive VRayMtl and transparent VRayMtl
- Noisy alpha channel with shadow catcher objects
- Difference in GI generated by matte objects using BF or LC with glossy reflections
- The temperature attribute of the VRayRectLight doesn't work when the light is set to be a "Disc"
- Support for VRayLightMtl's Opacity
- Incorrect VRayPlane bump mapping
- Wrong IPR render with specific scene with render elements
- Fireflies with VRscan car-paint with flakes
- VRayFastSSS2 on GPU gives additional specular artifacts
- Flickering between the first and rest of the frames with Forest Pro and Mesh VRayLight
- VRayRefractionMap, VRayRefractionFilterMap, VRayExtraTexMap result is blank when baking textures
- The "Dim distance" parameter doesn't work with Dome Lights
- Cuda error 700 with VRayHairMtl with VRayHairInfoTex set to "Random by strand index"
- Displacement AutoBump for GPU does not produce correct results
- Issues with textures with either dimension larger than 32768 pixels
- The Invert option of nested Output rollout/map renders wrong
- Invert output option of VRayHDRI texmap is not properly considered when used with multiple materials
- Backburner marks job as failed when there is an error in V-Ray messages for unsupported material
- Wrong render of VRayFur and Ornatrix objects when using VRayUserColor map
- VRayFastSSS2 is producing artifacts when a texture with black areas is loaded as a scatter radius texture
- VRayDiffuseFilter render element for VRayFastSSS2 is rendered incorrect
- VRayLightSelect render element for VRayFastSSS2 is rendered incorrect
- Wrong render of edgesTex on subdivision surfaces
- Artifacts with VRayScannedMtl and Bump multiplier
- VRayEdgesTex not showing up in diffuse channel with IPR
- Random crash with specific heavy scene with animation
- Tint override in Forest Color is ignored when there is texture randomization
- Unhandled exception when changing SSS materials during IPR
- Crash with certain GLSL materials in BRDF mode
- Crash when loading with a scene where geometry map channel info is inconsistent with face count
- SSS artifacts on voxel edges of proxy object due to different voxel splitting on GPU
- Crash when rendering animation with VRayProxy with multiple voxels
- Black transparency effect in a scene with a lot of geometry stacked behind each other
- Matte doesn't work with Multi/Sub-object materials
- Textures from IFL are not updating correctly during IPR
- Animated clipping plane of VRayPhysicalCamera is not exported to .vrscene
- Crash on update with animated meshes with motion blur during IPR
- If there are unsupported elements baking output is wrong due to messed elements order
- Unhandled exception with VRayPlane or VRayFur converted to mesh light
- If V-Ray is the current render engine, V-Ray GPU utilization settings are exported with wrong values
- Composite map with empty layers is not exported correctly
- Noise threshold reports are misleading
- Forest Pack "Limit to Visibility" is not properly exported to .vrscene when the camera is animated
- Body object is always exported with draft quality
- Maxscript command vrayUpdateIPR() stops the IPR
V-Ray Cloud
- Export stats dialog should not be closed on scene node deletion
- Animated tilt and shift parameters of physical cameras are not exported in .vrscenes
- Animated color of the Falloff map is not exported
- Animated VRayPhysicalCamera target movement is not exported
- Flipped textures in VRayOSL
- Camera animation discrepancies with V-Ray
- Export VRayWireColor render element
- VRayNormalMap assigned to VRayBumpMtl is not exported
- No motion blur is rendered on the last frame when exporting an animation frame range
- Vector displacement in "Object" mode produces wrong result
- Invalid colors when rendering scenes with two VRay2SidedMtl materials nested in each other
- Mesh VRayClipper doesn't work if the mesh has animated parameters
- Animated parameters of VRayMtl are not exported
- Physical cameras with offset pivots are not exported properly
- Ornatrix feathers are not exported
- Animated intensity of VRayIES lights is not exported
- Animated Multiplier of VRayLights is not exported
- Animated VRaySun position is not exported
- Export for VRayMtlID render element in .vrscene files
- Texmap plugged into a texture slot of the Tiles map is rendered even if turned off
- Displacement turned off in the V-Ray Global Switches still renders
- Wrong material rendered when Falloff map is used
- Animated VRayPhysicalCamera "Zoom factor" is not exported
- Forest Pack object with "Visible to Camera" disabled still renders
- Animated slice modifier resets Material object ID's when exporting animation in .vrscene
- Difference in render result when using MultiTexture
- Different result with V-Ray for invisible spherical VRayLight and VRayEnvironmentFog
- Material editor sample slots rendering slows down the vrscene export
- Wrong render time in V-Ray log when material editor is opened during IPR
- Wrong export of the Gain parameter of ColorMap
- Saving V-Ray raw image file and Separate render channels options are not exported
- Shutter offset of the Physical camera is not exported properly
- Exporting a .vrscene without animation always includes "//Frame at time 1" in the .vrscene file
- The option to lock the dome light texture orientation to the dome light viewport icon not taken into account when exporting animated .vrscene
- "Lights" option in Global Switches is ignored
VRayALSurfaceMtl
- Opacity slot not exported in .vrscenes
- Endless render when the SSS1/2/3 radius values are set to 0
VRayDistanceTex
- Crash when using the material editor while a Phoenix FD simulation that is evaluating a VRayDistanceTex is running
- Not working with particle systems loaded in its objects list
- Texmap is affected only by renderable objects in V-Ray GPU
VRayFur
- Different bend direction between V-Ray and V-Ray GPU
VRayFurStyler
- Crash when copied/cloned
VRayGLSL
- Error when merging scenes with GLSL shaders
- Anisotropy has wrong mapping and rotation
- Shaders with uninitialized samplers crash with V-Ray GPU
- GLSL materials cause V-Ray GPU to recompile kernels on each start
- Shaders use too much memory per thread
- vr_RayFlags has incorrect value with V-Ray GPU
- Vector displacement in "Object" mode does not work with V-Ray GPU
VRayGLSL/VRayMDL/VRayOSL
- Cloned or copied plugin may result in error
VRayGLSL/VRayMDL
- LLVM produces code for Skylake processors that causes crashes
- Crash with specific shader rendering with V-Ray GPU
VRayHDRI
- Undo doesn't work for Bitmap field
VRayIES
- Cloning a light causes it to render incorrectly
VRayInstancer
- Instances are rendered with the particle materials instead of the instanced geometry material
VRayMDL
- Param block error on scene load
- Crash when the material of the node is changed
- Empty material crashes 3ds Max when rendering with V-Ray GPU
VRayOrnatrixMod
- Crash with VRayHairNextMtl and motion blur
- ObjectSpace data per vertex of the hair is not working in V-Ray Next
- Per-vertex mapping for hairs' texmaps
VRayOSL
- Randomly rendering black
- Local assets are not found when rendering with V-Ray GPU
- OSL additional paths not working in 3ds MAX
- Crashes in V-Ray IPR
- Bitmap texture buttons don't work in Slate Material Editor
- UI shows string popups as texture buttons
VRayPluginNode
- Ability to use V-Ray PluginNodeTex in bump and displacement material slots
- ObjectXYZ and WorldXYZ mapping modes
- Plugins with texture inputs don't have an input to load a bitmap file
- Mtl plugins have no inputs
- Material with BRDFCarPaint and BRDFStochasticFlakes renders black with V-Ray GPU
- Crash with TexFalloff or TexCellular when assigned to material
- Plugin parameters have reverse tab order of UI controls
- Wrong initial render with MtlOverride plugin
- Gaps along the boundaries of TexBitmap plugin
- Animated parameters are not saved with scene
- Parameters' tooltips and ranges are not correctly set
- Texmap buttons are not immediately updated in 3ds Max 2013-2016
VRayProxy
- Crash when opening a scene with Аlembic preview file
- Preview cache sometimes prevents proper rendering with Alembic offset
- Tooltip text listed in Parameter Wiring dialog
VRayScene
- Crash with .vrscene sequence and missing first file
- Crash when using UV-coordinates from an imported .vscene
- VRayExtraTex with a bitmap is blurred on objects from the .vrscene
- Viewport representation of VRayLights from vrscenes is wrong
VRayVolumeGrid
- Missing buckets with moving volume grid in Volumetric Geometry mode and motion blur
- Render Cutter in Isosurface mode of a volume grid with VRayMtl with Affect Shadows blocks GI rays for geometry inside the Cutter with V-Ray Next
- Incorrect light intensity with Approximate Scattering using V-Ray GPU
- Random crash when rendering a volume grid in Volumetric Geometry mode with V-Ray Velocity Render element
- VRayVelocity render element doesn't work in Volumetric Geometry mode
- Exception Compiling Geometry when attempting to start IPR in Mesh, Ocean Mesh or Cap Mesh mode
- Volume renders wrong on CPU when the grid is moving with the camera and Motion Blur and the Phoenix Light Cache are used
- Buckets in VRayLightSelect render element when rendering in Volumetric Geometry mode with Phoenix Light Cache enabled
- Rendering a scene containing a volume grid and a Phoenix FD Simulator causes a crash with V-Ray GPU
- Even when there aren't active render elements warnings appear in V-Ray messages
- Incorrect preview when volume grid's pivot point is offset
- Voxel preview of temperature around 200 Kelvins with As Fire enabled draws bright red and pink voxels
- Warning: Emit light isn't supported on V-Ray GPU
VFB
- Crash when enabling Bloom/Glare while A/B compare is enabled
- Lens effects Threshold parameter value is reset on scene open
- LUT color correction is not loaded properly from 3ds Max scene files
- Blank VFB when comparing images from history after effectResult is generated
- Freezes randomly if playing with it while rendering
- Maximized VFB returns to previous size on render start on 3ds Max 2018-2019
- Buckets shift slightly when completed
V-Ray scene converter
- Standard materials are converted to VRayMtl with unlocked highlights and reflection glossiness
VRayDenoiser/vdenoise.exe
- NVIDIA AI denoiser is not releasing the GPU memory after the denoise calculation