Search Issue Tracker
Fixed in 1.0.0-preview.7
Votes
0
Found in [Package]
1.0.0-preview.2
Issue ID
1222972
Regression
No
[InputSystem][Editor] Generated C# file is not checked out when overwriting
When using Perforce or PlasticSCM for version control, assets must be checked out for write access. The importer currently just goes and tries to overwrite file contents if the generated code has changed. This will fail if the asset is write-protected (IIRC Perforce indeed write-protects the files whereas PlasticSCM doesn't).
We need to communicate with the VCS integration to check out files, if needed.
May make sense to forego code-generation in this scenario. Something to consider.
Repro:
1. Create project and set up Perforce integration for it.
2. Create .inputactions asset, enable "Generate C# Class" for it and check it in.
3. Check out the .inputactions asset, edit it, and save it.
Result: the .inputactions asset importer will try to overwrite the .cs file and thus produce an error because the file is read-only.
Expected behavior: The importer should first check the file out using Unity version control APIs.
Also, try saving out the `.inputactions` asset without checking it out. This results in an exception.
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
- Shader Graph Swizzle Node Input/Output and Mask Update Incorrectly After Undo
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
Resolution Note (fix version 1.0.0-preview.7):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1111