Oculus Quest 2 Runtime Not Working/Switching to OpenXR
I'm stumped. I checked the Meta website to see if anyone has had a similar problem--and/or solved it. Sure, people have had their issues solved, but not me. As of now, I've updated my drivers (both headset and laptop), and restarted and updated everything I could think of. I also went through the SteamVR route, which didn't help either. I checked the developer portion of SteamVR settings and still couldn't switch it the runtime correctly. I went over to device manager, and made sure the USB ports were turned on and all that, weird things that Meta themselves suggested to another plea for help. Additionally, I installed the OpenXR toolkit off of the Microsoft webstore. Nothing much there... I'm going through all this because I just wanted to solve my Pavlov screen jitter issues--now I'm in a world full of problems 😕 Any help would be appreciated, please let me know!
[MajorBug] Acceleration returns 0 for all Meta Quest, on Unity and Unreal Engine
Hi, Whatever the Meta Quest version 1, 2 & 3, whatever the node or device, on Unreal Engine 5.4.4 and on Unity 2021 to 6000, the requested acceleration is (0, 0, 0) and the requested angular acceleration is (0, 0, 0). In Unity, these (0, 0, 0) vectors are obtained using the TryGetFeatureValue(CommonUsages.deviceAcceleration, out deviceAcceleration) and TryGetFeatureValue(CommonUsages.deviceAngularAcceleration, out deviceAngularAcceleration) methods (but also using OpenXR) In UnrealEngine, they are obtained using the GetRawDeviceData in a blueprints. The bug has 100% repeatabilty and is very easy to reproduce Consequently: There is no way to get the acceleration for the Meta Quest The problem is neither Unity nor UnrealEngine nor OpenXR --> is has to be a Meta bug
Developer Hub - Build Upload Failed - PROCESSING ERROR, API ERROR, ECONNRESET
I am trying to upload a new build of my game through the Meta Quest Developer Hub. I am uploading it to a private release channel for alpha testing. I am getting a number of errors after multiple attempts with a different error each time. I get upload failed errors sometimes showing Processing Error please try again later, API error, or ECONNRESET Network error. I've tried looking at the log files but Im not experienced enough to know what to do. It is strange because I havent had these issues before, I've uploaded multiple builds with the most recent being a little over a week ago. I am using unity 2021, the most recent version of MQDH, and am attempting to upload an apk and single OBB file (2.2 GB). I have tried copying the adb files associated with my unity project and pasting them into the "Meta Quest Developer\resources\bin" file path. I've also tried changing the MQDH ADB file path to match the unity version in the file path "C:\Program Files\Unity\Hub\Editor\2021.3.15f1\Editor\Data\PlaybackEngines\AndroidPlayer\SDK\platform-tools" Nothing seems to work and its more strange that different errors pop up instead of a single consistent error. I've made sure my manifest file is correct and am increasing the version and bundle code with each build, and done other things like make sure MQDH is able to pass through my firewall, tried making a fresh release channel. I also sometimes receive this error when attempting to open MQDH and I have to uninstall it and reinstall just to get it to reopen. Am i doing something completely wrong? Here are two of the errors, with the other one saying PROCESSING_ERROR please try again later. I can send log files if needed. Thank you for any help in advance!
SERIOUS ISSUE Quest Pro not Casting and I'VE DONE EVERYTHING!!
Please don't skip this isn't your run of the mill I can't get this going post. I have been working in and using the developer hub for along time and I CAN NOT GET AN ANSWER FOR THIS ISSUE! Long story short I can not cast through the Quest Pro on MQDH. When I try to cast I get the same error listed below. This used to work fine, it also worked on my laptop, now it works on neither. Also when I try to record it says the "display is off ...it's not. A few others have reported this issue with NO RESOLVE. I've tried everything, factory reset headset, factory reset PC, everything is updated, tried rolled back version of MQDH ETC and still not dice. It works fine with my Quest 2, I can also cast with the Quest Pro through sidequest AND the oculus casting website no problem but you can not record quality mixed reality content so they are worthless. This is only an issue with the MQDH and only with my Quest Pro. I'm not sure if it is the root cause but "allow usb debugging" does not pop up when I plug the pro in but it does when I plug the Quest 2 . I've been at this for weeks with no help! Everything is correct, developer mode, my developer mode account. I've tried turning developer mode on in of while the app while in the headset. I've tried different cables, different pc, even different operating systems and it STILL it refuses to work and it used to. I've toggle usb displays and developer options in the headset etc. Once again I'm not sure if this is the cause but it's the only thing different between the Quest 2 and Quest Pro when trying to cast. The worst part is it used to work, I didn't touch the headset for a month and now this.
Velocity estimation is working worse than it was when entering the tracking FOV
Hi, The black box driver estimating the handler position and velocity using, it seems, a Kalmann and an inertial filters, obtains degraded results as compared what it obtained before. More precisely, if the handler comes from outside the FOV of the tracking cameras and enters this FOV, the velocity is completely irrelevant (sometimes pointing rearward while the handler is moved forward for one or even several frames). His is easy to reproduce by printing the angle between velocity and the player camera direction, and by moving (slowly or quickly) from behind the head to in front of the head. Before throwing objects was a real pain in VR before (example : throwing objects in SuperHot VR). Either the object was falling on the floor, or the throwing direction was wrong up to 90°. Now it is worse, since the error is random up to 180°. You would have 2 ways of solving this : 1) Going back to the previous velocity and position engine, and stop modifying it (how can we expect a developed game to react consistently otherwise?) 2) Exposing the raw data (really raw, not already filtered), enabling us to do the job as we wantit to be done (I'm a scientist in image processing for 25 years) Even better, you could do both. Best RegardsQuest 2 controller vibration and Meta Haptics Studio
Hi guys, I am currently using Quest 2 and Meta Haptics Studio to design haptic feedback with controllers. In Meta Haptics Studio, vibration amplitude and frequency range from 0 to 1 without showing information about how strong they are in specific units. Could anyone please tell me how strong the vibration and frequency are when they are 0.5 or 1 in Meta Haptics Studio? Thank you!
