Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2018.4
2019.4
2019.4.8f1
2020.1
2020.2
Issue ID
1277994
Regression
No
Material SetInt and GetInt methods are not precise when large values are used
How to reproduce:
1. Open the attached project named "Material_SetInt"
2. Open the Main Scene
3. Enter Play mode
4. Observe the output from the Test.cs in the Console window
Expected result: The input and return values match
Actual result: The value returned from the material which was set using the SetInt does not match the original value
Reproducible with: 2018.4.27f1, 2019.4.11f1, 2020.1.6f1, 2020.2.0b3
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
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
Resolution Note (fix version 2021.1):
Fixed in - 2021.1.0a2. We have added an `Integer` type together with the corresponding `SetInteger/GetInteger` API and are going to deprecate Int type in the future. These methods should now be used instead of the old `SetInt/GetInt` to resolve this issue