Search Issue Tracker
Fixed in 2020.2
Fixed in 2020.1
Fix In Review for 2019.4
Votes
0
Found in
2019.1.0a3
2019.3.15f1
2019.4
2020.1
2020.2
Issue ID
1252289
Regression
Yes
[WebGL] Application throws an exception and/or shows incorrect values when Mathf methods are passed as Func<> parameter
How to reproduce:
1. Open user's attached "WebGL_Func.zip" project
2. Enter Play Mode
3. Notice that the uppermost value is "17.000" in the Game view
4. Go to File -> Build Settings
5. Make sure Platform is set to WebGL
6. Press Build And Run
7. When built, observe the application in the browser
Expected result: Application doesn't throw an exception, uppermost value is "17.000"
Actual result: Application throws an exception and/or uppermost value is "1.000"
Reproducible with: 2019.1.0a3, 2019.4.1f1, 2020.1.0b12, 2020.2.0a14
Not reproducible with: 2017.4.40f1, 2018.4.23f1, 2019.1.0a2
Notes:
- The issue is not reproducible in the Editor and on Windows, Mac build
- In 2019.3.16f1 application throws an exception and doesn't load the scene at all
- In 2020.1.0b12, 2020.2.0a14 the application throws an exception and shows wrong values in the scene
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
- Application.systemLanguage returns "Unknown" when system language is set to Norwegian Bokmål/Nynorsk
- Project fails to load scene in WebGL due to lack of memory
- Particle System's Point Light flickers while Looping is on and Emission Rate over Time set to 0 with Bursts Count set to 1
- [GLES2] [iOS] UnityGet2DClipping function returns wrong values
- Lightprobes influencing object shading on specific position is not deterministic and causes artefacts
Resolution Note (fix version 2020.2):
Fixed in: 2021.1.0a1
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0b7
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.11f1