Search Issue Tracker
Fixed
Fixed in 6000.0.58f1, 6000.2.5f1, 6000.3.0b2, 6000.4.0a1
Votes
0
Found in
6000.0.54f1
6000.1.13f1
6000.2.0b10
6000.3.0a3
6000.4.0a1
Issue ID
UUM-112725
Regression
No
Raytracing renders artefacts and performance drops when switching Volumes at runtime
Reproduction steps:
1. Open the attached “IN-108833.zip” project
2. Open the “bug_repro” Scene
3. Enter Play mode
4. Move around in the Game view with left mouse button
5. Press “Space” on the keyboard 5-10 times (or however many it takes to reproduce)
6. Observe the Game view
Expected result: No frame rate drop or artefacts are visible
Actual result: Frame rate drops and white cube/block artefacts are visible
Reproducible with: 2023.1.0b1, 6000.0.54f1, 6000.1.13f1, 6000.2.0b10, 6000.3.0a3
Reproducible on: Windows 10 (user reported), Windows 11
Not reproducible on: No other environment tested
Notes:
- Pressing “Space” switches between Raytrace and Pathtrace volumes and the Area Light gets toggled with the Pathtracing volume
- To make the reproduction faster, move the camera around and press space frantically
- When there is both Directional and Area Light present in the scene the glitch doesn't happen, only when just Directional Light is present
- Re-enabling the Area Light manually when the glitch is visible will clear the glitch and restore framerate
- Also reproducible in the Player
- In the 2023.1.0b1 version could only observe the performance drop, but not the artefacts
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Resolution Note (fix version 6000.4.0a1):
Fix verified in 6000.4.0a1_fa35ad2071f9
Resolution Note (fix version 6000.3.0b2):
Fixed in 6000.3.0b2
Resolution Note (fix version 6000.2.5f1):
Fixed in Unity 6000.2.5f1.
Resolution Note (fix version 6000.0.58f1):
Fixed in 6000.0.58f1.