Search Issue Tracker
Fixed in 2020.3.X
Votes
0
Found in
2019.4
2020.3
2020.3.17f1
Issue ID
1409392
Regression
No
DynamicGI.materialUpdateTimeSlice ignores a set value when hardcoding the value in a script
How to reproduce:
1. Open the user attached "GITest.zip" project
2. Open the "SampleScene" Scene
3. Enter Play Mode
4. Open the Console Window
Expected result: Only "1234" is logged
Actual result: Different values are logged together with the "1234" value
Reproducible with: 2019.4.38f1, 2020.3.18f1
Not reproducible with: 2020.3.19f1, 2020.3.34f1, 2021.3.1f1, 2022.1.0f1, 2022.2.0a11
Note:
- Reproducible on Windows
- Reproducible on a new project
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.19f1