257 Photon fusion compiler errors though i use Photon Pun 2
basically i use Photon pun 2 and i downloaded the meta sdk for in app purchases and Meta quest In game usernames but now i have almost exactly 257 compiler errors cause i dont use fusion and when i try Re downloading it and importing it, my project crashes and doesnt open again. Please help (editor version 2022.3.62f1)16Views0likes0CommentsGame crashing on restart
Hello. I'm developing a game for Quest 2 and 3 and have encountered issues with the game crashing on Quest 2. The weird thing is that only crashes on some of our quests, some of them work fine while others will start the game once then crash when trying to the start the game again. There are no noticeable differences between the Quest 2 headsets either. The source of the crash seems to be this error: MemoryBroker: INPUT_TYPE_MAP: client com.DefaultCompany.Game does not have access (app ops or VR focus). I have tried multiple solutions like forcing a clean shutdown and INPUT_TYPE_MAP permissions but none of them seem to work. I think it's likely related to the RAM use of the game but there is not much more I can to do optimize it further and shouldn't be needed either since it works normally on other headsets.79Views0likes2CommentsMeta Quest white color saturation with OpenXR
Hello I am trying to build a VR application for Meta Quest 2/3 headset with Unity 2022.3.7f1 using OpenXR. However, when I build a pure white object, or whatever. The color appearing inside the build won't be pure white, it is something around RGB=(243,255,255). I tried many things such as URP Settings, OVROverlay, switching to HDR, environment light, texture compression to None, Graphics API to Vulkan, Color Gamut to Display-P3, OVRManager's Color Gamut to Unknown, Unmanged,etc... I can't think anything else. There is no light baking in my scene, nothing else than a pure white object. Can someone provide me some ways to prevent that please ? Here are my Unity settings :62Views0likes3CommentsMeta XR SDK broken between 74 - 77
It looks like the Unity play mode linking to headset is broken as of SDK 74 almost 6 months ago. I've been trying to get a new project going with all of the latest versioning - SDK 77, Unity 6000.1.13f1 and everything I've been doing is by the book from the latest documentation I just have the camera block and interaction grab block and when I press play the screen on my oculus goes black for 2 seconds and then back to the Link environment. I've tried Unity 6000.0 and 2022 as well and same issue. When I do a build it builds and runs fine on the headset, but I can't preview anything with the play button After trying all of the different Unity versions, I found this thread on the Unity forum which narrowed it down to headset functionality breaking at 74, so I installed 72 and lo and behold the headset connects fine - passthrough and everything... but the interactions don't work. Hand tracking and controller tracking are broken both in editor and when I build, so using 72 is a non-starter if I can't interact with anything. Anyone have any solutions for this? I need hand/controller tracking and passthrough as I'm making an MR project. I tried Unity's XR and while it connects to the headset and has controller tracking it doesn't have good support for quest, no passthrough and seemingly no spatial tracking. I'm new to the Meta SDK, this is my first time using it. Last time I did VR dev I was using Steam SDK on Vive, so my knowledgebase on how to set this up from scratch is outdated. If any of you have any pointers toward where I should look for a solution for this, I'd appreciate it. Thanks!259Views1like6CommentsMQPro Controller Tracking turning OFF when kept somewhat still + Bug with InputTrackingState
When a Meta Quest Pro Controller is kept relatively still (even if your hand is shaky!), the tracking gets disabled until a couple of moments after a large movement. I have disabled auto-switching to hand. The biggest issue is that during this time, InputTrackingState/InputActionProperty flag isn't appropriately set to show that tracking is invalid. This applies to both: `UnityEngine.InputSystem.XR.TrackedPoseDriver.trackingStateInput` and `UnityEngine.XR.Interaction.Toolkit.currentControllerState.inputTrackingState` So, how do I prevent the controller tracking randomly turning off OR how do i detect when it turn off??62Views0likes4CommentsPerformance issues after building APK for Meta Quest 3
Hi everyone. I'm new to VR development and just created my first VR project in Unity for Meta Quest 3. When I run the game through Unity Link (Oculus Link) from my PC, it works smoothly with good graphics and no lag. My PC has 32 GB RAM and the game uses around 9 GB while running. But when I build it as an APK and run it directly on the Quest 3, I get problems like lagging, lower graphic quality, flickering, and sometimes low memory warnings. I know Quest 3 has only 8 GB RAM, so that might be part of it. But I would really appreciate help on how to optimize the game for Quest 3, what settings or methods I should use to reduce lag and improve quality, and whether there are tools to check what is using up memory on the Quest. Thanks a lot. I'm learning and want to get better at building for VR.65Views1like1CommentHow to remove snap interctor from the snap interactable?
My cube with the snap interactor snaps just fine to the snap interactable, but when I try to grab and remove my cube, the position transforms weirdly as if it was still connected to the snap interactable. I am sure I have set up my scene fine. Has anyone had a similar issue before?35Views0likes1CommentHow to properly set up an AR/XR Unity project for Meta Quest 3 to get past the 3 dots loading screen
I am developing a Meta Quest 3 (v74 for my OS with SDKs version being the lates the time of writing - v72) application in Unity 6 41f1 (and 29f1), where I currently struggle to get the application working past the loading screen (the 3 dots) in on the apk, while in the editor it just works, hovewer I would like to access functions that are not available in the player and even then my target platform in the Meta Quest 3 standalone platform. While running adb logcat -s Unity the result I get this log lines which peek my curiosity: W OpenXR : xrGetVulkanGraphicsDevice2KHR: Called twice. OpenXR : PostSessionStateChange:[pid: 18824] XR_SESSION_STATE_FOCUSED -> XR_SESSION_STATE_VISIBLE OpenXR : PostSessionStateChange:[pid: 18824] XR_SESSION_STATE_VISIBLE -> XR_SESSION_STATE_SYNCHRONIZED OpenXR : PostSessionStateChange:[pid: 18824] XR_SESSION_STATE_SYNCHRONIZED -> XR_SESSION_STATE_STOPPING Handle cmd APP_CMD_WINDOW_INSETS_CHANGED(17) Handle cmd APP_CMD_GAINED_FOCUS(7) Handle cmd APP_CMD_LOST_FOCUS(8) Handle cmd APP_CMD_PAUSE(14) Handle cmd APP_CMD_RESUME(12) Handle cmd APP_CMD_STOP(15) 03-10 10:29:46.300 7012 7044 W Unity : Orientation Listener cannot detect orientation. 03-10 10:29:47.098 7012 7044 W Unity : Your project uses a scriptable render pipeline. You can use Camera.stereoTargetEye only with the built-in renderer. 03-10 10:29:49.306 7012 7044 I Unity : Handle cmd APP_CMD_LOW_MEMORY(10) 03-10 10:29:46.301 7012 7044 I Unity : Handle cmd APP_CMD_LOST_FOCUS(8) 03-10 10:29:46.301 7012 7044 I Unity : Handle cmd APP_CMD_GAINED_FOCUS(7) 03-10 10:29:46.301 7012 7044 I Unity : Handle cmd APP_CMD_PAUSE(14) 03-10 10:29:46.301 7012 7044 I Unity : Handle cmd APP_CMD_RESUME(12) (Being paused and resumed repeatedly - run without focus is enabled) xrEndFrame frameTransaction failure detected, might due to compositor frame blocking, swapchains not marked as used-in-frame 2270 The number 2270 is arbitrary and you could insert any other number instead of this. I am asking if there is an extended documentation and what version of the Unity Editor to use, to work with the development of XR/AR applications with the latest possible feature set without any errors? I am interested in usage of the scene semantic classificators and the upcoming camera API.Solved377Views1like2Commentsupdated metaXR-all-in-one xr sdk from v67 to v77. associated script cannot be loaded
I have updated metaXR all in one sdk from version 67 to v77 latest. I'm using unity 2022.3.21f1. Lots of files used in the project is having problem. should i revert to the last used version? What i have done to fix this? after updating i got this issue "OVRProjectConfig exists but could not be loaded. Config values may not be available until restart." first deleted the package cache folder under library. and restarted unity to regenerate those files incase if any package is causing issue. also deleted the OculusProjectConfig.asset file under oculus directory in assets. it got regenerat I restarted the unity editor. now i'm getting this earlier issue can anyone look into this issue. Thanks in advance. tdmowrer​ any idea?101Views0likes2Comments