Search Issue Tracker
Active
Won't Fix in 2023.2.X
Votes
1
Found in
2023.2.17f1
6000.0.0b14
Issue ID
UUM-68242
Regression
No
Character spacing value is not applied when using a specific font asset
Reproduction steps:
1. Open the attached “repro_IN-72301“ project
2. Open the “/Assets/Scenes/SampleScene.unity“
3. Open the “Game“ window
4. Observe how the spacing in the second row (“original“ GameObject) looks
Expected result: There are no spaces between “U“, “A“ and “D“ in the “original“ GameObject
Actual result: There are spaces between “U“, “A“ and “D“ in the “original“ GameObject
Reproducible with: 2023.2.17f1, 6000.0.0b14
Couldn’t test with: 2021.3.36f1, 2022.3.22f1 (not able to resolve the “NullReferenceException: Object reference not set to an instance of an object error” when trying to assign the “original“ font to the Font Asset parameter field)
Reproducible on: macOS 14.2.1 (user’s), Windows 10 (22H2)
Not reproducible on: No other environments tested
Notes:
* Reproducible in Player
* “update_atlas“ GameObject is a modified asset, tested with the “Get Font Features“ option enabled in the “Font Asset Creator“
* “make_new“ is a newly made asset from the font
* The correct spacing is visible in the “update_atlas“ and “make_new“ GameObjects
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (2023.2.X):
Closing as Won't fix due to 2023.2 reaching it's EOL.