Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X
Votes
0
Found in
2021.3.44f1
2022.3.47f1
6000.0.21f1
6000.1.0a7
7000.0.0a1
Issue ID
UUM-82585
Regression
No
FontEngine.LoadFontFace fails with Invalid_File_Path when the file path contains Turkish characters
How to reproduce:
1. Open the attached “BugReport.zip” project
2. Open the “SampleScene”
3. Enter Play Mode
4. Observe the Console window
Expected result: Font loads successfully from file path
Actual result: Font does not load, console logs “Invalid_File_Path”
Reproducible in: 2021.3.44f1, 2022.3.47f1, 6000.0.21f1
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
Note: FontEngine.LoadFontFace(new Font("path")) works as intended, but FontEngine.LoadFontFace("path") does not
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Animation Clip with Legacy enabled does not play when Time.timeScale is set to 0 despite Update mode set to "Unscaled time"
- Rename is enabled on subfolder empty space - "Can't rename to empty name" warning
- SamplerState Property Missing Anisotropic Filtering
- Visual glitches when using Handles API
- The RGBA color values are inconsistent when comparing two identical colors set in the Inspector
Add comment