-
Notifications
You must be signed in to change notification settings - Fork 57
[Feature]: Support for WebGPU on Xbox #4150
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
Comments
I was just looking at Platform and API support for Dawn/Tint and it currently notes:
So I suppose this is something the Dawn WebGPU implementation does not yet implement. It'd be great to see support though. |
This feature is not only crucial for web gaming, but also indispensable for Microsoft's flagship Office 365 suite, which relies heavily on WebView2 as its core rendering engine. Office 365 applications, a cornerstone of Microsoft's productivity ecosystem, are increasingly utilizing WebView2 to provide a unified and consistent experience across both desktop and web platforms. As Office 365 continues to evolve, particularly with the integration of more advanced features that demand high-performance GPU capabilities, the need for full WebGPU support in WebView2 becomes imperative. The ability to select and leverage the best available GPU through APIs like await navigator.gpu.requestAdapter({"powerPreference":"high-performance"}) is essential for optimizing performance in Office Add-ins, which are integral to the productivity suite’s functionality. Without full WebGPU support, these applications cannot fully utilize the hardware capabilities of modern systems, leading to potential performance bottlenecks and a less optimal user experience. Given that Office 365 is one of Microsoft’s most widely used products, ensuring that WebView2 can support different GPUs seamlessly across all platforms is vital. This enhancement would not only benefit game developers, but also millions of Office 365 users who rely on these tools daily. Enabling WebGPU in WebView2 across all platforms, including the new Teams client and other Office apps, would therefore be a significant step forward, aligning with Microsoft’s commitment to delivering cutting-edge performance and functionality in its premier software products. |
That would be really helpful! |
+1 |
1 similar comment
+1 |
on side note, there is no webgl/webgpu/wasm on playstation's (dialog) web browser. |
Uh oh!
There was an error while loading. Please reload this page.
Describe the feature/enhancement you need
Ref discussion: #4138
WebView2 on Xbox One does not appear to support WebGPU, even though WebView2 on Windows does. Support for WebGPU is potentially important for web games as it allows for better performance and rendering features.
For a minimal repro, just point a WebView2 at this URL: https://webgpu.github.io/webgpu-samples/samples/helloTriangle
It works in WebView2 on Windows, but on Xbox One it reports
TypeError: Cannot read properties of null (reading 'requestDevice')
. Note it does not say thatnavigator.gpu
is undefined, so this appears to indicate the WebGPU API is implemented, but no adapters/devices are available.AFAIK Xbox One supports DirectX 12, so in theory WebGPU support is possible as it's designed to work on top of DX12, but perhaps there are some Xbox-specific details that need to be implemented.
The scenario/use case where you would use this feature
High-performance web games in WebView2.
How important is this request to you?
Nice to have. There are other ways to tackle this, but having official API support would be beneficial.
Suggested implementation
Hopefully this is only a matter of providing access to the GPU device on Xbox. AFAIK Xbox supports DirectX 12 which is one of the backends WebGPU was specifically designed for, and it works on Windows already, so in theory all the technology is there.
What does your app do? Is there a pending deadline for this request?
We're looking to add support for publishing high-performance web games on Xbox from our game development tool Construct.
AB#47690642
The text was updated successfully, but these errors were encountered: