Forum Widgets
Recent Activity
Can I use the OVR Manager alongside Unity's XR Origin Rig ?
Hello ! I'm a student making a game on Meta Quest 3. I'm leveraging Unity' XR Interaction Toolkit to make most of the game but I'm wanted to enable some Meta Quest native features. Notably, I wanted to use the OVROverlayCanvases but this imply using the OVR Manager as well. I desperately attempted to find any source of information about using both Unity's built-in XR systems and the ones provided by the Meta XR Core SDK, to no avail so far. Is dealing with both simultaneously a no-go or is there some critical configuration to make it work ? Does Unity's XR Origin or the OVR Manager take precedence over the other (specifically on the Tracking origin mode) ? Thanks a lot for your help and your time !
Cannot set Meta Quest Link as active OpenXR runtime normally
Hello! We are developing a PC-VR app in Unity with Meta Quest 3 at our company. We use OpenXR plugin to build the code around OpenXR standard in order to support more platforms in the future. However, the button to set the meta quest link as active runtime for open xr never works on our test PCs. We've tested multiple laptops & PCs in the companies and none of them seem to be work without us manually setting the path in the registry. We've tried starting the Link app as an admin, installed it as an admin etc. One time the registry entry doesn't even get added automatically after installing Meta Quest Link App and we had to install "OpenXR for Windows Mixed Reality" to create it without writing a script to automatically create the group entry ("HKLM\Software\Khronos\OpenXR\1") in the registry. Could anyone help clarify what is up with this case and how we can resolve it? Otherwise the setup process is basically impossible for our potential customers without in-depth technical support... Thank you! References: https://community.khronos.org/t/openxr-directory-not-existing/111184
Getting Analog Values from Joysticks in Spatial SDK Native Android App
Hi, I am trying to create an app that can track the joystick push values as continuous values rather than discrete pushed/not pushed. I am using the Spatial SDK and it seems to only expose getters such as ButtonThumbLL which return an Int representing whether they were pressed or not. I saw a similar post about 4 months ago that was left unanswered: Interface of getting Controller joystick travel range | Meta Community Forums - 1336257. I am curious if anyone knows and idiomatic way of getting the continuous values of how far the joysticks are pushed. Thank you.Is it possible to use hand tracking with just one hand?
Hi everyone! I’ve been experimenting with ways to give players a more super-real experience. After attending a gesture recognition session yesterday, I started thinking about removing the hand controllers entirely, but there’s a problem: without them, I can’t let players move through hand tracking alone. My game includes boss fights that require precise movement to dodge attacks. So I’m wondering, is it currently possible to have one hand use gesture tracking while the other hand uses a controller joystick for movement?
Finding lost controllers
Wouldn’t it be a great idea to add a feature on the meta horizon app where you can just click a button and it makes a noise in our controllers so we can find our missing controllers like me and I’m sure, many other people would be happy to spend extra money for a controller that can be found by sound. (I don’t know where else to say this so I said it here)
HorizonOS v81 update broke Passthrough in startup Splash Screens
Hi folks, This is for a project in a C++ UE 5.5.3-0+oculus-5.5.3-release-1.109.0-v77.0 engine from official Oculus Branch. A recent update to Horizon OS, likely v81, seems to have changed the way Splash screens are handled to now send the user to a black void with particles and wisps flying by. This has created a big problem for our MR application in that now NO Passthrough is visible during splash, which is causing us to fail VRC (Functional.14). This was not an issue before this OS update. These are the settings and image (PNG with transparency) we are using: Even forcing bAutoEnabled to True in DefaultEngine.ini does not help: Setting to Black also gives the same result, which is the black void with a very low resolution proxy of the PNG we have: For reference, this was the behavior before the v81 update: We also scouted other MR apps and it seems they face similar situations (?) Any help is appreciated as we'd rather not request any waivers during our QA process. Thank you! -Sebastian
