Explorting 3d Scans made on the Quest 3
It would be really cool to be able to export the models and textures made while 3d scanning environments using the quest 3. This would allow us to import the scans into a 3d modelling program like blender, to be able to set them up for use in another VR game or experience. In a way it would be helping expand the content available in the metaverse by allowing users to get creative, even if the 3d model isn't particularly high detail, users could add in missing detail via a 3d modelling program. We could also add extra detail by modifying the textures, normal maps, height maps ect. I would love to be able to make a map out of my gaming room for use in a social VR game! People used to make maps in CounterStrike years ago called RAT maps, where they would model an environment where the player was tiny playing in a massive ( to them). Having this feature available would make is much more accessible to create fun content like that. Progress is good ^_^, and the less limitations we have for contributing to the content available the better! Unlock peoples creativity ^_^
Orion - AR - Driving - Eye tracking - Glare
Feature Request: A big problem with driving especially during sunrise, sunset and night driving is the driver being blinded by harsh incoming lights. These can be distracting or dangerous. The Orion prototype is well positioned with its external cameras and eye tracking to measure environmental glare and generate pixels to block some of the incoming light. Imagine being able to put on a pair of Orion glasses prior to driving a car on winding, two-lane roads at night time. Other drivers intermittently strain your night vision as you are looking for animals along the side of the road. With this feature in place, the Orion glasses could significantly dampen the incoming light allowing you to maintain your concentration on the road. Similarly, I believe there is a large opportunity providing context-dependent, information on demand. This could be a heads up display of maps while driving to searching for similar parts in a mechanics workshop or even providing interactive training where surgeons could be remotely assisted.
Disabling App Sharing?
I am a developer for a multiplayer game, we are currently facing a problem where users are abusing app sharing to get around meta account ID bans. Is there a way, for us, as developers to disable the ability to app share our game? If not, is there a way we can get the account ID of who originally owns the game?
[Feature Request] Camera and Depth raw data access through USB ADB connection
I know there have been plenty of other posts requesting access to the camera feeds from the Quest devices, and I understand the privacy and potential PR issues that might arise from giving apps access to the raw feeds from the cameras. I know Passthrough Over Link exists, but it's not the original data. What I don't understand, however, is why the raw data isn't accessible through a wired ADB connection... Wouldn't it be possible to enable access to the raw data of each camera and the depth sensor through a wired ADB connection, without exposing it to apps running on the device? Akin to what is done for screen capture as described in https://creator.oculus.com/create-build/capturing-video-from-a-quest-headset/ I'm interested in using the data for my university research, but the lack of access to it is rather disappointing.How to start Eye Tracking Calibration from an Application or ADB
Is it possible to start the Quest Pro eye tracking calibration flow (the one in Settings -> Movement -> Eye Tracking) in either of these ways?: Within an application (whether it is an OpenXR call, android intent, or Unity plugin) Through ADB (intent, executable; can use root permissions) If this is not possible, then I'd like to make this a feature request, as it would greatly improve our user experience 🙂Allow predefined HTML attribute in <video> tag to define video as 2D / 3D and 180VR /360VR
I have a small website with VR Videos that are exclusively for Oculus devices. The video-clips are emmbedded with video-Tag. HTML Code: <video controls> <source src="video.mp4" type="video/mp4"> </video> Everytime the user has to select manually the following parameter. 3D-Side by Side, 180°VR or 360°VR. It would be awesome, if Meta can introduce a custom html attribite to video tag to preselect. Eg. HTML Code: <video controls> <source vrangle="180" vrmode="3DSide" src="video.mp4" type="video/mp4"> </video> Or with better naming 🙂 Thank you.
Numeric Virtual Keyboard does not have period button : Meta Quest OS Software
The numeric virtual keyboard from the Meta Quest OS software does not have a period so it is impossible to input textual decimal values with this numeric focused keyboard. Can a period button be added to this keyboard please?
Authentication using OAuth on Quest - supported flows using browser, QR or companion app?
We have an existing enterprise app that we are porting to Quest. The app is built using Unity and an OAuth service (Azure B2C) is used for authentication. Currently, we support multiple authentication flows, including using browser based authentication and reading QR codes using the built in camera on devices where typing is inconvenient, such as Microsoft HoloLens. I'm trying to find the recommended path for secure authentication for Oculus Quest. Thing's I've tried: browser authentication does not work since the Oculus browser does not appear to allow intent-filters to open applications as per Android default behaviour, see https://forums.oculusvr.com/developer/discussion/89646/feature-request-allow-appps-to-be-launched-via-intent-filters-from-oculus-browser#latest QR authentication does not work, since no QR reading framework is available on the device like it is on other platforms (HoloLens 2 and even Windows Mixed Reality headsets), and since the cameras are not directly accessible to developers either. Quest does seem to have some provisioning for authentication through it's own companion app, but I can find no mention that we can develop our own 3rd party companion app to handle authentication this way? I'm sure there are many other developers looking to authenticate their Quest users through OAuth; how did you manage this?