ERROR_CLOUD_MESH_UPLOAD_FAILED(-400039)
Unity colocation build with MRUK, getting this error in Logcat and "host can't share the room with group xx-xx.." on immersive debugger... User ID and User profile active in dashboard, device has spatial permission enabled, project uploaded to alpha channel, my own user invited as tester, Keystore signed, tried with 4 different WIFI, no LLM has a clue... was working before upload alpha, What else should I check?
MRUK QR Tracking suddenly not working
I am making a quest3/3s app that uses QR codes for alignment, I was able to get the system working but suddenly this week I am now getting an 'MRUK Shared: queryCompleteEvent->result returned error code: -2', and QR tracking has stopped completely. The headset has stopped asking for me to confirm the environment setup before launching. I was able to confirm its broken on an old push and fresh project. I have spent most of a day trying to troubleshoot, but my best guess is something on the headset changed, and I have done all the troubleshooting steps on the headset and unity project as possible. Any ideas here would be extremely helpful. Ideally all i need is tracking, in fact, id love to remove the scene setup step, since the app is boundaryless and only uses the scene for QR code tracking support MRUK/Meta XR core/Meta Interaction/SDK Essentials all V85.0.0 Quest3 OS V2.1
Accessibility Feature Request: Conversation Focus Mode for Ray-Ban Meta Display Glasses
Hi everyone! I’m a Ray-Ban Meta display glasses user who is hard of hearing and wears hearing aids daily. I’d love to see a conversation focus mode added that prioritizes voices directly in front of the wearer and reduces background noise. In busy environments, this would make a big difference for hearing-aid users and others who rely on clearer speech in real time. If this type of accessibility feature is ever developed, I would absolutely love the ability to have it added to my glasses and would be happy to provide feedback or participate in any beta or user-testing opportunities. I’ve also submitted this through support channels, but wanted to share here in case the team is gathering feedback.
Stylized passthrough: How can i retexture walls?
Meta Horizons documentation on Scenes gives this image as an example of a Basic stylized passthrough. This looks to me like a screenshot of a stylized hall way. How can such an effect be accomplished in Kotlin without using Unity or Unreal? Can this effect also be achieved on Quest 2 or only on Quest 3(s)? The article mentions that Assisted scene capture (available on Quest 3(s) only) shouldn't be used to create such an effect.HorizonOS v81 update broke Passthrough in startup Splash Screens
Hi folks, This is for a project in a C++ UE 5.5.3-0+oculus-5.5.3-release-1.109.0-v77.0 engine from official Oculus Branch. A recent update to Horizon OS, likely v81, seems to have changed the way Splash screens are handled to now send the user to a black void with particles and wisps flying by. This has created a big problem for our MR application in that now NO Passthrough is visible during splash, which is causing us to fail VRC (Functional.14). This was not an issue before this OS update. These are the settings and image (PNG with transparency) we are using: Even forcing bAutoEnabled to True in DefaultEngine.ini does not help: Setting to Black also gives the same result, which is the black void with a very low resolution proxy of the PNG we have: For reference, this was the behavior before the v81 update: We also scouted other MR apps and it seems they face similar situations (?) Any help is appreciated as we'd rather not request any waivers during our QA process. Thank you! -SebastianBuilding NE9: A Runtime and App for AI-Driven Interactive 3D and XR Worlds
Hey everyone, I wanted to share what I’m currently building and open it up for discussion. I’m developing NE9, also known as NastyEngine 9. It’s a modular, real-time runtime designed to integrate AI systems, 3D environments, and interactive applications into a single live pipeline. Alongside NE9, I’m building a companion app that interfaces directly with the runtime. The goal is to use it as a control and integration layer where scene logic, agents, and interaction can be composed and updated live instead of being locked into a traditional editor workflow. The core idea is to treat AI, rendering, networking, and interaction as runtime-orchestrated systems rather than isolated tools. This approach makes it easier to experiment, iterate, and eventually extend into XR and VR environments. This is an active build and the architecture is evolving quickly. I’ll be sharing progress, experiments, and lessons learned as things continue to come together. This screenshot shows where we are right now in the development process. This was our first full session using Meta Quest 3 connected to our desktop via USB, running the Meta desktop app as our development workspace. We were viewing and working directly with our existing tools inside the headset to get a real sense of scale, comfort, and workflow. It was our first serious hands-on development session this way, and getting our feet wet was a lot of fun. Even just working from the desktop inside the headset made it clear that this is a platform we’re excited to build for. We’re looking forward to transitioning from desktop-based development into deeper Horizon and native XR workflows as NE9 continues to evolve. If you’d like to connect, feel free to check out my LinkedIn. Thanks for stopping by, and I’m excited to see what we can build together. https://www.linkedin.com/in/daniel-harris-0745b8374/
Hiding the Scene Mesh for AR
I feel like I've tried everything, but I cannot get my AR project to load a scene without overlaying a giant box mesh over everything. I.e. I'm looking to be able to raycast against walls, but have it look as though you're interacting with the actual walls of the room via the Quest 3 camera. I stole the setup from the MRUK Sample: I've tried messing with the Material for the GenerateProceduralSceneMesh call. I've tried asking the Room for the GlobalMeshAnchor and setting the actor hidden. I found a tutorial that recommended adding an OculusXRSceneActor to your scene and changing the static mesh class types based on anchor type - it didn't seem to do anything and apparently this class is now deprecated. Same thing with adding an OculusXRSceneGlobalMesh component and messing with the Visible toggle and the Material field - also deprecated. No matter how I mess with the materials or actor visibility it always looks like this: I'm able to use MRUKSubsystem->Raycast to interact with the walls. I just don't want to see them. What's the accepted way to hide them?
