Search Issue Tracker
By Design
Votes
0
Found in
2021.3.40f1
2022.3.37f1
6000.0.9f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-75119
Regression
No
Components do not accept a comma in float values when using operators
Reproduction steps:
1. Open the “ReproProject“ project
2. Open the “Assets/Scenes/SampleScene“ scene
3. Select the “Cube” GameObject in the Hierarchy window
4. Type “0+1,5“ into the Position of the “X" axis of the Transform Component and press the “Enter” key in the Inspector window
5. Observe the Transform Component in the Inspector window
Expected result: The “X” axis value is changed to “1.5”
Actual result: The “X” axis value is changed to “1”
Reproducible with: 2021.3.40f1, 2022.3.37f1, 6000.0.9f1
Reproducible on: Windows 11 Pro (22H2)
Not reproducible on: No other environment tested
Notes:
1. Does not reproduce if not using operators in the value field, for example “1,5”. Reproduces only if using operators “0+1,5”
2. Does not reproduce if using a dot instead of a comma
3. Reproduces in other Components as well, not just the Transform Component
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
- Animator Controller Layer name stays unchanged in Layers tab when renamed from Inspector
- [RenderingDebugger]Motion vectors are displayed when Phong Tessellation is used on the material and Skinned Motion Vectors are enabled on the GameObject's Skinned Mesh Renderer component
- Shader Graph Enum Keywords always select last element in Entries when Stages is set to Fragment and Recursive Rendering is enabled in the Scene
- [Mac] Glitchy visual artifacts appear when moving around a scene with Sphere Handles
- Crash on memcpy_repmovs when selecting NavMesh Agent objects while in Play Mode in a specific scene
Resolution Note:
As we need to support expressions with decimal points like `R(1.2,3.5)` we cannot support the comma as a decimal in an expression. This is as designed.