Search Issue Tracker
By Design
Votes
0
Found in
2019.3.0f3
2020.1.0a16
Issue ID
1204700
Regression
No
[URP] BoatAttack demo throws emscripten error
-e: when running the demo in a browser the following error is being thrown
--the error is not being thrown when creating a new URP project from the template
--tested and repro with 19.3f3 + 20.1a16, Chrome & FF latest
-repro:
--get the demo at https://github.com/Verasl/BoatAttack (used the "demo-work" branch)
--import into latest Unity
--Build&Run for WebGL
--open browser console
--NOTICE one error being thrown
---Looks like you are rendering without using requestAnimationFrame for the main loop. You should use 0 for the frame rate in emscripten_set_main_loop in order to use requestAnimationFrame, as that can greatly improve your frame rates!
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2020.1.X):
This is a harmless error. Unity is correctly using requestAnimationFrame for the main loop. The error is caused by a separate update timer that triggers a frame update if the main loop is too slow, which is happening at the beginning of boat attack load.