Search Issue Tracker
Fixed
Fixed in 2022.3.61f1, 6000.0.45f1, 6000.1.0b13, 6000.2.0a8
Votes
1
Found in
2022.3.48f1
6000.0.21f1
6000.1.0a1
6000.2.0a1
7000.0.0a1
Issue ID
UUM-82983
Regression
Yes
Numeric field expressions do not provide correct results when used in a public float field in the Inspector
Reproduction steps:
1. Open the attached “Broken Numeric Field.zip” project
2. Open the “BugReport” Scene
3. Find the “Select all Cubes” GO in the Hierarchy
4. Expand that GO and select all of the child Cubes
5. In the Inspector find the ‘Test Script’ Component
6. In the ‘Some Value’ property enter “L(0,5)”
7. See the ‘Some Value’ values of the different selected Cubes
Expected result: All Cubes have different values
Actual result: All Cubes have the same value
Reproducible with: 2022.2.0a9, 2022.3.48f1, 6000.0.21f1
Not reproducible with: 2021.3.44f1, 2022.2.0a8
Reproduced on: Windows 10 (User reported), Windows 11
Not reproducible on: No other environment tested
Notes:
- The expressions work correctly when used in the Transform component fields
- Hard to pinpoint the exact regression point as from 2022.2.0a9 (and through alpha and beta versions) the values just have a value of “0” no matter the input
- Also reproduces with the R(a,b) function
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sprite Importer Checkbox Label Truncated in UI (2D Template)
- Light theme icon is missing for Volume Component in the Inspector window
- Volume Profile effects are still showing and active in Game View when the Volume Profile is reset
- Shader Graph Tab Lacks Right Margin for Long Titles
- 2DLight component only renders when ShadowCaster2D components are within range in WebGL builds
Add comment