Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.3p1
Issue ID
953672
Regression
No
Unsigned Long (ulong) value input range is identical to Long in Inspector
Steps to reproduce:
1. Open attached “DataTypes.zip” Unity project
2. Open “Test” scene
3. Select “Data” object in Hierarchy
4. Change “Unsigned Long” value in Inspector to 18446744073709551615
Expected results:
Unsigned Long value is 18446744073709551615
Actual results:
Unsigned Long value is 0
Reproduced in: 2017.3.0b2, 2017.2.0f2, 2017.1.1p3, 5.6.3p4, 5.5.4p5, 5.4.6f2
Note: Negative values can be entered even though the ulong data type is unsigned. Entering any value higher than 9223372036854775807 in Inspector will result to value being 0.
-
krakentanz
Sep 19, 2022 14:34
One possible workaround seems to be (if you don't need editing capabilities) to mark it as [DisplayAsString] if you have OdinInspector at hands. That way Unity won't f***k up your variables...
-
krakentanz
Sep 19, 2022 14:27
shit indeed
-
saltfishgames
Jul 03, 2021 05:32
shit
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
- Physics.IgnoreCollision method does not work when used on a disabled GameObject
- Empty data buffer gets passed to OnAudioFilterRead when using Video Player
- The Update() method gets called on a disabled script when added and disabled during runtime
- URP Decal instanced rendering breaks and spams warnings when it is enabled at runtime
- Ligtmaps disappear when entering the Play Mode
Resolution Note (2020.2.X):
Currently we dont support unsigned long long int (UINT64), adding support for it will require a lot of changes and could cause many regressions.