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
- Unity Cloud icon does not appear next to project and does not connect correctly when the project is created with Cloud but closed right after creation
- ScrollerSlider in the Scroller Control is still using UXMLTraits
- Crash on ExtractHandles when shutting down the Editor in a specific scene while Burst jobs are in progress
- Unity Hub closes with no "Project is currently open" window when selecting an already open project from the Projects list
- The Hub freezes indefinitely when copy/pasting a lot of characters in the “Set project display name” Hub window since it has no character limit
Stardog
Oct 31, 2025 19:32
Solution is to check floatValue.IsNaN() before using that float as the parameter.