https://playground.babylonjs.com/#KBS9I5#36570
The scene loads normally in WebGL but throws errors directly in WebGPU mode
There is a small bug in the shader.
This PR fixes it:
You can try it out here:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15361/merge/index.html#KBS9I5#36570
Result:
You rock dude!
Thank you, but credits goes to the Chrome WebGPU team! The WebGPU error messages on Chrome are so verbose (finally what the developers deserve) so just a completely uninvolved would miss it
If I correctly remember Safari was/or still is very stingy when it cames to spitting out the error message associated with especially the framebuffer completeness GL errors. Nothing is reported to the console. You had to have a great time while debugging stuff for Safari while working on babylon.js
So did I when tried to be cool (loyal to the brand lol) and use Safari to try out WebGL stuff.