3 ms·
Absolutely, yeah. I've actually just opened an issue for this: https://github.com/AmbientRun/Ambient/issues/1038 https://github.com/AmbientRun/Ambient/issues/10
by Philpax 3y ago
Absolutely, yeah. I've actually just opened an issue for this: https://github.com/AmbientRun/Ambient/issues/1038 https://github.com/AmbientRun/Ambient/issues/1038
Rest assured we'll have this sorted for the next release; we were aware that Linux/Chrome/WebGPU were incompatible, but we didn't bubble that error up correctly. Our bad!
- FredrikNoren 3y agoIt's fixed on the website now as well (it'll show you a nice warning screen on non-webgpu browsers, instead of just loading forever)
- riskable 3y agoI have enabled webgpu in Firefox (set `dom.webgpu.enabled` to true) but it just says, "your browser does not support WebGPU". No, actually it does support WebGPU it's just that you're not detecting that properly.
- FredrikNoren 3y agoHm yeah, we need to fix the detection as part of instantiation, which happens in the engine. I'm adding a "Try anyway" button for you in the meantime, it should be up in a couple of minutes.
- Philpax 3y agoWe've just tested internally with Firefox nightly with WebGPU enabled (you should also be able to test this with the fix Fredrik just pushed out), but it doesn't seem to work - Firefox's WebGPU implementation doesn't implement enough of the spec [0] to be able to run our renderer. As I mentioned in another comment, we're considering adding a fallback renderer, but our hope is that Firefox will be able to complete its implementation sooner rather than later - as a Firefox user, I would much rather use it than Chrome myself! [0]: https://github.com/gpuweb/gpuweb/wiki/Implementation-Status#firefox-and-servo https://github.com/gpuweb/gpuweb/wiki/Implementation-Status#...