Diego Marcos
Diego Marcos
```html ``` With the above a default camera is injected incorrectly
Chrome has switched from vendor specific APIs to OpenXR. [Oculus and Valve have shipped experimental runtimes on their respective beta channels](https://immersiveweb.dev/chrome-support.html#getting-openxr). It requires users to opt in. Once the OpenXR...
Reported by several users. I think the Oculus Browser is reporting `oculus-touch` [profile](https://github.com/immersive-web/webxr-input-profiles/tree/main/packages/registry/profiles/oculus) instead of `oculus-touch-v2` I couldn't confirm because I don't have a Quest 1 around at the moment....
Viewport resizing in Safari / iOS still giving us trouble. I spent a few hours unsuccessfully looking for a solution. Found a couple of suggested fixes in the links below....
The hand tracking WebXR API has changed on how it reports the joint pose and the [model needs to be updated](https://github.com/aframevr/assets/tree/master/controllers/oculus-hands/unity). Information I collected from 3rd party > The left...
A good place to put it would be the [webxr system](https://github.com/aframevr/aframe/blob/master/src/systems/webxr.js). [Spec](https://immersive-web.github.io/webxr/#ref-for-dom-xrsession-updatetargetframerate)
This is a proposal for a built-in post-processing API. Setting up post-processing in a comprehensive manner that works well in 2D and VR modes is not trivial to do. It...
We are using touch 1 models (shipped / sold with OG Oculus Rift). We should probably replace them with Touch 2 controllers. Probably not that many OG Rifts in use...
The strokes are drawn from one hand to the other instead of a separate stroke per hand.