Search Issue Tracker
By Design
By Design in 2023.3.X
Votes
0
Found in
2023.2.0b6
2023.3.0a2
Issue ID
UUM-47232
Regression
No
HDRP Global Settings Tracing settings are not affecting the project
How to reproduce:
1. Open the user-attached project “test0728”
2. Open the “SampleScene” scene
4. Change the Scene View position so you can see the ball’s reflection in the water on the ground
5. Click Edit → Project Settings → Graphics → HDRP Global Settings → Screen Space Reflection → Tracing
6. Change the Tracing to “Ray Tracing” and then to “Ray Marching”
7. Observe the reflection of the ball
Expected result: There is a reflection when set to “Ray Tracing,” and there is no reflection when set to “Ray Marching”
Actual result: With both settings, there is a reflection because the settings don’t affect the Tracing
Reproducible with: 2023.2.0b6, 2023.3.0a2
Couldn’t test with: 2021.3.29f1, 2022.3.8f1, 2023.1.10f1 (No settings available)
Workaround: Change the “Volume Ray Tracing” Colume Profile Tracing settings
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Working as intended.
The settings in the Volume Profile attached to the HDRP Asset override those in the Default Profile.
Resolution Note (2023.3.X):
Working as intended.
The settings in the Volume Profile attached to the HDRP Asset override those in the Default Profile.