OSC/WebSocket/MQTT to Quest
Hi there, I'm trying for a few days to have something working on UE4.27 and I'm hitting a wall. I've made a blueprint where i'm able to receive OSC input data from a remote laptop to a UE4.27 app that then triggers an event (for now print something or play a specific audio cue). It works flawlessly on UE4.27 but as soon as I load the project onto the quest and send that same OSC input data it crashes the app on the Quest 2. I tried different ports, data formats but still the same behavior without much logs to learn from which make me wonder if the Quest forbids such incoming IP communication ... could someone confirm whether or not Oculus Quest accepts remote information (regardless of the protocol used). Maybe I'm missing something in the settings somewhere but I couldn't find much information about it. Thanks for your response
Large map building&texture help
Hello, I'm new in Horizon Desktop App, started creating few things. I have 2 questions that needs your helps. Is it better to parent+stack everything into a single Asset after I finish building some objects? For performance issues, because my world itemwise only %3 but almost %70 in vertex limits. How can I reduce this vertex usage? I cannot adjust textures. I'm creating one, inserting into my floor, but all the stones on the floor are so big that doesn't look realistic. I want to pattern to repeat itself in a smaller scale. Thank you for your helps
Bring back Switch View to curve all windows!!!
Why did Switch View option disappeared and instead we have useless Theatre Mode that allow only one window to be curved at the same time. Flat screens are horrible in vr, who came up with this change? Or add ALL windows to be allowed in Theatre Mode and each be curved/flat and positioned wherever we want. Currently it's horrible.
How to connect and manage an Oculus VR application from my tablet?
I have created a VR application using Oculus Quest in Unity and I am in the process of creating an app on an Android tablet. I am interested in managing (running/stopping different Unity scenes or tasks within a Unity scene using Oculus Quest) from the tablet. So I need to control the application on my tablet, Oculus VR tasks/scenes. Any help or advice would be very appreciated.ADB not detecting a headset
I am trying to load an app onto my headset but it won't show up in adb device list. I have two headsets for this app to test. One headset, with the same cable and same port, is detected in the terminal. This specific headset is never detected. I have tried downloading the oculus adb driver. I have tried factor resetting the headset. I have tried simply powering down both the computer and the headset. I have tried to connect adb wirelessly (only to find it needs a wired connection first to work). I have tried different ports, cables, and computers. I am at my wit's end trying to get this thing to work, and I am hoping for some suggestions and new things to try to fix it. Thank you.
FIX THE ISSUE THAT RESULTS IN CONTROLLERS FAILING ON REGULAR BASIS
Why is meta unable to address the serious problem with controllers failing or bricking, or purple lights of death? Replaced mine 3x in month and keep getting refurbished junk. what is meta doing about this? It's costing me time, money, and a ton of frustration with terrible support & constant down time. I paid $500 for this thing but have maybe 3 full months of play time over 10 months. How is this OK?How to launch development app from within headset
I am developing an app for Meta Quest 2. When I Build & Run out of Unity, the APK correctly launches on the headset. I am also able to directly download the APK to the device using the Meta Quest Developer Hub (MQDH) and launch it using MQDH's file manager. But once such a development build is on the device, how can I launch it directly on the device, without needing to go through MQDH file manager? The app is listed in MQDH's file manager, but no icon appears in the app library on device.ADB with wifi without a usb connection
Hi there, We have a VR project, which requires us to use 20-40 Quest 2s and a mobile hotspot device for a local network. Our project consists of several .apk files installed into our devices, and we use MQDH to send adb scripts so we can launch them or return home, using the Local Network the hotspot device provides. The apps need to launch simultaneously or with minimal lag. However, MQDH requires a USB connection to turn on adb-over-wifi, and also if the connection is lost somehow, we need to re-establish it, not so reliable. How can we overcome this? We just need a local network with several Quest 2s and a computer/tablet/phone to launch apps wirelessly. I know there are some apps for that but they require us rooting the devices, which we do not want. Any help? Thanks.
