Bela Bohlender
Bela Bohlender
Interactions in react-three/xr v6 now work just like in the whole react-three ecosystem, which means that the [pointer-events concept](https://developer.mozilla.org/en-US/docs/Web/API/Pointer_events) is used. [Here's a tutorial](https://docs.pmnd.rs/xr/tutorials/interactions) that gives an overview what is...
Supported in v6. See this [tutorial](https://docs.pmnd.rs/xr/tutorials/object-detection).
dom overlay is now supported in 6.1 so I am closing this :)
Postprocessing with threejs unfortunately does not work in WebXR. This is not related to this repository though, just a [limitation of threejs](https://github.com/mrdoob/three.js/pull/26160).
this example requires node 18 because it uses vite mkcert (which requires fetch) to be able to run in WebXR other examples should work without node 18
Sorry, I was wrong, I removed WebXR from the example earlier, so it doesn't need mkcert anymore Fixed in 4e09568de3197da34c37451b412d960de9d48237
@ricklove On what device and browser are you experiencing these z-fighting issues? I cannot reproduce Can you test if this behavior also appears on other devices (e.g. your smartphone) ?
Fixed in adac3593a823c4644b9affa55fbdbdbbb5ec08f4
Thanks for the PR The problem with this implementation is unexpected behavior for ```jsx ``` To implement the expected behavior for this case you want to create a new property...
Yes, but the current implementation in the PR turns ``` ``` into `transformTranslation={[1,2,3]}` I already described how to preserve the order of jsx properties when applying them :)