Search Issue Tracker
Fixed
Fixed in 6000.0.16f1, 7000.0.0a1
Votes
0
Found in
6000.0.15f1
7000.0.0a1
Issue ID
UUM-77418
Regression
No
Some default UxmlConverters are dependent on the Current Culture
Some default UxmlConverters are dependent on the Current Culture{}.{}
For example, new Vector2(123.45f, 234) will be saved as "123,45,234" which will later fail to be parsed from UXML.
Most types are failing when being converted to string, but Length fails when converted from string.
Steps to reproduce:
1. Open attached project
2. Run in Test Runner
3. Observe failure when running tests
4. If you comment out line 38 in the test (where Frenc culture is set), tests are passing
Actual results: Tests are passing
Expected results: None of the Uxml Converters dependent on the Current Culture
Reproducible with versions: 2023.2, 6000.0.15f1
Not reproducible with versions: N/A
Can’t test with versions: Earlier than 2023.2 (API did not exist)
Tested on (OS): Mac Intel
Notes:
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 6000.0.16f1):
Converters will not depend on the specific culture of the machine