-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Kludgine work on the web #49
Comments
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:
What isn't working:
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. |
easygpu has been updated to wgpu-0.8.1. Progress has been made, shader code is executing. However, the shader isn't compatible with naga without enabling The other challenges that I knew I ran into last time but didn't address here:
|
With the rewrite, this is now going to be blocked by khonsulabs/appit#1 in addition to some of the previous findings. |
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.
The text was updated successfully, but these errors were encountered: