Page History
...
- Specific frames rendering black in V-Ray Standalone
- 3ds Max 2025 crashes with Active shade enabled
- Crash with Convert bitmap to tiled exr/tx and specific file
- Wrong result with VRayTriplanarTex rendering in Standalone
- Rendering discrepancy between 3ds Max and V-Ray Standalone with very distant and small disc lights
- IPR crash when moving lights in scenes with PhysicalMaterial and emission texture
- Failing redirection of missing Cosmos assets for very old scenes
- Rename the "Autoswitch to effectsResult" label to "Auto-show post effects"
- Crash when linking or unlinking VRayTriplanarTex to VRayBitmap used in ForestPro Material tint while V-Ray IPR is running
- Crash on scene reset, when there are 2 or more lights or cameras with an open V-Ray Lister
- 3ds Max crashes on opening ME if we have Phoenix installed on top of V-Ray
- Multiple "V-Ray viewport IPR" items occur in the quad menu
- Standalone renders consistent lighting elements incorrectly when having matte object in the scene
- RawBitmapBuffer containing .hdr pixels data is not extracted to .tx on Enscape .vrscene import
- Slow import of specific Enscape vrscene with more than 240000 nodes
- Crash with V-Ray CPU IPR when going from Perspective to a VRayPhysicalCamera with Motion blur enabled and a VRayDenoiser Render Element
- Animated V-Ray IES light settings are not exported and rendered with V-Ray Standalone
- Warnings for invalid material evaluation with specific scene
- Incorrect shading of backfacing geometry when there is Phoenix Simulator, V-Ray Volume Grid or Environment Fog in the scene
...