Problem with update v7
After automatically updating to v7 my games are not working: -the FOV is reduced -Only right control is visible by default -Left control is visible only when pressing a button, on release is back to reset position (0,0,0), not affected by tracking. i'm using Unity 2019.1. Apparently lost of devs are having issues, is there any way to revert the update? Regards
Developer documentation updates for the week of July 15th, 2024
Hello Meta Quest Developers! Here are the latest developer.oculus.com documentation updates for the week of July 15th, 2024. Updates: Introducing Acoustic Ray Tracing. Acoustic Ray Tracing is a new tool included in the Meta XR Audio SDK that simulate how sound propagates from its source to the listener based on actual game geometry. (Unity, Unreal) A new Unity topic Getting Started with Interaction SDK and Unity XR has been added. “Meta XR Interaction SDK Essentials for Unity can also integrate with Unity’s OpenXR and XR Hands packages enabling potential for cross platform development.” The Unity topic Mixed Reality Utility Kit Features has been updated with new guidance and screenshots. Additionally, the MRUKStart component has been deprecated and replaced with a SpawnOnStart property instead. The Unity topic Mixed Reality Utility Kit Samples has been updated with new samples. The Unreal topic Mixed Reality Utility Kit Getting Started has been updated with new guidance for v66 and v67. The Unreal topic Passthrough Relighting has been updated with new guidance and troubleshooting. The topic Depth API for Unity has updated requirements, new info on permissions, a new section on Using the API with code samples, guidance on shader graphs, and info on adding occluded objects to the scene. The topic Body Tracking for Movement SDK for Unity has updates for prerequisites, clarified steps for configuring the project, and other improvements. Minor updates: The Platform Solutions topic Multiplayer Overview has minor updates for clarity (Unity, Native, Unreal) The following Unity topics have minor updates for clarity: Get Started with OVRSceneManager using Building Blocks (deprecated) Unity Plane and Volume Scene Sample (deprecated) Use OVRSceneManager (deprecated) The Use Capsense topics have minor updates for clarity (Unity, Native, Unreal) The Use Simultaneous Hands and Controllers (Multimodal) topics have minor updates for clarity (Unity, Native) The Platform Solutions topic Achievements has minor updates for clarity (Unity, Native, Unreal) The Meta XR Simulator Introduction topic has minor updates for clarity (Unity, Native, Unreal) The Developer Tools topic Use Meta Quest Scriptable Testing Services to Enable E2E Testing has minor updates for clarity (Unity, Native, Unreal) The Platform Solutions topic Subscriptions has minor updates for clarity. The Platform Solutions topic In-App Purchase Server to Server APIs has minor updates for clarity (Unity, Native, Unreal) The Platform Solutions topic App Deep Linking has minor updates for clarity and improved images (Unity, Native, Unreal) The Passthrough topic Passthrough API Overview has minor updates for clarity (Unity, Unreal) A number of topics have been updated to remove outdated branding references. Removed topics: The following Unity topics have been removed because they are now included in the MR Utility Kit samples: Unity Bouncing Ball Scene Tutorial Unity Bouncing Ball Scene Sample Unity Virtual Furniture Sample Last week’s post: Developer documentation updates for the week of July 8th, 2024
Platform settings in Unity takes the wrong credentials
Hello there, In Unity, the Oculus Platform settings state that the credentials used are these from the Oculus application. Looks like this is not the case for me, and I'm not able to resolve the situation so far. I reinstalled the Oculus desktop app, I used that "Restart Oculus" feature from the desktop app in the Beta section, deleted the plateform settings and letting Unity regenerate these, still somehow connected to the wrong account. What am I supposed to do ? Thank you.
Software updates
V25 is terrible and I still don't have V26. Developers should be among the first to get new software updates. But the bigger problem is that the software update process is too slow. I understand (*) that phasing the distribution is important but it's truly awful right now. * I've written software entitlement/licensing/distribution systems for large downloads w/CDN integration.
Can't get user's Oculus ID with dev builds in the headset
Hello there, Prior the last unity sdk update, we were able to get the Oculus ID of the current user when we were testing devlopment builds in the headset (without pushing the build on the dashboard). Now I can still get user's informations, like his username, but the ID is always the same, and this is the one that you can find in the API section of the app : "Your application specific user ID for debugging and testing." How are we suppose to test features like Voice Chat if the real user ID is not exposed anymore ? Are we supposed to push a new build on the dashboard every time ? Or am I misunderstanding something ? Thank you,
