Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.35f1
2022.3.20f1
2023.2.10f1
2023.3.0b7
Issue ID
UUM-63946
Regression
No
The Scene is not set to dirty when calling EditorUtility.SetDirty from within MonoBehaviour.OnValidate
How to reproduce:
1. Open the attached project "IN-68131.zip"
2. Open Assets/Scenes/SampleScene.unity
3. Open Assets/Scenes/SampleScene1.unity
Expected results: "Scene(s) Have Been Modified" window is thrown
Actual results: No "Scene(s) Have Been Modified" window is thrown
Reproducible with: 2021.3.35f1, 2022.3.20f1, 2023.2.10f1, 2023.3.0b7
Reproducible on: Windows 11 22H2
Not reproducible on: No other environment tested
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
- [Android][OpenGL]Soft Shadows contain artifacts when the OpenGL Graphics API is used
- The particle system prewarm flag is ignored when calling the Start function after the Stop function
- The Scene view flickers when moving around if there are visible Hair Shaders
- The gradient ShaderGraph is inverted when using the Perceptual blend mode
- Particle System allocates large amounts of memory when it is very far away from the origin of the Scene
Resolution Note:
To manually mark a scene as dirty please refer to our documentation here: https://support.unity.com/hc/en-us/articles/115002294603-How-do-I-make-a-scene-dirty-when-modifying-a-property-via-script