Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
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
- SetComponentEnabled uses class instead of struct when constraining Enableable Component type
- [iOS] Application.deepLinkActivated does not get invoked while app is running when UIApplicationSceneManifest is added in Info.plist
- Inspector scroll area stretches when using components with nested serialized arrays on FBX model prefab instances
- Crash on ConstraintProjectionTree::projectionTreeBuildStep when ConfigurableJoint uses JointProjectionMode.PositionAndRotation and connected Rigidbody switches from kinematic to non-kinematic
- ScriptableObject asset is accessed during the lookup of Build Profiles when opening the Build Profiles Window
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
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.15f1