Passthrough and hand tracking, hand size
Hi, I managed to use both hand tracking and passthrough with new Unity2021.2.5, OculusXR plugin 1.11.0, XR Plugin Management 4.2.0. 🙂 But the hands are smaller then my own hands. OVR Custom Skelteon script with update root scale seams to do nothing. Is there a way to have the hands the same size, like we have in quest home environment.
Not receiving 2FA confirmation code via text to enable dev mode
As the title says I am not able to set up my two factor authentication code with my phone number because I simply do not receive anything via text message from Meta. I have tried my girlfriends phone number and she also receives nothing. We both have different carriers... Is there any solution to this? I would really like to enable developer mode.. I have zero numbers blocked, I am receiving other automated texts just fine. Never had any problems with that, only with Meta.Oculus Go + browser + videos won't play
Apologies in advance I'm not familiar with how things work around here but I was hoping someone could answer if not resolve the issue I'm having whenever I try to play a video in the oculus browser and the Firefox browser. When the video starts to load and play it glitches and I'm paraphrasing the error message that comes up basically saying it's unable to play, something along those lines. When I factory reset the device the videos will play just fine but after awhile they'll regress and won't play. Is there an update or downgrade I have to do? Or is the oculus go obsolete now? Any help and answers would be greatly appreciated thank you in advance!!!
Meta Ray Ban to PC
Man super disappointed that the glasses can’t connect to my PC. My old razor did but the sound wasn’t great. I work from home and thought it’s perfect for meetings. Prob going to return it now. So stupid to limit it. Is it capable for over the air update? Wonder if it can batch an update to allow PC use. Then I def would buy it again or keep this one.
Can't get the SceneModel
Hey guys. I'm having an issue of pulling the SceneModel (Room that I have Setup) from any of the scenes in the The World beyond that use the OVRSceneManager to load the SceneModel. I've been using TheWorldBeyond (https://github.com/oculus-samples/Unity-TheWorldBeyond) to try and get this running. I have also created several new projects on many different versions of Unity (2020.3.18f, 2021.3.18f & 2022) and tried the VirtualFurniture Scenes from the Oculus Integration SDK - receiving the exact same issue as below. I've tried default/different combinations of Build Settings, Package versions and Platform types (PC/Mac/Android) and still had no luck. I've attempted some of the solutions in this thread (https://communityforums.atmeta.com/t5/Unity-VR-Development/OVRSceneManager-can-t-query-scene/td-p/98... I tried this on Windows 11 and Windows 10 and got the same error message. Anchor support is set to Enabled as per the project default. No matter what I've tried, I always receive the same error message - I'm just unable to pull the Room I've setup: (PassthroughPet Scene) (PassthroughRoom) (TheWorldBeyond Scene) I have tried building the scenes using both a PC and a Mac, and each time I load into the scene, it says "The World Beyond requires Scene Data. Please run Room Setup". I've ran the Room Setup around 30-40 times, trying different variations of wall numbers/desks/doors - still no luck of retrieving that data or even running The World Beyond build. HOWEVER, strangely, when I download the The World Beyond straight from the Oculus Store, it runs absolutely fine, it finds the room I've mapped and lets me continue with the experience. This seems to be a Unity only issue? I contacted a friend who tested this on his Quest 2, and he was able to simply download the The World Beyond Unity code and click Play and have instant working access to the SceneModel. He was also able to build The World Beyond and go straight into the experience without the message above coming into play. As mentioned, I've tried it on a PC and a Mac, still the same issue. I bought a second Quest 2 headset today to test this out, and still received the same issue. The only visible difference between my two Quest 2 headsets, and my friends Quest 2 headset, is that my versions are 49.0.0.207 and his version is 49.0.0.186 (an earlier one by a few weeks I think?). Can you give me a hand getting this resolved? Message if there is any more detail needed. Cheers guys
