Render to only one eye
Hello, I'm after a bit of information about who I should try contacting regarding making VR less GPU wasteful for my particular situation. I'm blind in my right eye so I was hoping that there could be a driver level option maybe that would allow users to say "hey, as much as I'd love 2 working eyes, it would be real nice if I can just render a black image to the right eye and benefit from better FPS in the left". I get that stereoscopic is better, given the choice, but for me it's not a choice I have so I may as well benefit from improved frame rates or better image quality. I was born blind in one eye so I've had plenty of time getting used to lack of depth perception, however, I can still take visual cues from surrounding environment on a virtual race track to know when to out brake you :wink: Back on track though (pun intended), would it be a driver level (pun unintended) development, or maybe SteamVR? Something where we do not have to rely on every game studio to provide it as an option, instead we can just set it and forget it at lower level. I have a degree in games programming, so I'd be happy to get my fingers dirty if I was pointed in the right direction, if Oculus isn't prepared to implement something like this. Thanks in advance, Kevin
Black grid on camera frame when displaying point cloud
I am developing an application that receives and display a point cloud. When I try to render a point cloud (both with normal mesh or MaterialPropertyBlock and GPU) I get what it seems to be a black transparent canvas that follows my head. This is very annoying. I tried to change materials and shaders, to disable shadows, but I didn't find a way to get rid of this problem.Full Screen Pass Renderer Feature Not Working on Build
Hello, I'm trying to implement an Outline Post Processing shader. I've found a simple graph shader that uses "full screen pass renderer feature" and the video is here. In the project I'm utilizing Meta's All-in-One SDK with passthrough and Meta's Depth API. Everything seems to work fine in Scene and Game mode with link. However, when I build the project the objects shift around and go undesired places while disabling the passthrough. I figured that the outlines seem to be in the correct location but the rendering of the red cube is moving around. I have been trying to debug it but could not find the reason causing this issue. I am not sure if these screenshots would help but here there are anyways.
Standalone Vulkan in headset not working correctly - Huge Flickering, Incorrect frames
Hello, I'm working on a game with The Mirror (https://www.themirror.space/) , we've spoken to support at Godot Engine and they have mentioned that the Quest 3 has a Vulkan issue where the headset flickers intensely. We are experiencing this issue but only on the meta quest 3, on Mac, Windows, Linux and the quest 2 we don't have the same rendering problem. I have made a video of the issue please see the video https://www.youtube.com/watch?v=gd4NBKl0Gro The team at Godot Engine have tried to resolve this problem before for quite a lot of users but haven't been able to locate the source of the issue apart from it seems to be driver related for the adreno 740 in the meta quest 3. I am not a driver/rendering expert and would appreciate any help with this issue. The API is using Vulkan 1.0 and Vulkan 1.1, it has Vulkan 1.2 available too. I can provide full source code. Thanks, Gordon MacPhersonMake all materials in all samples URP
Dear Meta staff, can we please make ALL materials URP in all samples for Unity? I don't know any person using Built-In Renderer Pipeline in their Quest projects anyways.... I think this will give a lot of value to the samples offered by Meta, without having to duplicate materials and re assign them cus the URP converter can't change some stuff in the packages folders..... Thanks!
Issues with APK Build Rendering and Body Tracking on Quest 3 in Unity
Hello everyone, I'm currently working on a project in Unity for the Meta Quest 3, and I'm facing several challenges that I hope some of you might be able to help me address. Rendering Issues in APK Build: When I run my scene directly from Unity on my PC connected to the Quest 3 via Link, everything renders correctly. However, when I create an APK and run it on the Quest 3, certain elements like water and body models do not render properly. It seems as though the body model is not visible and the water in the scene does not display at all. Body Tracking: Alongside rendering issues, the body tracking does not function as expected in the APK build. When connected to the PC, the body tracking works fine, but this functionality breaks down in the standalone APK. Configuration Details: Unity Version: Unity 2021.3.26f1 XR Plugin Management settings are configured for Oculus. I've tried various settings for Android texture compression and multi-view rendering. My scene includes body tracking and uses the OVR plugins. I've attached the settings I'm using for Android build and XR plugin management for reference. Has anyone else encountered similar issues or can offer any insights into what might be going wrong? Any suggestions on how to ensure the APK build maintains fidelity with the editor preview would be incredibly helpful. https://youtube.com/shorts/BzQq_aj-mfo Thank you in advance for your help!Designated Photogrammetry App?
When you open up a mixed reality app on the Quest 3, it has you take a scan of your space so the game knows where to place things in the 'real world'. When I saw this happening for the first time I was mesmerized. The room I was in was very quickly translated to untextured polygons and only got more accurate the more I looked around things, for example, my fan went from a large cylinder, to an extremely accurate render of my fan as I went above and around it. I would love to see if the Quest 3 could even house a photogrammetry app, seeing as the depth sensors could make seriously accurate models in real time. If It did exist, I personally wouldn't change a thing about the model rendering portion of it, but to add a texture mapping second part would also be so cool. This is just an idea as I have no idea how to code, but I'm not above starting if someone could point me in the right direction because well, I have no idea where I'd start with making software for the Quest 3.
