Hand Tracking menu ruins game play
The first thing people do with hand tracking is look at their hands. The second thing they do is touch their fingers. Then Quest shuts down the game; because that's the hand gesture Meta chose as an 'escape' key. I encourage players to see/feel their hands in the experience because it is so much more enjoyable and immersive. Literally the entire point of mixed reality. This menu punishes all that fun with a distracting, overly sensitive button that apparently cannot be disabled. But can it be delayed? Ideally, the icon would not appear until after touching (and holding) thumb/finger together for 2 seconds, then become active (similar to holding controller's menu button down to reset view). I understand Quest "needs" an escape gesture, but not if it constantly interrupts everything. Anyone else dealing with this? Found another solution or workaround?
Announcing the XR Accessibility Project on Github
Hi Oculus developers. The XR Access Initiative and XR Association have created a new resource for XR developers: the XR Accessibility Project! This Github repository is intended as a place for developers to find helpful guidelines and code snippets to create accessible XR applications. We're hoping that the XR Accessibility Project is able to grow over time, as more developers utilize it and submit the resources they use. We encourage you to take a look, and if you think of something that would be useful for other developers, submit it using the contribution form. You can also submit other comments by creating an issue on Github. We know it's hard enough to develop for XR platforms, let alone to do so accessibly; but we hope this resource will help make sure everyone, regardless of ability, can enjoy the great applications you're making. Best, Dylan Fox Coordination and Engagement Team Lead, XR Access
How to disable Quest recentering in Unity XR 2019.3?
Previously we could just call `ovrp_SetReorientHMDOnControllerRecenter(false);`, and set the tracking level to stage, but using the XR Plugin workflow, it looks like even though this method returns true, it's not honored, and the recenter will still teleport you manually. The comments layout why you would want to disable it: > /// If true, the Reset View in the universal menu will cause the pose to be reset. This should generally be > /// enabled for applications with a stationary position in the virtual world and will allow the View Reset > /// command to place the person back to a predefined location (such as a cockpit seat). > /// Set this to false if you have a locomotion system because resetting the view would effectively teleport > /// the player to potentially invalid locations. Also, `ovrp_GetAppShouldRecenter()` seems to always return false, even during a recentering operation. So I have no idea why AllowRecenter used to work on the Quest, but the calls appear to not be working now, in 2019.3. So, in 2019.3, using the new XR Plugin system -- how can I disable location recentering, so that the player can't use it to teleport behind walls, etc.?window.requestAnimationFrame not working in newest 33.3 Meta browser in WebXR mode
I used window.requestAnimationFrame inside a WebXR app, which previously work fine in the Meta Browser, but it seems automatically update to 33.3 on June 3rd, and now this function only works when I press the Meta button to pop up the browser but not work at all when I hide the browser and enter the XR mode. Any helps? Maybe I need to change the function? But I don't see an alternative to count frames accurately. Basically I want to have a timeManager that supervise the timing of different assets in the app.