Search Issue Tracker
Fixed
Fixed in 2021.3.31f1, 2022.3.11f1, 2023.1.15f1, 2023.2.0b10, 2023.3.0a4
Votes
0
Found in
2021.3.29f1
2022.3.6f1
2023.1.6f1
2023.2.0b2
2023.3.0a1
Issue ID
UUM-43504
Regression
No
Vector3Field SetValueWithoutNotify triggers RegisterValueChangedCallback when used with float.NaN
Reproduction steps:
1. Open the “NaNVectorNotify_Stripped” project
2. Choose the Window menu > NaN Test
3. Click “Set to NaN” and observe the Console
Expected result: RegisterValueChangedCallback is not fired because SetValueWithoutNotify is used
Actual result: “RegisterValueChangedCallback…” was logged
Reproduced in: 2021.3.0f1, 2021.3.29f1, 2022.3.6f1, 2023.1.6f1, 2023.2.0b2
Reproduced using: macOS 13.4.1 (c) (Intel), Linux 5.15.0 Ubuntu 22.04.2 (by reporter)
Notes:
1. Not reproduced with an individual FloatField
2. Could not test in runtime because Vector3Field is specific to the Unity Editor UIElements system
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2023.2.0b10):
Fixed UUM-43504 @laila-chammaa:
UI Toolkit: Fixed Vector3Field SetValueWithoutNotify triggers RegisterValueChangedCallback