This demo seems to have fallen by the wayside:
Just wondering the state of it.
Yes, I’m running Babylon inside a Web Worker using Offscreen Canvas.
While some parts, such as standard camera input, rely on the DOM and will need to be rewritten, it basically works without any issues.
However, it’s important to note that Web Workers come with their own costs.
Creating a separate thread increases startup time and memory usage.
Also, while this might be an issue with the browser’s implementation or my own implementation, rendering isn’t as smooth as it is with a non-OffscreenCanvas. To put it another way, it feels like it’s always rendering at 59 fps.
We use it quite intensively internally at MSFT too
cc @RaananW as it seems we may have a problem with current devops changes
checking
EDIT - I believe this is a caching issue because this should have been resolved already. I am redeploying just to be sure and purging the CDN’s cache, will check right after.
Works for me, please check as well just to be sure
It does work now eventually, reeeeally slow to load for a scene with one model imho.
It does work though, “please wait loading…” never goes away however..
I didn’t think the startup time syuilo mentioned would be quite so profound.
We are working on modernizing all demos.