Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0b9
Issue ID
642111
Regression
Yes
Scene file is modified after changing build settings
To Reproduce:
1. Download the attached project or create any project with two scenes in it, make sure the target platform is iOS.
2. Open scene "testScene_many_models", make sure it is added to the build then goto player settings, select iOS and, for example, change Graphics API to some other setting.
3. Open another scene, a "Scene Has Been Modified" message box is thrown (only if the first scene is included in the build) the Graphics API settings remains scene independent so if you don't save it still remains changed in the new scene.
4. After saving nothing seems to be changed in the scene file itself, when comparing it with the pre-save version using filemerge.
Settings that trigger the message box:
-Graphics API in iOS
-Stripping Level, in Android/iOS/... (it seems to trigger it on scene opened after changing it)
Some other function seems to sometimes tag the scene as unsaved too, but this can be reproduced most consistently by changing Graphics API setting for iOS.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment