- From: Jasper St. Pierre <jstpierre@mecheye.net>
- Date: Sun, 3 Nov 2019 07:58:41 -0800
- To: public-gpu@w3.org
- Message-ID: <CAA0H+QQz8u0GbGS9Q66e+RUFK+myHkqOtOBfC7uuiwd+6KbjZA@mail.gmail.com>
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
Received on Sunday, 3 November 2019 15:58:55 UTC