Search Issue Tracker
Fixed in 1.1.0-preview.2
Votes
0
Found in [Package]
1.0.0
Issue ID
1254502
Regression
No
ProjectSettings.asset is checked out in perforce when building a project with the Input System package installed
How to reproduce:
1. Create and open a new project
2. Install the Input System package
3. Connect the project to perforce
4. Open P4V
5. Add and Submit the Assets, Packages and ProjectSettings folders
6. Build the project in Unity
7. Open P4V and refresh
Expected results: no changes are made
Actual result: ProjectSettings.asset is checked out in the default Changelist
Reproducible with: 0.2.10-preview (2020.2.0a14), 0.9.6-preview(2020.2.0a14), 1.0.0(2019.3.16f1, 2019.4.0f1, 2020.1.0b12, 2020.2.0a14)
Could not test with: 0.2.8-preview and earlier (the package doesn't compile)
Notes:
-When the project is built for the first time the "preloadedAssets: []" line changes into "preloadedAssets: - {fileID: 0}"
-If the project gets upgraded to a newer version of Unity, another "- {fileID: 0}" line gets added upon building
-On further builds the ProjectSettings.asset file gets checked out without any changes made to it
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
- Standard Unity Materials and Shaders become corrupted after importing specific Asset Packages
- [Linux][OpenGL][Vulkan] Draw calls are not shown in the Event List when taking a capture of a frame with RenderDoc
- Inaccurate collision detections when Rigidbody Collision Detection is set to "Continuous" or "Continuous Dynamic"
- Crash on Object::IncrementPersistentDirtyIndex when upgrading project version
- [iOS] Multiple Xcode project instances created before opens up when performing Build and Run for iOS Platform
Resolution Note (fix version 1.1.0-preview.2):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1202