Meta Quest 3 with Link Cable has very low FPS.
Hello, First of all, I am beyond excited to try this new technology that you guys have brought to life. It is truly an amazing experience, and I’m so glad I decided to buy it. I'm also a game developer, and recently, I wanted to try VR game development in Unity with my Quest 3 headset, which is where I’m running into a bit of trouble at the moment. My Wi-Fi connection is really poor, so I decided to buy a link cable. When I test the connection, it says I have a 2.4 Gbps speed, and everything seems fine. However, when I launch Oculus Link through my headset, the first 2-3 minutes of the experience are perfectly smooth without any FPS drops. But after those initial minutes, my FPS rapidly drops, making it unbearable. I tried reinstalling the Oculus app, but the problem persists, and I’d really appreciate your help in fixing this issue. I’m using an MSI GF63 Thin 11UC-617XTR laptop with 16 GB RAM, an Nvidia RTX 3050 4 GB, and an Intel® Core™ i5-11400H Processor. My friend has a laptop with an RTX 3050Ti and has successfully developed a VR game in Unity, but I can't seem to achieve the same results. To clarify what I mean by "low FPS": when I turn my head in Oculus Dreamdeck, the area I’m looking at appears dark at first, and then, after about half a second, the graphics load. Also, I can’t click on objects smoothly because aiming becomes difficult due to the low FPS. I’d greatly appreciate any help you can offer. I really adore this technology, and I want to be a part of it as it continues to grow. Thank you!1.7KViews0likes5CommentsUSB C Extension Cable used to work with v62, saw dust and debris issue in v63, doesn't work on v64
I have a long, expensive USB C 3.1 fiber optic cable that I need to use for development on the Quest. My desktop computer is located in a different room for cooling purposes so I have used a 50m fiber optic extension cable. It worked fine with v62 and below; however, with v63 the connection exhibited the 'dust and debris' issue and became unusable. Then v64 has come around and there is no more dust and debris messages but now the cable won't work. Of course, the next option are USB C 3.1 extenders over ethernet or fiber optic cable but they are $1-2k so really quite untenable. Is there some way to get this cable working, do you think? The Quest 3 does show up as a USB device connecting with SuperSpeed to Windows but Meta Quest Link (nor MDQH) won't see it and of course Quest Link won't begin. I am just a hobbyist dev though this has shut down much of my development opportunities. Is there a long cable you might recommend or even do you sell long cables that might work in my setup? Thanks for any help.786Views0likes0CommentsWorking in tethered mode?
Hey All, We're trying to develop a commercial application that will eventually run on PC (requires high-level graphics) and want to use a Meta Quest Pro as an HMD (using USB tethering). I'm seeing that the connection is possible but recommended in the docs for development only. Is it possible for production uses also? Also, when using the Quest Link software on my PC, the rendering is SUPER slow, and in Task Manager, the OVRServer takes ~60% of GPU. How can this be fixed? My specs are: - Intel Core i9-10885H CPU - 32GB RAM - NVidia RTX 2070 Max-Q GPU1.1KViews1like0CommentsWebXR issues with Link Cable using Quest 3 and RTX 4090 - Graphics Gods please save me
Hey I'm having performance issues with a WebXR app that I'm working on specifically when connected to Oculus Link and viewing the app with WebXR through PCVR. I expected my RTX 4090 would make it faster but I'm getting worse performance. I've tried profiling on mac pro, quest 3 standalone, and link cable (quest 3). Link cable is by far the slowest and I'm not sure why. My beefy GPU should make the scene render faster shouldn't it? For this particular webgl scene, the per frame gpu time is less than a ms on my mac pro when using the emulator and using the webxr emulator on my windows pc yields about the same. Once I plug in, the gpu time shoots up to 10-15ms. I've run the oculus profiler and it reported a min-max of (0,20ms) and an average of 9ms. This is a super small scene with only 60k vertices so I'm not sure what's going on. I ran profilers and verified that my CPU and GPU both have enough headroom. They're both <50% utilized. I don't see any abnormal Garbage Collecting in the chrome profiler. I've tried a bunch of other stuff I read on forums like disabling Hardware Accelerated Graphics Scheduling, uninstalling MSI afterburner, updating drivers, and a bunch more. I can't for the life of me figure out why my macbook and the quest 3 standalone would be outperforming the 4090. Any tips or advice would be appreciated! Happy to provide performance or log traces too.1.8KViews0likes1Comment