Search Issue Tracker
Not Reproducible
Votes
0
Found in
Issue ID
744434
Regression
No
[VCS] Unity 5.3: "ProjectSettings is modified" dialog frequently pops up when starting a build
The "Verify saving assets" option is useful for catching cases where the TFS Plugin silently fails to check out modified content. Unfortunately, having this option enabled exposes bugs in Unity where settings files are unnecessarily overwritten, resulting in extra wasted time dismissing popups.
Repro Rate: 5/10 - 50%
1. Launch Unity 5.1 editor
2. Click Edit -> Preferences
3. Make sure Verify Saving Assets is checked
4. File -> Build Settings
5. Set configuration like this:
Platform = Windows Store
SDK = Universal 10
UAP Build Type = XAML
Uncheck all three boxes
Click Build
6. Select HoloStudio's checked-in WindowsStoreApp directory as the build target
7. Build
Result: Annoying dialog pops up most of the time
Title: Save Assets
Text: Unity is about to save the following modified files. Unsaved changes will be lost!
File: ProjectSettings/ProjectSettings.asset
If you look at the diff of the ProjectSettings.asset file, nothing is actually changing from the checked-in version. This looks like a case where Unity engine code is aggressively dirtying the in-memory settings file state despite no actual changes being made.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment