3D model of the room
I started developing for Quest3 but I'm stuck and not making much progress... So far, I've got pass-through working and added collision detection to the scanned room model. Next, I want to bring the scanned 3D model into a Unity scene so I can edit it, but I'm stuck because I don't know how to do it... Any ideas on how to make this work, or even a little advice, would really help.Shared Mode - storing app data across sessions
We’re working on integrating a new license system for our VR training app and were hoping to get insights on two related issues we’re facing — particularly in the context of Meta for Work (MHMS). Accessing MHMS Distributed Files We’d like to support large-scale deployments by allowing customers to deploy encrypted license files to headsets via Horizon managed services (there us an option there to deploy files to devices). File distribution itself works fine, but we haven’t found a way to read these files from within the app at runtime, i.e. to have the proper permissions to read those files. Do you have any guidance on how to access these files from the app? Storing License Info Locally We also want to store license data locally on the device after activation (while online, in the case were they do not want to distribute license files), so the app can validate the license even when the device is offline. This is essentially the same encrypted data as the distributed file, just generated online and then downloaded to the device. Is there a supported way to persist such data locally on MHMS-managed devices? We’re aware that local storage is very restricted across sessions, so we’d love to know if there is a way (now or with a future update). A work-around is keeping users in the same session, but that's not really ideal as users always will have the option to end a session. For now we will be requiring MHMS devices to be online, but that's not a solution viable on the long term where you will also see devices being used offline. MHMS itself now supports offline use. If there is a solution (so my first question and maybe to my second) this could also be used for trained led courses where the trainer sets the training options for a training session or even for the organization as a whole (think language and other regional options). Hopefully someone can provide some insights.249Views0likes8CommentsOrganization Groupings are going away as July 25th. What does it mean?
Hi. As Meta announced, Organization Groupings will be discontinued as of July 25th. What does it mean? We need to have a general matrix from which different organizations that will publish different games can branch off. How can we do this from now on? Thank you very much.23Views0likes0CommentsPing data overlay
Hi. Fairly new to development and I am stuck with a project. I am trying to develop a program that displays Network information to the user (ping, jitter, packet loss etc.) . I would like this to be able to run over any 3d application in real time Similar to how OVRMetric displays headset information. Any documentation or assistance would greatly be helpful.827Views0likes1CommentMRUK not found despite it being created...?
I'm currently using Quest 3 v62 (now v63) and Unity 2022.3.10f1. Working on a random spawn mechanic in the MR environment where objects can spawn on the ceiling. The feature worked fine when I tested it on Unity Playtest, but once I built it on the standalone Q3 (or simply hooked it up with a quest link), the scene could no longer be implemented. The room setup does indicate that I have my tables and walls, but there's no ceiling. I presume the Spatial data didn't transfer properly (I did write a script to grant permission to Q3 for spatial data, and clicked the Permission Requests On Startup) I have no idea where it all went south. Any ideas?1.7KViews0likes2CommentsFAIL_FORBIDDEN_PERMISSION Developer Hub error READ_PHONE_STATE Error
I have no other errors besides this one when I upload my build to the alpha production stage. The error says this: FAIL_FORBIDDEN_PERMISSION The upload could not be completed because your application contains the following Android permissions that are not supported: - android.permission.READ_PHONE_STATE Please remove the following permissions and upload your application binary again. The log says this: 2024-08-03T21:58:36.097Z [DEBUG] Run args: {"appId":"26165759013071717","apkPath":"C:\\Users\\rcper\\OneDrive\\Desktop\\Gorilla Flag First Version\\First Version.apk","channel":"ALPHA:quest2only|questproonly|quest3+","draft":true,"excludeAddons":false,"inheritAssetFiles":false,"isODH":true,"uploadFromEngine":false,"token":"(removed)","uploadConcurrency":null,"platform":"ANDROID_6DOF","disableProgressBar":true} 2024-08-03T21:58:36.367Z [DEBUG] Server log: {"app_id":"26165759013071717","client":"ODH","log_level":"DEBUG","event_name":"COMMAND_PARAMS","stack_trace":"at Object._log (C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js)\nat Object.debug (C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js)\nat C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js\nat processTicksAndRejections (node:internal/process/task_queues:96:5)","extra":"{\"appId\":\"26165759013071717\",\"apkPath\":\"C:\\\\Users\\\\rcper\\\\OneDrive\\\\Desktop\\\\Gorilla Flag First Version\\\\First Version.apk\",\"channel\":\"ALPHA:quest2only|questproonly|quest3+\",\"draft\":true,\"excludeAddons\":false,\"inheritAssetFiles\":false,\"isODH\":true,\"uploadFromEngine\":false,\"token\":\"(removed)\",\"uploadConcurrency\":null,\"platform\":\"ANDROID_6DOF\",\"disableProgressBar\":true,\"os\":\"{\\\"platform\\\":\\\"win32\\\",\\\"arch\\\":\\\"x64\\\",\\\"type\\\":\\\"Windows_NT\\\"}\",\"cli_version\":\"1.98.0.000001\",\"compatibility_version\":2,\"session_id\":\"26165759013071717_2024-08-03T21:58:36.095Z\",\"command\":\"upload-quest-build\",\"app_id\":\"26165759013071717\"}","platform":"ANDROID_6DOF","cli_version":"1.98.0.000001","session_id":"26165759013071717_2024-08-03T21:58:36.095Z","binary_id":"","duration":null,"is_patch_upload":0,"duration_since_session_start":271} 2024-08-03T21:58:37.552Z [WARN] 🟡 WARNINGS: • Quest 1 support is automatically disabled for apps created after 04/30/2024. Please refer to this post for more details: https://developer.oculus.com/blog/changes-coming-quest-1-2023-meta/ • 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 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. • This app contains both 32-bit (armeabi-v7a) and 64-bit (arm64-v8a) libraries. This consumes extra storage and increases download times. Consider updating your build to target 64-bit only. 2024-08-03T21:58:37.552Z [ERROR] Server log: {"app_id":"26165759013071717","client":"ODH","log_level":"ERROR","event_name":"UPLOAD_PREVALIDATION_FAILURE","stack_trace":"at Object._log (C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js)\nat Object.error (C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js)\nat C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js\nat processTicksAndRejections (node:internal/process/task_queues:96:5)","extra":"{\"errors\":[\"The upload could not be completed because your application contains the following Android permissions that are not supported:\\n - android.permission.READ_PHONE_STATE\\nPlease remove the following permissions and upload your application binary again.\"],\"warnings\":[\"Quest 1 support is automatically disabled for apps created after 04/30/2024. Please refer to this post for more details: https://developer.oculus.com/blog/changes-coming-quest-1-2023-meta/\",\"Your manifest includes the following permissions restricted by Oculus:\\n - android.permission.WRITE_EXTERNAL_STORAGE\\n - android.permission.READ_EXTERNAL_STORAGE\\n - android.permission.READ_MEDIA_AUDIO\\n - android.permission.READ_MEDIA_VIDEO\\n - android.permission.READ_MEDIA_IMAGES\\n - android.permission.ACCESS_MEDIA_LOCATION\\n - android.permission.READ_MEDIA_IMAGE\\nPlease 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.\",\"This app contains both 32-bit (armeabi-v7a) and 64-bit (arm64-v8a) libraries. This consumes extra storage and increases download times. Consider updating your build to target 64-bit only.\"],\"time\":549,\"os\":\"{\\\"platform\\\":\\\"win32\\\",\\\"arch\\\":\\\"x64\\\",\\\"type\\\":\\\"Windows_NT\\\"}\",\"cli_version\":\"1.98.0.000001\",\"compatibility_version\":2,\"session_id\":\"26165759013071717_2024-08-03T21:58:36.095Z\",\"command\":\"upload-quest-build\",\"app_id\":\"26165759013071717\",\"platform\":\"ANDROID_6DOF\"}","platform":"ANDROID_6DOF","cli_version":"1.98.0.000001","session_id":"26165759013071717_2024-08-03T21:58:36.095Z","binary_id":"","duration":549,"is_patch_upload":0,"duration_since_session_start":1456} 2024-08-03T21:58:37.793Z [ERROR] :cross_mark: ERROR: • The upload could not be completed because your application contains the following Android permissions that are not supported: - android.permission.READ_PHONE_STATE Please remove the following permissions and upload your application binary again. 2024-08-03T21:58:37.793Z [ERROR] Server log: {"app_id":"26165759013071717","client":"ODH","log_level":"ERROR","event_name":"USER_ERROR","stack_trace":"UserVisibleError: • The upload could not be completed because your application contains the following Android permissions that are not supported:\n - android.permission.READ_PHONE_STATE\nPlease remove the following permissions and upload your application binary again.\n at C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js\n at processTicksAndRejections (node:internal/process/task_queues:96:5)","extra":"{\"error\":\"• The upload could not be completed because your application contains the following Android permissions that are not supported:\\n - android.permission.READ_PHONE_STATE\\nPlease remove the following permissions and upload your application binary again.\",\"os\":\"{\\\"platform\\\":\\\"win32\\\",\\\"arch\\\":\\\"x64\\\",\\\"type\\\":\\\"Windows_NT\\\"}\",\"cli_version\":\"1.98.0.000001\",\"compatibility_version\":2,\"session_id\":\"26165759013071717_2024-08-03T21:58:36.095Z\",\"command\":\"upload-quest-build\",\"app_id\":\"26165759013071717\",\"platform\":\"ANDROID_6DOF\"}","platform":"ANDROID_6DOF","cli_version":"1.98.0.000001","session_id":"26165759013071717_2024-08-03T21:58:36.095Z","binary_id":"","duration":null,"is_patch_upload":0,"duration_since_session_start":1697} Thank you for your time.Solved5.9KViews0likes16CommentsMQDH can not keep sync alive for more than 3 seconds...
Hello!. I hope all you to be fine .. I'm experimenting some strange behaviour as follows: 1) I open MQDH and it recognizes my Quest 3, but keeps "Unauthorized" 2) I check my Quest 3 and there is no popup message... so, make some reboot here and there.. and then i got the popup again.. 3) I have allowed the connection. 4) MQDH enters debug mode for ADB, that's cool! ....3 seconds later... 5) MQDH returns with the message "Unauthorized" and exits the debug mode. Also it says in red: "Failed to refresh user on device X" My Specs: Windows 11 Ver. 10.0.22631.4317, 64-bits MQ3 built in package USB-C Cable . MQDH Version 5.1.0 MQ3 is with latest updates. I have enabled debug mode with Meta Horizon App from my Mobile. Any help will be very appreciated. Mikeh571Views0likes2CommentsVirtual 3D world anchored to real-world landmarks
## Introduction In an era where immersive technologies have struggled to gain widespread adoption, we believe there is a compelling opportunity to rethink how users engage with digital content and applications. By anchoring a virtual world to the physical environment and seamlessly integrating 2D and 3D experiences, we could create a platform that offers enhanced productivity, intuitive interactions, and a thriving ecosystem of content and experiences. We build upon our previous vision for an AR virtual world by introducing an additional key capability - virtual identity augmentation. This feature allows users to curate and project their digital personas within the shared virtual environment, unlocking new dimensions of social interaction, self-expression, and the blending of physical and virtual realms. ## Key Concepts The core of our proposal revolves around an AR virtual world that is tightly integrated with the physical world, yet maintains its own distinct digital landscape. This environment would be anchored to specific real-world landmarks, such as the Pyramids of Giza, using a combination of GPS, AR frameworks, beacons, and ultra-wideband (UWB) technologies to ensure consistent and precise spatial mapping. Within this virtual world, users would be able to interact with a variety of 2D and 3D elements, including application icons, virtual objects, and portals to immersive experiences. As we previously described, the key differentiator lies in how these interactions are handled for 2D versus 3D devices: 1. **2D Interactions**: When a user with a 2D device (e.g., smartphone, tablet) interacts with a virtual application icon or object, it would trigger an animated "genie out of a bottle" effect, summoning a 2D window or screen that is locked to a fixed position in the user's view. 2. **3D Interactions**: For users with 3D devices (e.g., AR glasses, VR headsets), interacting with a virtual application icon or object would also trigger the "genie out of a bottle" effect, but instead of a 2D window, it would summon a 3D portal or window that the user can physically move around and even enter. ## Virtual Identity Augmentation One of the key new features we are proposing for the AR virtual world is the ability for users to place virtual objects, like hats, accessories, or digital avatars, on themselves. These virtual objects would be anchored to the user's position and movements, creating the illusion of the item being physically present. The critical distinction is that 2D users (e.g., on smartphones, tablets) would be able to see the virtual objects worn by other users in the shared virtual world, but they would not be able to place virtual objects on themselves. This capability would be reserved for 3D device users, who can leverage the spatial awareness and interaction capabilities required for virtual object placement. These virtual objects placed on a user would persist across devices and sessions, creating a consistent virtual identity or "avatar" for that user within the AR virtual world. This virtual identity would be visible to all other users, regardless of their device capabilities (2D or 3D). Importantly, the virtual objects used to create this virtual identity could also be leveraged to partially or completely obscure a user's real-world appearance from 2D video, photo, and 3D scanning. This would allow users to control how they are represented and perceived in the blended physical-virtual environment, providing greater privacy and security. ## Enhanced 2D Interfaces for 3D Users Building on our previous concept, we can further enhance the user experience for 2D applications, particularly for 3D users. By leveraging the depth and spatial characteristics of the 3D interface blocks, we can unlock new ways for users to interact with and manage their virtual applications and content. Some of the key capabilities include: 1. **Contextual Controls and Information Panels**: The sides of the 3D interface blocks could display shortcut controls, supplementary information panels, and other contextual elements that 3D users can access and interact with as they navigate around the application window. 2. **Dynamic Layouts and Customization**: 3D users would be able to resize, rotate, and reposition the side panels and controls, enabling personalized layouts and ergonomic arrangements tailored to their preferences and workflows. 3. **Multi-Dimensional Interactions**: The 3D interface blocks could support advanced interaction methods beyond basic clicking and scrolling, such as gestures (grabbing, pinching, swiping) and voice commands to interact with the contextual controls and information. 4. **Seamless Transition between 2D and 3D**: Despite these enhanced capabilities for 3D users, the 2D application windows would still function as regular 2D interfaces for users without 3D devices, maintaining a seamless collaborative experience across different device types. ## Potential Benefits and Use Cases The enhanced AR virtual world concept we propose offers several potential benefits and use cases: 1. **Increased Productivity and Ergonomics**: By providing 3D users with enhanced controls, contextual information, and customizable layouts, we can improve their efficiency and ergonomics when working with 2D applications. 2. **Intuitive Spatial Interactions**: The ability to physically move and interact with 3D portals and windows, as well as the option to place virtual objects on oneself, can lead to more natural and immersive ways of engaging with digital content and applications. 3. **Virtual Identity and Self-Expression**: The virtual identity augmentation system allows users to curate and project their digital personas, enabling new forms of social interaction, status signaling, and even monetization opportunities. 4. **Privacy and Security**: The option to obscure one's real-world appearance through virtual identity augmentation can provide users with greater control over their digital privacy, especially in public spaces. 5. **Collaborative Experiences**: The seamless integration of 2D and 3D interactions within the same virtual environment can enable users with different device capabilities to collaborate on tasks and projects. 6. **Extensibility and Customization**: Providing tools and APIs for developers to integrate their own applications and content into the virtual world can foster a thriving ecosystem of experiences. 7. **Anchored to the Real World**: Tying the virtual world to specific real-world landmarks can create a sense of spatial awareness and grounding, making the experience feel more meaningful and connected to the user's physical environment. Robotics Safety Integration Real-time visualization of robot operational boundaries Dynamic safety zone mapping visible to all platform users Automated alerts for boundary violations Integration with existing robotics control systems Unified space mapping for multi-robot environments Environmental Monitoring Visualization of invisible environmental factors Air pollution particle mapping CO2 concentration levels Temperature gradients Electromagnetic fields Real-time data integration from environmental sensors Historical data visualization for trend analysis Alert systems for dangerous condition levels Construction and Infrastructure Real-time 3D blueprint visualization Infrastructure mapping Electrical wiring paths Plumbing systems HVAC ducts Network cables Safety feature highlighting for drilling and renovation Progress tracking and documentation Client visualization tools for project understanding Augmented safety checks and compliance monitoring Inventory and Asset Management AI-powered real-time inventory tracking Integration with camera-based stock management systems 3D spatial mapping of warehouse spaces Automated photogrammetry for stock visualization Real-time update of virtual inventory models Cross-reference with ordering systems Predictive analytics for stock management ## Conclusion By combining the core concepts of an AR virtual world with the added capability of virtual identity augmentation, we believe we can create a compelling platform that addresses the shortcomings of past immersive technology efforts. This vision not only offers enhanced productivity, intuitive interactions, and a thriving ecosystem, but also unlocks new dimensions of social interaction, self-expression, and the blending of physical and virtual realms. Creating a shift toward a 3D society, by including 2D phones. Leading to a new 3D app store. We invite you to explore this concept further and consider its potential impact on the future of computing and human-computer interaction. Together, we can shape a new era of spatial computing that bridges the gap between the physical and digital worlds.