Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.37f1
2022.3.26f1
2023.2.20f1
6000.0.0f1
Issue ID
UUM-72122
Regression
No
Vertical mapping of most characters is incorrect when using a Texture on each character
How to reproduce:
1. Open the “TextMeshProBugs.zip“
2. Open the “TestUvMapping Vertical MatchAspect“ Scene
3. Observe the Scene view
Expected results: All characters are uniformly affected by the texture, and feature only one cycle of the texture
Actual results: Characters m, M, w, and W feature only one cycle of the texture, while the other characters have noticeably more cycles of the texture applied
Reproducible in: 2021.3.37f1, 2022.3.26f1, 2023.2.20f1, 6000.0.0f1
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Notes:
- Each character has a different texture stretch to it
- All horizontal with “Line“ vertical mapping combinations result in g, j, p, q, and y characters being affected
- All other combinations seem to be working correctly
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Regarding the above comment, We're going to reject the issue as it's not a bug.