Search Issue Tracker
Won't Fix
Votes
5
Found in
2017.1.0f3
Issue ID
959900
Regression
Yes
Scene is set dirty immediately after opening it
To reproduce:
1. Open the project, attached by the user (TreinaMais.zip)
2. Open the "SignUp" scene
3. Observe that the Editor immediately shows that the scene had some changes made to it
Expected: the Editor doesn't show that the scene is dirty when no changes were made to the scene
Reproduced in 5.5.5p1, 5.6.4p1, 2017.1.0f3, 2017.1.2p1, 2017.3.0b5
Did not reproduce in 2017.2.0a1, 2017.2.0f3, 2017.3.0b4
Regression introduced in 2017.3.b05
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
Only happens the first time you open the scene. Minor issue and low priority dont know when we'd get to fixing it.