I think its on my end as per (updateFloatArray vs webgpu) post. Ran into the issue while adding the wgsl, set it aside, finished the rest and tried starting the webgpu engine (thinking it was all done). Will have to wait for the next release to confirm…
I see the huge dump in console from dbgShowShaderCode, what should I be looking for? Eyeballing, it seems everything is in wgsl. Do I have to export and dig thru? I have shaders still not in wgsl yet but since they are not loaded at startup, there should be no impact?
For the record, csp errors (sniped) are below. I’m not sure what stance to take on this, best to defer to the core team. But users should know what they are getting if bjs is supplying the libs from cdn…
wasm streaming compile failed: CompileError: WebAssembly.instantiateStreaming(): Refused to compile or instantiate WebAssembly module because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive:
failed to asynchronously prepare wasm: CompileError: WebAssembly.instantiate(): Refused to compile or instantiate WebAssembly module because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive:
CompileError: WebAssembly.instantiate(): Refused to compile or instantiate WebAssembly module because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive:
CompileError: WebAssembly.instantiate(): Refused to compile or instantiate WebAssembly module because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive:
Uncaught (in promise) RuntimeError: abort(CompileError: WebAssembly.instantiate(): Refused to compile or instantiate WebAssembly module because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: