V-Ray Next, Update 2.1
Official Release
Date - July 02, 2019
Download - Build 4.20.01
New features
VRayEdgesTex
-
Add mapped multiplier to control the rounded corners' radius
Modified features
V-Ray
-
Add a warning when there are Render Elements with filtering off and Progressive Sampler
-
Avoid saving the "Shademap export" helper channel to image files
-
Render Raytrace material as black to avoid interfering with shading
VRayOSL
-
Increase width of the string widgets
VRaySamplerInfo
-
Add tangent and bitangent modes in object space
VRayVolumeGrid
-
Copy-paste support for render gradients and curves
VFB
-
Revert the IPR zoom modificator to Ctrl+Shift/Ctrl
Bug fixes
V-Ray
-
Artifacts with VRayEnvironmentFog and Adaptive dome light
-
Debug shading in Viewport IPR MaxScript error on 3ds Max2017
-
Debug shading in Viewport IPR menus produce error after V-Ray is uninstalled
-
EXR images are saved as "incomplete" (since 4.20.00)
-
Memory tracking reports wrong month number on the timestamps
-
Rendering a specific scene with disc lights produces incorrect results on the second render
-
Spurious skipping of a subframe when rendering using PresenZ camera and DR
-
Using "File" > "New" > "Keep objects and hierarchy" may cause a crash if the scene has VRayHDRI maps
V-Ray IPR
-
Attempting to stop rendering may freeze 3ds Max
-
Changes to displacement maps are not updated (since 4.20.00)
-
Crash if the scene is modified while V-Ray is preparing objects
-
Crash when copying objects with Override material
-
Crash when creating new objects while V-Ray is preparing geometry
-
Crash when rendering with CoronaMtl
-
Crash with 3D displacement with "Keep continuity" enabled if the scene is modified while V-Ray is preparing objects
-
Creation of dome light from the V-Ray toolbar is not correctly detected
-
Deleting a dome light is not reflected
-
Inconsistent lighting when rotating dome light
-
Incorrect direct illumination of VRayLightMtl
-
Lights with animated multiplier don't update
-
Moving an instance of a displaced object during rendering may cause a crash
-
Unhandled exception when exporting a .vrmesh file during rendering
V-Ray GPU
-
Crash with adaptive lights with more than 110 000 lights
-
Closing the VFB while exporting nodes crashes 3ds Max
-
Crash when rendering VRayInstancer with many particles and VRayVolumeGrid
-
Crash when sliding the timeline during IPR and then stop rendering
-
Crash with light cache when mesh acceleration types in MB segment's ends are different
-
Every 10-th UV tile (e.g. 1010, 1020, 1030) is not rendered
-
Incorrect light cache retrace amount in some cases
-
Incorrectly strong bump effect with normal maps and VRayAlSurfaceMtl
-
Rounded corners аrе not rendered with Bucket sampler in scenes with no direct lighting
-
Vertical FOV with spherical panoramic camera is ignored unless a 360 degree horizontal FOV override is used
-
VRayALSurfaceMtl with rounded edges render wrong
-
VRayALSurfaceMtl's SSS is darker in the areas reflecting objects with VRayFastSSS2
V-Ray Cloud
-
Color Correction texmap is rendered wrong with 32-bit images
-
Difference in render with VRayEdgesTex in the VRayMtl displacement slot
VRayHairMtl
-
Does not compose correctly when the "consistent lighting elements" option is enabled
VRayOSL
-
Dropdown parameters reset when refocusing the node in the Slate Material Editor
-
Tooltips for shader parameters are displayed in the wrong places
VRayPluginNode
-
MtlRoundEdges plugin is not working in "Convex only" and "Concave only"
-
Renders different than V-Ray Standalone in bump slots
-
Scenes saved with blacklisted plugins should still open correctly
VRayToonMtl
-
Don't bake gamma into the gradients of VRayToonMtl
-
Export to .vrscene
VRayVolumeGrid
-
Brighter results in VRayLighting render element with Consistent lighting elements turned on
-
Crash with caches over 2.1 billion voxels with Phoenix Light Cache since Phoenix 3.12
VFB
-
Crash when loading a 3ds Max scene from the history
-
Dock history option causes IPR restart
-
The tooltip for the debug shading is wrong