Re: Trying WebGPU samples on Chrome Canary on Windows 10

Hey Jasper,

It looks like the BabylonJS demo bitrotted although I'm not sure exactly
how. +CC Sebastien that made the demo.
Glitch seems to have problems at the moment and I cannot access it. I'll
try again later.
However all the WebGPU samples work great on my Win10 machine. We can look
into it, can you open a bug at crbug.com under the WebGPU component and CC
cwallez@chromium.org? A paste of your about:gpu would certainly help!

Cheers,

Corentin

On Sun, Nov 3, 2019 at 4:59 PM Jasper St. Pierre <jstpierre@mecheye.net>
wrote:

> Windows 10 finally has WebGPU support on Chrome Canary. However, I cannot
> seem to run any of the samples. Have the samples simply bitrotted, or is
> something else going on?
>
> The sample at
> https://hello-webgpu-compute.glitch.me/hello-compute-chromium.html has a
> CORS issue with GLSLang:
>
> > Access to script at '
> https://unpkg.com/@webgpu/glslang@0.0.7/web/glslang.js' from origin '
> https://hello-webgpu-compute.glitch.me' has been blocked by CORS policy:
> The 'Access-Control-Allow-Origin' header has a value '
> https://austineng.github.io' that is not equal to the supplied origin.
>
> I'm not sure why unpkg.com sends a CORS header... that doesn't seem great.
>
> The samples at https://austineng.github.io/webgpu-samples/#helloTriangle
> do not seem to generate any errors, but they do not render anything for me.
> I do not know if WebGPU support on Windows 10 is incomplete, or if the
> samples are not updated for the new spec.
>
> The BabylonJS Forest demo (
> https://www.babylonjs.com/demos/webgpu/forestwebgpu ) seems to complain
> about missing assets:
>
> > Uncaught (in promise) TypeError: Cannot read property 'asset' of
> undefined
> >    at e._getLoader (babylonjs.loaders.min.js:1)
> >    at babylonjs.loaders.min.js:1
>
> Are there any samples out there that are working with latest WebGPU on
> Windows 10?
>
> --
>   Jasper
>