ecton
commented
3 years ago Today I made a significant amount of progress -- Kludgine now compiles to WASM successfully. Significant changes to easygpu were needed to support this, but the tl;dr is: Kludgine is not yet working in the browser. I wasn't expecting to have success today and am still thrilled with the progress made.
What is working:
- Async runtime integration (caveats below)
- winit event loop
- wgpu initialization
- shader loading
- most of the engine's flow up until it draws a frame, which is a significant amount
What isn't working:
- We use crossbeam for non-async channels and for a ShardedLock.
- Atomics are available on nightly, which may offer a partial solution
- Thread parking is the other half of the equation. I believe that in most cases where we're using these structures, thread parking shouldn't be an issue. However, we have to be careful and evaluate whatever replaces them. This is why the errors are being avoided right now -- I refactored the app startup code to not block, and since the structures are always free to unlock now, the situations where parking would need to happen are impossible in a single-threaded environment in wasm as I understand it.
- While I was able to reduce the original error a bit, we can't create any uniform or index buffers per gfx-rs/wgpu-rs#748
I'm very happy with the progress today. While nothing was drawn to the screen, I did succeed in getting a large portion of the engine runtime working -- for the engine to get to the location it did to crash, it means that the entire async app runtime is functioning correctly.
This issue is likely going to be tabled until the next wgpu update -- it's a goal for Cosmic Verge but it's not something that I need in the near future.
This is an issue tracking the progress of making Kludgine run in a web browser using WASM. The current status is that running in a browser is not working at the moment. The current work-in-progress attempt at a simple example working can be seen here.