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
Rendering to OffscreenCanvas on non-yielding workers #403
Comments
|
Thanks for the prompt reply @kainino0x :) It will be great if we can have (2) because I am currently working on porting AutoCAD to Wasm and being able to render directly from the Worker without having to transfer control back to the main thread would be a huge plus. |
@kainino0x and @Kangz , can I check if OffScreenCanvas is currently available for WebGPU in Chrome Canary on Windows now? If not, is there an estimate on when it will be ready? Thanks. |
@awtcode I don't think any of the WebGPU implementations have OffscreenCanvas right now. In Chromium it is blocked on some internal code refactor so it won't be available at least until the end of the year, maybe more. |
Thanks for your reply @Kangz . |
Hi @kainino0x -- do you happen to know the status of the internal refactor? I'm really looking forward to accessing WebGPU from Web Workers. Thanks! |
@s11k It's still ongoing (but had recent progress). You can follow along this Chromium bug. |
FYI offscreen canvas is completely working in WebGPU in Chromium now. Closing now since this was more of a question on WebGPU than a spec discussion. |
This reverts commit bddeaea.
Hi,
I currently execute my code in a Web Worker and does not yield the context back to the browser because everything happens in a while loop. As such, I need to pass the OffScreen Canvas back to the main thread for rendering.
Here are my questions:
The text was updated successfully, but these errors were encountered: