Search Issue Tracker
Fixed
Votes
0
Found in
2020.1.0f1
Issue ID
1268037
Regression
No
Gradient.Evaluate does not understand Time variable in a build when Time is calculated inside Evaluate method argument
Steps to reproduce:
1. Open User's attached project "project2020.zip"
2. Build it with the Developer build option on
3. Open the build and click on the Mesh
4. Notice the error in the console "Evaluate: time is not a valid number"
Expected results: Mesh Changes color
Actual results: Mesh does not change the color due to Gradient. Evaluate does not understand time calculation
Reproducible with: 2019.4.7f1, 2020.1.1f1, 2020.2.0a20
Notes: This only reproduces in a build. The issue does not reproduce in 2018.4 according to the user and updating the project from 2018.4 to 2019.4 and 2020 versions fix the issue. I was not able to reproduce the error, however, the raycast didn't seem to detect the mesh anymore, the same happened when updating the project from 2018 to upper versions. A video of expected and actual results are attached
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Stardog
Oct 31, 2025 19:32
Solution is to check floatValue.IsNaN() before using that float as the parameter.