Forum Widgets
Recent Discussions
Browser Extension 4 Xbox Controller?
Hi all, wouldn't it be nice to use a controller within the (IMHO) already great browser? So we can use JS content with it? Like, the "Internet Arcade"... Shouldn't Meta add a chrome add-on like "Gamepad to Keyboard Mapper" to its chromium browser? Or is there a workaraound to archieve this? Cheers, ChristianEl_Loote6 months agoHonored Guest38Views0likes0Comments
Scale issue of 360 panoramic images within VR view
Hi all, I've been working on designing a simple web app for 360 virtual tours using 360 images. The images were taken by an Insta 360 X4 camera. I designed the scripts using Threejs and React Three Fiber components to view these 360 panoramas and added simple hotspots for navigation purposes. The images are embedded as textures to the inside of a large sphere. However, when I viewed the images through my Meta Quest 3 headset, the scenes seem to be quite larger than their real-world scale. Is there any way to reduce this scale into a realistic value?hash_rx6 months agoHonored Guest69Views0likes0CommentsWhat are the best practices for designing an engaging and user-friendly social media feed?
I'm working on a social media app and want to create a feed that keeps users engaged without overwhelming them. What design principles or features have you found effective for making feeds both intuitive and addictive? How do you balance content variety and relevance? Do you use algorithms or manual curation? How do you handle ads or sponsored content without disrupting the experience? Any UI/UX tips or examples that worked well? Would love to hear your insights!jameswood327 months agoProtege52Views0likes0Comments
Browser shortcuts in Library (25/02/18)... 4 months later
As a WebXR developer you can imagine how delighted I was that the facility to add browser shortcuts was added to Meta Quest in v74 back in February... ... As a WebXR developer you can imagine how frustrated I am that this feature has still not materialised on my headset despite now being on v78 some four months later. There must be some actual way of determining what is wrong with updates on my headset or method for unblocking my headset/feature on the rollout schedule being disappointed every time I switch on my headset is wearing thin. And wishful thinking every time I reboot is getting annoying.michael.dowman9 months agoHonored Guest153Views0likes0Comments
Any info on new initial support for passthrough camera on Meta browser v38.2?
Is there any API info, documentation, or code samples regarding access to the passthrough camera api in WebXR as per the Meta Browser 38.2 Release notes? I am assuming this is to allow access the the front facing cameras as a texture available to use in AI models or for other purposes using the passthrough camera api (not as a background like traditional AR, but allowing javascript access to the actual data from the camera stream, which would be new to Quest WebXR and very powerful!) Browser 38.2 The 38.2 release contains the following: Experimental features (not available to all users): Passthrough Camera: Added initial support for passthrough camerapanoram.io9 months agoHonored Guest147Views0likes0Comments- Mizi789510 months agoHonored Guest179Views0likes0Comments
/conversations endpoint returns 500 (code 2, is_transient) — but only for one Page
Hi everyone, We are running into a puzzling issue with the Graph API and hoped someone here has seen it before. GET /v22.0/{PAGE_ID}/conversations ?platform=MESSENGER Error we get only for ONE page: HTTP 500 { "error": { "message": "An unexpected error has occurred. Please retry your request later.", "type": "OAuthException", "is_transient": true, "code": 2, "fbtrace_id": "AIv25knnUDxlaRvUCqr4LfP" } } The same call succeeds for all other Pages we manage. Fails 100 % of the time for this one Page, for > 36 h now.brashka11 months agoHonored Guest334Views0likes0Comments
Promotions are restricted
Hello, Created a business Instagram account. Right away my account's promotions were restricted. Stating "the account was created or used with an automation that doesn't follow our rules." Unsure what this means. Tried to send an appeal, but the page freezes. Currently have 128 days remaining and am lost. Seeking guidance. Thank youbut.first.doughnuts11 months agoHonored Guest197Views0likes0Comments
Memory leaking from headset sleep in WebXR sessions & fastrpc_shell_3 crashing
I've been troubleshooting performance issues in Quest3 with webXR. In doing so I have found that I'm getting consistent memory leaking whenever an XR session is running and the headset goes to sleep. It seems that when the headset sleeps about 100mb of free memory is lost each time and is not recoverable without a full reboot of the headset. In addition to this memory leak I also see pretty consistent crashing of "fastrpc_shell_3" which seems related to body tracking. I get this crash happening every time the headset is removed regardless of if I'm in an XR session. Eventually these issues seem to destabilize the system leading to other systems crashing and often a full system crash/reboot. Sometimes even after the system reboots all services do not appear to have been successfully restarted. I have captured some more detailed system logs around some of these issues using Logcat which I would be happy to share. I'm looking to better understand what and why these things are happening and how to best mitigate them. Any help is appreciated 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: ############################### Process on cDSP0 CRASHED!!!!!!! ######################################## 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: --------------------- Crash Details are furnished below ------------------------------------ 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: Process "/frpc/f04134a0 HexagonThread" crashed in thread "fr/6757/6842" due to TLBMISS X (execution) 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: Crashed Shared Object "fastrpc_shell_3" load address : 0x81F00000 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: fastrpc_shell_3 load address : 81F00000 and size : 130578 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: Fault PC : 0x82524E50 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: LR : 0x82524E50 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: SP : 0x4AC7C50 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: Bad VA : 0xC4F46C1 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: FP : 0x4AC7C68 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: SSR : 0x1E70660 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: Error code : 0x600A 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: Call trace : 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: [<82524E50>] __eh_nodes+0x4BCE4C: (_rtld_anonymous) 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: [<82524E50>] __eh_nodes+0x4BCE4C: (fastrpc_shell_3) 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: [<82523E24>] __eh_nodes+0x4BBE20: (fastrpc_shell_3) 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: [<81FA2AC0>] __cxa_finalize+0x60: (fastrpc_shell_3) 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: [<825B3B94>] __eh_nodes+0x54BB90: (fastrpc_shell_3) 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: [<81F6C31C>] u2g_client_close+0x2D2C: (fastrpc_shell_3) 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: [<81F6C050>] u2g_client_close+0x2A60: (fastrpc_shell_3) 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: [<81F6C5E8>] dlclose+0x24: (fastrpc_shell_3) 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: [<81F63510>] remote_handle_close+0x3F48: (fastrpc_shell_3) 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: [<81F6BACC>] u2g_client_close+0x24DC: (fastrpc_shell_3) 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: [<81F62E38>] remote_handle_close+0x3870: (fastrpc_shell_3) 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: [<81F4F7D0>] err_Fatal_internal0+0x923C: (fastrpc_shell_3) 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: [<81F58170>] err_Fatal_internal0+0x11BDC: (fastrpc_shell_3) 04-08 12:47:25.154 795 842 V adsprpc : 6b0b:b87: CDSP0: ----------------------------- End of Crash Report --------------------------------------------------htroutmaniv1 year agoHonored Guest437Views2likes0Comments
Difficultés de prévisualisation des partages de liens en contexte Client-Side Rendering
Bonjour à tous Je me permets de vous contacter en tant que développeur web travaillant sur des applications modernes utilisant des frameworks comme React, Vue ou Angular avec TypeScript (Débutant). Nous rencontrons une difficulté persistante concernant la génération des aperçus de partage sur les plateformes – notamment Facebook, Instagram, Twitter ou LinkedIn – lorsque les URLs concernées pointent vers des pages générées côté client (Client-Side Rendering - CSR). Dans ces architectures modernes, le contenu – y compris les balises meta essentielles aux cartes de partage (og:title, og:description, og:image, twitter:card, etc.) – est injecté dynamiquement dans le DOM après le chargement initial du HTML, souvent à l'aide de bibliothèques comme react-helmet-async. Cependant, nous observons que vos crawlers (facebookexternalhit, Twitterbot, LinkedInBot...) se basent uniquement sur le HTML initial livré par le serveur. Ils ne semblent pas exécuter JavaScript ni attendre l’hydratation et la résolution des données nécessaires à l’injection correcte des balises meta. Résultat : des aperçus vides, incorrects ou génériques. Nous comprenons bien sûr les défis techniques que représente l’exécution complète du JavaScript sur chaque page analysée (temps de rendu, charge serveur, fiabilité). C’est pourquoi de nombreuses équipes, comme la nôtre, mettent en place des solutions comme le SSR, le SSG ou le prerendering pour répondre à ces contraintes. Cela dit, la dynamique du web évolue rapidement, et les solutions 100 % CSR avec récupération de contenu via API restent très répandues. Dans ce contexte, nous aimerions savoir : Existe-t-il des plans ou des discussions en cours au sein de vos équipes pour améliorer la capacité de vos bots à analyser le rendu JavaScript ? Un mécanisme (entête HTTP, paramètre URL, balise meta spéciale...) pourrait-il à l’avenir signaler aux crawlers qu’une attente ou une exécution partielle de JavaScript serait pertinente pour obtenir un contenu plus riche ? Avez-vous des recommandations officielles pour les architectures CSR souhaitant assurer une bonne compatibilité avec vos aperçus sociaux ? Nous sommes nombreux dans la communauté à nous heurter à ces limites, et toute avancée sur ce sujet aurait un impact concret sur l'expérience utilisateur et la qualité des partages. Merci pour le travail que vous accomplissez, et pour l’attention portée à ce retour du terrain. Cordialement, Oredy MUSANDA Développeur web (Débutant) www.oredytech.com (N.B: Ce message a été corrigé par l'intelligence artificielle pour gagner du temps)OredyMusanda1 year agoHonored Guest200Views0likes0Comments
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device