Inspiring

Solved

Your computer doesn't meet the updated minimum specifications, which can lead to a poor experience

19 replies
5999 views

Hello,

I have just purchased a Quest 3, and am attempting to get it running on my PC via the Meta Quest Link app. When I open the app it immediately tells me "Your computer doesn't meet the updated minimum specifications, which can lead to a poor experience in VR. Learn More".

If I follow the link to read about the minimum/recommended requirements I see that I definitely meet all the requirements, and my drivers are up to date. (although this shows the requirements for the Rift and Rift S, which I guess is a little out dated now?) Tried repairing the Quest Link App, restarting, all the automatically suggested solutions. It also gives me a really hard time connecting (either with the link cable or the airlink). Half the time it freezes on the loading screen, and 1/3rd of the time it opens in the Quest 3 then immediately disconnects.

i7-13700K, 32 GB DDR5 Ram, RTX 4070, 2 TB SSD, Windows 11 home, GeForce Game Ready Driver 576.52. MSI B760 Gaming plus wifi, with USB C 10 gbps, and 2 USB A 10 gbps ports.

Does this really not meet the minimum specifications? What is needed?

Thanks,

P

K

Kozo1Answer

Inspiring

Update:

For anyone with a similar problem, I found a solution that works for me. After following an EXHAUSTIVE list of things to try from Meta Support, it seemed there was definitely a problem with cable/connection stability. I purchased an INIU link cable (that goes to a USB A, but has a separate USB C plug for wall power).

Initially plugging it in didn't work and I had the same problem. BUT if I left the headset connected, ran services.msc (windows + R), selected right clicked on 'Oculus VR Runtime Service' and selected 'Restart' and then restarted my headset (while leaving it plugged in) by holding the power button and selecting "Restart" inside the headset.

Then When I tried to connect to my PC it worked. I haven't seen how stable it is over a long time - but I got farther than ever before with the official link cable (with which the same process doesn't do anything).

If I disconnect the headset and reconnect it without going through the same steps again, it doesn't work and gets stuck on 3 dots loading screen, or can't find my PC. It only appears to work with this cable, and if I follow those steps. And it seems vital to plug the headset in before powering it on (or leaving it plugged in and restarting it).

I won't accept this as a solution, because it is ridiculous to have to follow that procedure every time you want it to work. But it is certainly a step in the right direction, and also figuring out what the problem is.

Thanks to anyone that tried to offer solutions. And hello and goodbye if you read this far.

T

TomCgcmfc

Honored Contributor

Kozo1 Your specs def exceed minimum requirements and you should expect to get very good PCVR performance with link. It’s common to get these warnings and you should be able to ignore them. I initially even got those with my rtx4090, lol! Over time this warning message has gone away but after some updates it pops up.

You don’t say what link cable you’re using and what results you get from the meta link usb speed test (hopefully around 2.4Gbps). Also, what are your meta link graphics and Oculus Debug Tool settings. You should also include what windows version and what nvidia driver and control panel 3d settings.

The more information you can provide, the easier it is for users like myself to try to suggest things to try.

You can also contact meta support including your log files (google how to do this).

i9 13900K water cooled, RTX4090, Z790 MB w/wifi6e, 64Gb 6400 ram, 2x2TB SSD, 1000W PSU, Win 11, QPro, Q3, w/Link and Air Link, Vive Pro1 with 2x2.0 base stations, Etsy lens mod and Index Controllers

K

Kozo1Author

Inspiring

Thanks for the reply. Forgot to say, I was trying with 2 different cables. One was 10 gbps, but giving a speed of 3.2 gbps on the USB speed test (but was too short for me to use, unless I sat under my desk...). The other was was a faulty VR link cable, which has since been replaced. Windows 11. I don't know the Oculus debug tool settings yet, as I only just started to get it set u. NVIDIA driver is GeForce Game Ready Driver Version 576.52.

V

vikingfox

Up and Coming

Hi, here's a guess.

Your PC may use Hybrid Mode on the graphics card settings.

The Intel CPU has a built-in GPU, which may then run in desktop mode, which means that the software does not see the rtx4070 because it is not currently active.

Therefore, it may be necessary to change the setting of the PC so that the rtx4070 is always active and the GPU of the Intel CPU is not used.

K

Kozo1Author

Inspiring

Thanks! What's the best way to do this? I went to Settings -> System -> Display -> Graphics and added OcculusClient.exe as an app and set GPU preference to my NVIDIA card. But it still says does not meet minimum requirements. I couldn't figure out another way to make the NVIDIA card the default.

P

PeterPancho

New Participant

My IT guy just changed it in the BIOS. But I am still getting that message. I had a similar issue with Lumion Renderer with my previous laptop when it was brand new. The GPU was not active or something like that, therefore the software thought I was using a wood computer.

V

vikingfox

Up and Coming

It is different and are depends on the device. Some can be configured by software setting, device and some by bios setting.

Take a look here, found an how to with screens: Example for device manager and bios

https://www.elevenforum.com/t/enable-or-disable-integrated-graphics-igpu-in-windows-11.18616/

maybe this help in case it was that problem but let’s give it a try

K

Kozo1Author

Inspiring

OK, I'll try that out later today. Along with a third cable, and some other options I've read about.

V

vikingfox

Up and Coming

Good Luck, Feedback with the results would be great. Best regards Fox

K

Kozo1Author

Inspiring

Update: my computer does not show an integrated graphics card, only the RTX 4070 which is enabled. In Device manager there is also a Meta Virtual Monitor under display adapters, but I left that as it is. In the meantime I also disabled the option to “Allow the computer to turn off this device to save power” for all my usb sockets. And I reinstalled my GeForce driver, uninstalled, deleted everything oculus related, reinstalled the oculus link app, and factory reset my headset.

now, if I test it with a short 1 meter 40 gbps usb c cable I have (by sitting under the desk) it didn’t seem to falter. The problem is somewhat intermittent, I have had it last several minutes before freezing with the link cable (usually it is immediate or only a few seconds), so I cannot guarantee that is the difference with the freezing. Both cables get between 3 and 4.2 gbps on the usb connection test. I have ordered another (this will be my 3rd) link cable, this time the official meta one. I also have a 10 gbps usb c to a adapter, to test it in a different port. But when I use that, in another usb 3.2 port, the link app doesn’t recognise the cable at all.

hopefully the new cable will solve the problem, but it still says my computer doesn’t meet the requirements, which I can’t help but think that is connected to all of the problems I have been having with freezes and disconnects…

one thing I will say though, is that it is a beautiful world sometimes, where you can post problems on in a box on the internet, and strangers spend their time trying to help you! So I appreciate everything!

K

Kozo1Author

Inspiring

Update 2:
Official meta quest link cable also does not work. But it doesn't even let me get into the desktop. It freezes in the loading screen with 3 dots. But it doesn't do the weird thing around the boarders. After this, I went back to the other cable that had worked yesterday, and it is now doing the same thing as the meta quest link cable. I flipped ends and orientations of both cables, got it working for about 30 seconds in one orientation, but after it disconnected I couldn't get it to connect again. Occasionally, if it doesn't freeze during loading, it disconnects the moment my desktop becomes available (in the grey grid-like room area). I'm going to try a USB A to C cable, with a separate charging port to see if that makes a difference. But I need to order it. I'm almost ready to return this thing. Wasted nearly a week already and still made no progress.

V

vikingfox

Up and Coming

One thing: Your PC Ports are USB 3.0 or higher?

it has to be a USB 3 Port so I know.

Note: There are USB-A and USB-C Ports which just supports 2.0 (so check the PC Details that the ports are supported 3.0)

K

Kozo1Author

Inspiring

All are USB 3.2. One is USB C connector, 2 are usb A which I tried with adapter. The other 4 usb ports are 2.0, but those have my keyboard etc. I’ve tried it in all just to be sure. Also after unplugging every other usb device.

T

TomCgcmfc

Honored Contributor

Kozo1 wrote:

All are USB 3.2. One is USB C connector, 2 are usb A which I tried with adapter. The other 4 usb ports are 2.0, but those have my keyboard etc. I’ve tried it in all just to be sure. Also after unplugging every other usb device.

Have you actually contacted meta support and included your log files (google how to do this)??? If not, please stop wasting cyberspace. Really starting to look like a Reddit kiddie repost imho.

i9 13900K water cooled, RTX4090, Z790 MB w/wifi6e, 64Gb 6400 ram, 2x2TB SSD, 1000W PSU, Win 11, QPro, Q3, w/Link and Air Link, Vive Pro1 with 2x2.0 base stations, Etsy lens mod and Index Controllers

K

Kozo1Author

Inspiring

UPDATE:

Their support offered one suggestion which worked temporarily Try to install the latest Meta Quest drivers.

1. Close the Meta Quest Link app.
2. Press the Windows key + R on your keyboard to open the Run command.
3. Enter C:\Program Files\Oculus\Support\oculus-drivers. (File path may be different per user based on the install location)
4. Open oculus-driver.
5. Open the Meta Quest Link app and then try to connect your headset again.

After I did this, it ran successfully for about 20 minutes. Then I restarted my computer, reconnected the headset, and the old problem persisted. Stuck on a different loading screen, this time. I repeated the steps again, and this time when I started it, it connected, then immediately froze and glitched out around the edges. I was able to look around, but at the side of my original field of view was all distorted and glitchy (see second photo). So now I am back to square 1.

By the way, I replaced the headset - same problem.

K

Kozo1AuthorAnswer

Inspiring

Update:

For anyone with a similar problem, I found a solution that works for me. After following an EXHAUSTIVE list of things to try from Meta Support, it seemed there was definitely a problem with cable/connection stability. I purchased an INIU link cable (that goes to a USB A, but has a separate USB C plug for wall power).

Initially plugging it in didn't work and I had the same problem. BUT if I left the headset connected, ran services.msc (windows + R), selected right clicked on 'Oculus VR Runtime Service' and selected 'Restart' and then restarted my headset (while leaving it plugged in) by holding the power button and selecting "Restart" inside the headset.

Then When I tried to connect to my PC it worked. I haven't seen how stable it is over a long time - but I got farther than ever before with the official link cable (with which the same process doesn't do anything).

If I disconnect the headset and reconnect it without going through the same steps again, it doesn't work and gets stuck on 3 dots loading screen, or can't find my PC. It only appears to work with this cable, and if I follow those steps. And it seems vital to plug the headset in before powering it on (or leaving it plugged in and restarting it).

I won't accept this as a solution, because it is ridiculous to have to follow that procedure every time you want it to work. But it is certainly a step in the right direction, and also figuring out what the problem is.

Thanks to anyone that tried to offer solutions. And hello and goodbye if you read this far.

V

vikingfox

Up and Coming

Kozo1 Thanks for sharing your temp Workaround, i think this is realy helpful. Hope it will work over a longer time!

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO