Search Issue Tracker
By Design
Votes
1
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
2020.1.0a9
Issue ID
1191871
Regression
No
[VCS] [Perforce] Changing file name capitalization for assets that are added to version control fails
How to reproduce:
1. Create a new project in your preferred workspace
2. Open it and connect it to Perforce
3. Create a new material named "Test" and submit it
4. Try to change its name to "test"
Expected result: the material is renamed without issues
Actual result: the material name is reset back to "Test" upon completion
Reproduced in: 2020.1.0a9, 2019.3.0b7, 2019.2.10f1, 2018.4.11f1, 2017.4.33f1
Note: only reproduces on Perforce, Plastic SCM lets you change file name capitalizations just fine
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
This is a behavior enforced by the P4 client. Casing in P4 in general is tied to the OS as per information here: https://community.perforce.com/s/article/3081
To see whether your Perforce server supports sensitive case handling use "p4 info" in the command line.