Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
6000.5.0a6
6000.6.0a1
Issue ID
UUM-133949
Regression
No
The Reflection Probe fails to update properly when generating lighting in the Lighting window and using a custom Renderer Feature
How to reproduce:
1. Create a new Unity URP Project
2. Import the attached “TestURPFeature“ custom Unity package
3. Navigate to Assets > TestURPFeature
4. Open the “TestURPFeature” Scene
5. Navigate to Assets > Settings > PC_Renderer
6. In the Inspector window, add the “Debug Feature” Renderer Feature
7. In the Lighting window, click on the “Generate Lighting” button
8. Navigate to Assets > Settings > PC_Renderer
9. In the Inspector window remove the “Debug Feature” Renderer Feature
10. Navigate to Edit > Lighting > Clear Baked Data
11. In the Lighting window click on the “Generate Lighting” button
12. In the Hierarchy window select the “Reflection Probe” GameObject
13. Observe the Inspector window
Actual result: The Reflection Probe displays yellow quads
Expected result: The Reflection Probe does not display any yellow quads
Reproducible with: 2023.3.0b1, 6000.0.66f2, 6000.3.7f1, 6000.4.0b7, 6000.5.0a6
Could not test with: 2023.1.0a1 (The URP Render Graph was introduced in the 2023.3 stream of Unity)
Reproducible on: Windows 10 (by user), Windows 11
Not reproducible on: No other environments tested
Notes:
- When the Reflection Probe is selected, pressing the “Bake” button updates it to the correct state, but after clicking the “Generate Lighting” button in the Lighting window, it resets back into the incorrect version
- To reproduce this issue in Unity 6000.5.0a6 exclude steps 8-11
-- Actual result: The Reflection Probe does not display any yellow quads
-- Expected result: The Reflection Probe displays yellow quads
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
Add comment