Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.2.16f1
2023.1.0b12
2023.2.0a11
Issue ID
UUM-33384
Regression
No
Setting ulong's and uint's values to negative is possible through the Inspector and the values handled/reported are incorrect when accessing them through a SerializedObject
Reproduction steps:
1. Open the attached “BugSerializedCopy.zip” project
2. Select the “Assets/A.asset” ScriptableObject from the Project window
3. Observe UINT and ULONG values in the Inspector window
2. Open the custom DemoWindow from the Menu bar (Demo > Window)
3. Observe the UINT and ULONG values in the custom DemoWindow
Expected result: Inspector shouldn’t accept negative values for UINT and ULONG and in the DemoWindow the values should correspond to the ones set in the Inspector
Actual result: UINT and ULONG shows extremely high values that aren’t equal to the ones set in the Inspector
Reproducible with: 2022.2.16f1, 2023.1.0b12, 2023.2.0a11
Couldn’t test with: 2020.3.47f1, 2021.3.23f1 (Script errors)
Reproducible on: Windows 10 Pro (22H2)
Note:
1. Inputting negative values from the Inspector into the uint and ulong fields shouldn’t be possible in the first place
2. Same/similar (incorrect) behavior is seen through the JSON property reported as well
3. Testing 2020.3 and 2021.3 streams was unsuccessful due to the errors in the user’s script, however, the behavior should be the same, thus the issue should be present in 2020.3 and 2021.3 streams as well
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
- Shader Graph Swizzle Node Input/Output and Mask Update Incorrectly After Undo
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.