Search Issue Tracker
Won't Fix
Votes
1
Found in
2023.3.0a12
6000.0.0b11
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-17953
Regression
No
[Perforce] Assets with Unicode characters in their file name cannot be added/submitted to Perforce
How to reproduce:
1. Create a new project in your preferred workspace and open it
2. Connect it to Perforce and disable "Automatic Add"
3. Create a new material, add it and submit it
4. Change its name to "Ä", observe that the material is now gone from the Project Window (Refocus the Editor to make the asset reappear)
5. Try to add and submit the renamed asset
6. Observe the error
Expected result: assets using Unicode characters appear in the Project Window right away after getting renamed and they are addable/submittable to Perforce
Actual result: assets using Unicode characters disappear from the Project Window upon getting renamed and can't be added/submitted to Perforce correctly
Reproduced in: 2020.1.0a18, 2019.3.0f4, 2019.2.16f1, 2018.4.15f1, 2017.4.36f1
Notes:
- If you were to rename assets in the File Explorer and submitted them through P4V that would work just fine. The Editor seems to be adding files incorrectly and files that were renamed/added in the Editor won't be submittable through the CL/P4V as well.
- Plastic SCM seems to handle Unicode characters just fine in the Editor
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
This issue will be revisited in 6 months. We will take into account while we prepare to create a better P4 plugin.