Solved

I'm currently trying to get some haptic feedback when grabbing an object in Unreal, but so far no result, no matter what the controllers will simply never vibrate. Here's the blueprints currently used to get the rumble effect :Hope someone will be able to find a solution.

I’m trying to set up my Quest, and the iPhone app says to enter the 5 digit code displayed-but there is no code. How do I find this code?

Hello other meta users, my mom recently got me an oculus 2. I am already having trouble with it. First, it says I have not a lot of storage, and when I delete some of my apps and photos, it only goes down a few percentages, and I don’t know if that is the main cause to my second problem with the oculus. Secondly, when my sister just got done playing job simulator she had canceled an update, and it has been having problems ever since. It won’t stop powering off and powering on and restarting. I contacted meta-and they had told me to do a factory reset. Now, I know how to do a factory reset, but it would not let me do a factory reset, I know that you have to shut off your VR headset, I know that you have to hold down the power button and the volume button, but it keeps restarting when I try to do it. And when I almost succeed, it says the words. “No command” I don’t know if I have a messed up something inside my headset but it would be great if a worker from Meadow could help me figure t

Hi my right controller won’t turn in or pair. Tried factory reset and app reboot

I am wondering if there was a reason why it is taking 5+ hours to download a 1Gb game on a 75Mbps Internet connection. I am hoping that because Oculus Quest has sold out and it is christmas day, the Oculus Servers are having a hard time with the large influx of new devices. Unfortunately i feel alienated with that hope because it seems as if i am the only one suffering with this problem. I am concerned to troubleshoot my internet as it would cancel my download wich is at 80% currently, but it works fine on my phone and laptop.

Just doing a mental health check. Often times the strongest people are available for everyone else and no one is available for them. Hope everyone has the most amazing week 😘 Just remember to check on your strong friends.

Hi everyone,We're currently developing a mixed-reality (MR) game for the Oculus Quest 3, which involves physical movement within a real-world space. To enhance immersion, we utilize the passthrough feature extensively and need to disable the Oculus Guardian boundary system.Currently, the only way we've found to disable the boundary requires players to activate Developer Mode on their accounts, which isn't ideal for general users. We're looking for alternatives that allow us to disable the Guardian boundary without requiring users to change their account settings.Additionally, our development process involves recording gameplay, for which the boundary needs to be enabled, but we would like to maintain passthrough vision. Is there a way to enable just the passthrough and disable the boundary for recording purposes?Has anyone here worked with similar settings or encountered these issues? Any advice or suggestions would be greatly appreciated.Thanks in advance for your help!

A critical issue has arisen with the recent update of the Meta Quest Link application to version 68.0.0.433.361. In summary, all of our applications based on Khronos OpenXR and Unreal Engine 4.27.2 can no longer be run via Link. This means that the vast majority of our customers can no longer access our applications. Additionally it prevents our Unreal Engine developers from being able to use tethered Meta devices. This issue has been confirmed for Meta Quest 2, 3 and even Rift S devices.This issue has been confirmed in vanilla Unreal Engine projects also. We have traced the failure to the OpenXR runtime layer. OpenXr API calls such as xrEnumerateInstanceExtensionProperties fail to return any valid extensions, which prevents the Unreal Engine being able to communicate with the headset. We believe that other people may be having the same or similar issues with the recent update:https://steamcommunity.com/app/1849250/disussions/0/4515506358400756962/https://www.reddit.com/

Hi there,so right now I am using several objects in my MR-Scene that are based on the NetworkGrabbable-BuildingBlock.They work fine so far, but when I try to release them from my hands, it feels “sticky”.The object has, similar to the cube that it's based on, a Box-Collider as “Trigger” and a Mesh collider.But, as seen in the image, the Box-Collider is larger than the object. Is that Boxcollider responsible for the “grabbing” and “releasing”-Area, and could it be that I just need to make that smaller? Or am I possibly **bleep**ing something up here?Anyone experienced in that?

Hi, I just did a fresh install of the Oculus UE build 5.1 and the new SS release to see how it worked, and I'm getting an error when trying to install the packaged project to my Quest2.db: failed to install SharedSpaces-arm64.apk: Failure [INSTALL_FAILED_OLDER_SDK: Failed parse during installPackageLI: /data/app/vmdl1751123627.tmp/base.apk (at Binary XML file line #8): Requires newer sdk version #33 (current version is #29)]It appears to be an SDK issue, I have 33 installed via android studio, but I'm not sure if there's something I need to do via unreal/ the SS project ?? Any feedback would be welcome since this appears to be a new issue with this particular setup.SharedSpaces4x + OculusUE4x works by default without this error.

Hey,   I just bought my Quest 2 and I used my Facebook account to register. It still says that I need to pay for Beat Saber. How I can redeem my free copy?

My son's left controller keeps disconnecting itself then has issues with re-pairing .

I'm trying to use Hand tracking in my app and no matter what the Hand scale stays at one event with a friends hands that are much smaller.After some investigation, and a lot of debugging, I found that the hand scale is calculated for the first frame of the application and is at like 1.1 before it gets switched back to 1 for ever.A "solution" I found is to switch of the update root scale parameter of my hands and I could then scale them depending on this initial value but as per the documentation says, the root scale is supposed to get updated during runtime. (The documentation is pretty empty on everything though and it's never detailled how they are supposed to be mesuring that).Does anyone managed to have the root scale update for their hand tracking ?If yes, could you share some insight with me ?  

VR preview cannot be run in Unreal 5.0 and 5.1. (VR preview is available in 5.2 and 5.3.) If anyone knows a solution to this problem, please reply.

I'm developing a native C++ OpenXR app for the Meta Quest 3 but I can't seem to properly set the api version to anything other than XR_MAKE_VERSION(1, 0, 0)Ideally this should work assuming I'm using a supported OpenXR version:XrApplicationInfo applicationInfo; applicationInfo.apiVersion = XR_CURRENT_API_VERSION;However this results in a:xrCreateInstance: API Version [281479271677988] not within supported range [281474976710656,281474976710656] If you do the math 281479271677988 is 1.1.36 and 281474976710656 is 1.0.0If I use XR_API_VERSION_1_0 as shown in the example here: https://developer.oculus.com/documentation/native/android/mobile-openxr-instance-session/It works without any issues. But I can't seem to set it to the correct version. At the time of writing this Meta OpenXR SDK 67.0 is based on OpenXR 1.1.36 https://developer.oculus.com/downloads/package/oculus-openxr-mobile-sdk/ I'm guessing the discrepancy between what version of 

Just bought an Oculus Quest 2 yesterday, set it up and played around with some of the pre installed stuff and some free demos, but for some reason I'm not able to buy games on the store. I tried two different cards from different banks on the Oculus itself, the app and a desktop computer and none of them worked. The desktop and app both gave an error along the lines "something went wrong" and the Oculus told me that my bank needed further authentication and to check my email which i did and it just had a link back to the store and gave me the same error again. I also did not receive any messages from the banking app for either card asking me to authorise a payment. 

So until now ive been able to just connect the link cable and use my headset on the pc freely now suddenly the pc app wont even recognize the headsets been plugged in, which kinda sucks since all my games are on the pc so basically cant do anything with my headset until a new update or a fix unless i want to buy the games over again. Not sure what to do to fix it 

Hi,I am developing an OpenXR PC VR app through oculus link and I am trying to get the global mesh using my Oculus Quest 3 headset.I am following the code of XrSceneModel sample and I am able to get the global mesh.I call xrGetSpaceTriangleMeshMETA and I obtain indices and vertices of the global mesh.The problem is when I try to obtain the pose of the global mesh referred the xr local space of my app.The function xrLocateSpace returns invalid handle.I am sure that the handle of my local space is valid so I think that the handle of the global mesh is not valid.In fact if I try to call xrLocateSpace for the global mesh referred to the XrSpace of the mesh itself I get invalid handle.Is it a bug or something not supported?Thank you  

Hi,I have spent the last two years developing for the Quest 2, and recently got the Quest 3. It's a great device and I'm super happy with it. There is just one big problem standing between me and total developer bliss.How is it possible that we still don't have a stable, robust hand tracking implementation across the whole development pipeline in 2023? I'm confused as to how Meta envisions developers to take full advantage of their (really good) hand tracking tech, if there are consistent inconsistencies, fumbling around, trying seven different versions of all of the little SDKs, components, etc.Can someone please advise me on how to achieve a simple Unity scene using the standard Oculus Integration, where I can just click "Play" in the editor and get hand tracking working over my Link cable?So far I have gone through five different Unity versions from 2021-2023, even more different Oculus Integration SDK versions (v50-57), and three different headsets (Quest 1, 2 and 3). Not

Hi, I bought the Quest Pro and love it, and develop for both PC VR and Android.I would like to know if Local Dimming will ever work on PC through OpenXR via Link or AirLink, or if it will be possible to enable it in the runtime somehow, like Link Sharpening is.I paid good money for this headset and I expect all its features to work on PC. I'm a pro developer and need PC vs Android builds to have visual quality parity and local dimming missing on PC is a glaring oversight, in my opinion. It's simply unacceptable to spend 2000$ and not be able to use local dimming for PC VR games and apps.If we can't enable it at a platform level on the headset itself, then if could at least consider a way to add it to Link / AirLink options in a similar way that LinkSharpening was, that would be great. If not, allowing us to enable it through OpenXR as it is on Android, would be fine as well.If this isn't done by my Amazon return window of Jan 31st, 2023, I will be returning the Quest Pro for a full ref

HiI am using Oculus SDK v66 in Unity and I use the interaction quick menu to add ray interaction to my UI canvas. Now, the only way I can interact with the UI Buttons is with the index trigger button. I would like to bind another button for interacting with the UI. How can I change this input binding?

I've got a 1 star review on my app saying the user is unable to find the game in his library... and I want to get this removed as this is an Oculus issue not an app issue. As per the documentation, there's a way to request that by clicking "Request Moderation" from the developer's dashboard on the review popup. https://developer.oculus.com/resources/user-reviews/but that button doesn't exist... What kind of a platform is this.. omg (btw I'm posting this knowing 100% that no one from Meta will bother to even read it...)

I cannot enable hand tracking in the Meta XR Simulator. In simulator settings, I do not see checkboxes to select/unselect hand tracking (screenshot attached). The controller simulation works fine. I have followed the documentation in https://developer.oculus.com/experimental/xrsim-hand-tracking/ and tried using Meta Building Blocks, but nothing seems to work. 

OS: Windows 11Quest Model: Quest 2 (more than one)Link Cable: Multiple third party cables made for Quest 2PC: Multiple PC setups including laptopsHello,I'm not necessarily here to ask a question, but I want Meta to be aware of an ongoing issue with the Oculus Software on Windows 11 (I haven't tested on 10).For the past year(?) I have been experiencing an issue where Quest Link either: fails outright with an error message, displays a black screen with three dots indefinitely, or I get video but no audio despite the audio settings being correct in 1) Oculus Software, 2) Windows, 3) In the game. I have tested on a slew of different devices all running Windows 11 including desktop PC's and laptops. I have also tested several different third party cables, and even with different Quest 2 headsets.The issue presents itself at seemingly random. Some times it works flawlessly. Most of the time, however, it requires 1) replugging the cable, 2) Restarting Oculus Software, 3) Restarting the PC, 4)

So I'm trying to get my app to AppLab, and I'm getting the following: APK is debuggable (android:debuggable in AndroidManifest.xml). NOTE: you may only distribute debuggable APKs through private channels. Android Target SDK version is 29, but should be 32 or greater (targetSdkVersion in AndroidManifest.xml).   NOTE: Your manifest includes the following permissions restricted by Oculus: - android.permission.WRITE_EXTERNAL_STORAGE - android.permission.READ_EXTERNAL_STORAGE - android.permission.READ_MEDIA_AUDIO - android.permission.READ_MEDIA_VIDEO - android.permission.READ_MEDIA_IMAGES - android.permission.ACCESS_MEDIA_LOCATION - android.permission.READ_MEDIA_IMAGE - android.permission.WAKE_LOCK Please remove these permissions if they are not needed by your application. If they are needed, you must include justification in the “Notes for the Reviewer” field when submitting your application for review. Failure to provide justification will result in the rejection of your application.