Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.1f1
Issue ID
UUM-72236
Regression
Yes
EditorUserBuildSettings is corrupted when changing Editor version of the project
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open “Assets/Scenes/SampleScene” Scene
3. Enter Play Mode
4. Observe the Console
5. Exit Play Mode and close the project
6. Add the project’s “Assets“, “Packages” and “ProjectSettings” folders to version control
7. Using Unity Hub, open the project in one of the “Reproducible with” versions
8. Close the project
9. Using version control, revert all the changes done to the Project in step 7
10. Open the project using the initial project version
11. Enter Play Mode
12. Observe the Console
Expected result: Messages logged in step 4 and step 12 are the same “Integral value of Player is 0“
Actual result: Messaged logged in step 4 is “Integral value of Player is 0“, while message logged in step 12 is “Integral value of 2 is 2“
Reproducible with: 6000.0.0b11, 6000.0.1f1
Not reproducible with: 2022.3.28f1, 2023.3.0b10
Couldn't test with: 2021.3.38f1 (this is the initial project version)
Reproducible on: Windows 10 (By user), Windows 11
Not reproducible on: No other environment tested
Note: CQA used GitHub for version control, but any version control should do
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
- 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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
There are no fixes planned for this Bug