Search Issue Tracker
Fixed
Fixed in 2021.3.X
Votes
0
Found in
2021.3.0f1
Issue ID
UUM-12741
Regression
No
Project Settings keeps appending {fileID: 0}
Forum users have reported that when using the new input system, an "\{fileID: 0}" string keeps getting appended to the projectsettings.asset file:
[https://forum.unity.com/threads/project-settings-keeps-appending-fileid-0.954147/]
Although this was supposed to be fixed in:
They are still reporting this issue, including in 2021.3 on WebGL, Windows, MacOS, and Linux. This needs investigating.
Here's a brief conversation about this in #devs-input: [https://unity.slack.com/archives/C09Q7LYP9/p1660762430036649]
I'm unsure if this is a regression so I'm going to go with No. I'm making it a public ticket for users to track progress.
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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-296
Resolution Note (fix version 2021.3):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-296