Garrett Johnson

> I can’t wait until browsers actually have WebGPU enabled! 🫠 It's already enabled in Chromium-based browsers, including mobile, and it can be enabled via flags in Firefox and Safari....

I've added a condition that includes the lines that break the shader when `#USE_SHADER_RAYCAST` is included in the location hash: https://gkjohnson.github.io/three-mesh-bvh/example/bundle/sdfGeneration.html#USE_SHADER_RAYCAST You can use that link to repro the issue....

> FWIW WebGPU specification is not a living draft yet and will be subject to breaking changes until then. Thanks - I didn't know this. I figured since it was...

https://github.com/mrdoob/three.js/pull/29710 will allow for copying data to and from layers of a 3d texture which will enable us to work around this 3d target rendering issue in the next release...

With r170 we can now copy 2d textures into array texture layers directly which bypasses the issue, it seems. It would be great to actually have 3d targets working correctly...

I'm not familiar with the internals here but the prior behavior was incredibly odd and undocumented. It doesn't make sense that if you have 5 components call `invalidate` in a...

I understand if this needs to be reverted because ramifications aren't clear but I'm hoping this is something that can be reopened as a higher priority bug. Are there other...

Is there an update on the state of this? Was it reverted? Or fixed? If it was reverted can we keep this issue open?

When submitting an issue please follow the template and submit the information that's requested - you haven't provided enough information to say exactly what the issue is. My guess is...

> Ok I updated the issue, the far away value is "x": -3761603.743620786, "y": 4105279.00727716, "z": 3870314.8490743843. it looks like a low poly version of my object when it's far...