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
- Packman: The same asset data is displayed differently in "Import" and "Remove" popups
- Reference to a deleted GameObject becomes "None" instead of "Missing" when the GameObject is restored with undo after entering and exiting Play Mode
- Size value in Particle System Curve's tab is highlighted with selection across all tab header
- Particle System Curve's Presets window has no visual indication of what preset is selected
- Blur shader doesn't work when the "Scene Color" Node is attached to the UI "Output" Node
Resolution Note (fix version 1.0.0-preview.7):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1111