Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
5.6.1p1
Issue ID
943141
Regression
Yes
TextMesh Renderer bounds changed between 5.3 and 5.6
We rely on measuring the renderer bounds for text in our game to ensure it fits within the container. The bounds in 5.6.2p3 are slightly tighter, which is causing them to interact differently with our systems.
I imagine this results from an intentional (if under-communicated) change in Unity, so I imagine you're not willing to change it back. Could you please describe what changed in sufficient detail that we can make our systems treat the new bounds like the old ones?
These sorts of changes are what make Unity upgrades painful for us.
I've attached 2 unity projects for different unity versions that demonstrate the change.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity freezes when opening a project
- [Silicon] Artifacts appear in the Game view when resizing the window/entering the Play Mode in a specific project
- Marker in the animation’s preview window doesn’t stop when reaching the end of the timeline and jumps to the start of the animation when moving it with the cursor
- Animation Event marker is not placed on the current time of the timeline when using the “Add Event” button
- Editor crashes on vector_map<ConstantString,AssetBundle when using the LoadAssetAsync function
Add comment