Search Issue Tracker
Fixed
Fixed in 1.5.0-pre.7
Votes
0
Found in [Package]
1.4.5
1.5.0-pre.6
Issue ID
LOC-1081
Regression
No
"FormatException" is thrown in the Console when Font Size is changed to a floating point number and Track Changes is enabled
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/MainScene” Scene
3. In the Localization Scene Controls window (Window > Assets Management > Localization Scene Controls), check if “Track Changes” is enabled
4. In the Hierarchy window, select “Text (TMP)” (MainCanvas > Text (TMP))
5. In the Inspector window, change the “Font Size” property’s value to a floating point number (e.g. 36.2)
6. Observe the Console window
Expected result: No errors are shown
Actual result: “FormatException: Input string was not in a correct format” error is thrown
Reproducible with: 1.4.5 (2022.3.18f1) (By user)
Reproducible on: Windows 10 (By user)
Not reproducible on: No other environment tested
Note: Not reproducible by CQA
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Particle size is not correctly reflected in Edit Mode when a particle system is used as a Sub Emitter
- [Usability] No warnings about having sufficient space before generating the Lighting
- "Invalid AABB inAABB" and "Assertion failed on expression: 'awake.loadStarted'" errors are thrown when when instantiating a prefab with InstantiateAsync
- Line Break Position Changes in Traditional Chinese when consecutive punctuation is used
- Tutorial Case - [First] Depth of field does not apply correctly to UI elements
Add comment