Search Issue Tracker
Fixed in 2017.2.0f3
Votes
0
Found in
2017.2.0a3
Issue ID
919294
Regression
Yes
INVALID_UTF8_STRING error in the Font Names field when upgrading a project to 2017.2
Steps to reproduce:
1. Open the attached project (UnityTest.zip)
2. In the Assets folder click on "arialbd"
3.Observe the error in the Font Names field
INVALID_UTF8_STRING
Expected result: Font Names should be shown
Actual result: Error in the Font Names field
Reproduced with: 2017.2.0a1, 2017.2.0a2, 2017.2.0a3
Not reproduced with: 5.4.5p3, 5.5.3f1, 5.5.4f1, 5.6.1p3, 2017.1.0b9
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment