Search Issue Tracker
Fixed in 2021.3.25f1
Fixed in 2021.3.X, 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a2
Votes
1
Found in
2020.3.37f1
2021.3.8f1
2022.1.12f1
2022.2.0b3
2023.1.0a4
2023.2.0a1
Issue ID
UUM-10812
Regression
No
[URP] Scene is not marked as dirty when Volume Update Mode
How to reproduce:
1. Create a new URP project
2. Open the "SampleScene" Scene
3. In the Hierarchy select the "Main Camera"
4. In the Inspector Expand Environment section and change "Update Mode" under Volume value
Expected results: The Scene is marked as dirty
Actual results: The Scene is not marked as dirty
Reproducible with: 10.10.0 (2020.3.37f1), 12.1.7 (2021.3.8f1), 13.1.8 (2022.1.12f1), 14.0.3 (2022.2.0b3), 15.0.0 (2023.1.0a4)
Reproduced on:
Windows 10
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