cancel
Showing results for 
Search instead for 
Did you mean: 

What aspect of my Surface Book 3 RTX 3000 GPU does the Oculus app not like?

Here's the info from perfLog:

 

"computer_type": "laptop",
"hardware": {
"Version": "1.0.0 (Custom Build)",
"Timestamp": 1687819850,
"Timestamp_str": "Mon Jun 26 16:50:50 2023 Mountain Daylight Time",
"OverallResult": 2,
"OverallResult_str": "FAIL",
"CpuList": [
{
"Name": "Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz",
"Manufacturer": "GenuineIntel",
"Level": 6,
"Model": 126,
"Stepping": 5,
"NumberOfCores": 4,
"NumberOfLogicalProcessors": 8,
"MaxFrequencyMhz": 1498,
"Compatibility": 3,
"Compatibility_str": "UNKNOWN",
"CompatibilityReason": 4,
"CompatibilityReason_str": "UNKNOWN"
}
],
"MatchedCpu": {
"Name": "Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz",
"Manufacturer": "GenuineIntel",
"Level": 6,
"Model": 126,
"Stepping": 5,
"NumberOfCores": 4,
"NumberOfLogicalProcessors": 8,
"MaxFrequencyMhz": 1498,
"Compatibility": 3,
"Compatibility_str": "UNKNOWN",
"CompatibilityReason": 4,
"CompatibilityReason_str": "UNKNOWN"
},
"CpuResult": 3,
"CpuResult_str": "UNKNOWN",
"CpuHelpUrl": "https://ocul.us/RiftSpecs",
"VideoCardList": [
{
"Name": "NVIDIA Quadro RTX 3000 Mobile",
"WhitelistName": "NVIDIA Quadro RTX 3000",
"DriverVersion": "31.0.15.2824",
"LUID": "0x000000000001554a",
"VendorId": 4318,
"ProductId": 7990,
"SubsysVendorId": 0,
"SubsysRevId": 161,
"VRamMb": 6144,
"HybridGraphicsStatus": "NoOutput",
"Compatibility": 2,
"Compatibility_str": "FAIL",
"IsDriverCompatible": true,
"PassHybridCheck": false,
"VulkanCapable": true,
"total_DVI_port_count": 0,
"total_HDMI_port_count": 0,
"total_generic_DisplayPort_port_count": 0,
"total_internal_DisplayPort_port_count": 0,
"total_external_DisplayPort_port_count": 0,
"total_external_mini_DisplayPort_port_count": 0,
"active_DVI_port_count": 0,
"active_HDMI_port_count": 0,
"active_generic_DisplayPort_port_count": 0,
"active_internal_DisplayPort_port_count": 0,
"active_external_DisplayPort_port_count": 0,
"active_external_mini_DisplayPort_port_count": 0
},
{
"Name": "Intel(R) Iris(R) Plus",
"WhitelistName": "Intel(R) Iris(R) Plus Graphics",
"DriverVersion": "30.0.101.3118",
"LUID": "0x000000000001525a",
"VendorId": 32902,
"ProductId": 35410,
"SubsysVendorId": 0,
"SubsysRevId": 7,
"VRamMb": 128,
"HybridGraphicsStatus": "Success",
"Compatibility": 2,
"Compatibility_str": "FAIL",
"IsDriverCompatible": false,
"PassHybridCheck": true,
"VulkanCapable": false,
"total_DVI_port_count": 0,
"total_HDMI_port_count": 0,
"total_generic_DisplayPort_port_count": 0,
"total_internal_DisplayPort_port_count": 0,
"total_external_DisplayPort_port_count": 0,
"total_external_mini_DisplayPort_port_count": 0,
"active_DVI_port_count": 0,
"active_HDMI_port_count": 0,
"active_generic_DisplayPort_port_count": 0,
"active_internal_DisplayPort_port_count": 0,
"active_external_DisplayPort_port_count": 0,
"active_external_mini_DisplayPort_port_count": 0
}
],
"MatchedVideoCard": {
"Name": "NVIDIA Quadro RTX 3000 Mobile",
"WhitelistName": "NVIDIA Quadro RTX 3000",
"DriverVersion": "31.0.15.2824",
"LUID": "0x000000000001554a",
"VendorId": 4318,
"ProductId": 7990,
"SubsysVendorId": 0,
"SubsysRevId": 161,
"VRamMb": 6144,
"HybridGraphicsStatus": "NoOutput",
"Compatibility": 2,
"Compatibility_str": "FAIL",
"IsDriverCompatible": true,
"PassHybridCheck": false,
"VulkanCapable": true,
"total_DVI_port_count": 0,
"total_HDMI_port_count": 0,
"total_generic_DisplayPort_port_count": 0,
"total_internal_DisplayPort_port_count": 0,
"total_external_DisplayPort_port_count": 0,
"total_external_mini_DisplayPort_port_count": 0,
"active_DVI_port_count": 0,
"active_HDMI_port_count": 0,
"active_generic_DisplayPort_port_count": 0,
"active_internal_DisplayPort_port_count": 0,
"active_external_DisplayPort_port_count": 0,
"active_external_mini_DisplayPort_port_count": 0
},
"VideoCardResult": 2,
"VideoCardResult_str": "FAIL",
"VideoCardHelpUrl": "https://ocul.us/RiftSpecs",
"RamMb": 32353,
"RamResult": 0,
"RamResult_str": "PASS",
"RamHelpUrl": "",

 

Now, the Compatability.json VideoCardWhiteList shows

{
"Name": "NVIDIA Quadro RTX 3000",
"Vendor": "NVIDIA",
"PID": "1F36",
"SubsysVID": "Any"
},

 

So, the GPU itself is in the whitelist. However, the MatchedVideoCard says

 

"MatchedVideoCard": {
"Name": "NVIDIA Quadro RTX 3000 Mobile",
"WhitelistName": "NVIDIA Quadro RTX 3000",
"DriverVersion": "31.0.15.2824",
"LUID": "0x000000000001554a",
"VendorId": 4318,
"ProductId": 7990,
"SubsysVendorId": 0,
"SubsysRevId": 161,
"VRamMb": 6144,
"HybridGraphicsStatus": "NoOutput",
"Compatibility": 2,
"Compatibility_str": "FAIL",
"IsDriverCompatible": true,
"PassHybridCheck": false,
"VulkanCapable": true,
"total_DVI_port_count": 0,
"total_HDMI_port_count": 0,
"total_generic_DisplayPort_port_count": 0,
"total_internal_DisplayPort_port_count": 0,
"total_external_DisplayPort_port_count": 0,
"total_external_mini_DisplayPort_port_count": 0,
"active_DVI_port_count": 0,
"active_HDMI_port_count": 0,
"active_generic_DisplayPort_port_count": 0,
"active_internal_DisplayPort_port_count": 0,
"active_external_DisplayPort_port_count": 0,
"active_external_mini_DisplayPort_port_count": 0
},
"VideoCardResult": 2,
"VideoCardResult_str": "FAIL",

 

 

Can anyone explain what attribute of this GPU is causing the Oculus app to fail? I don't actually want to drive a wired Oculus headset, I'm trying to drive a Quest 2 / Quest Pro via wired or wireless link. But I have to have the desktop app running in order to link them.

 

I suspect the app is mistakenly upset that I don't have an HDMI connector or something that the normal Rift headset would plug into, but I'm not going to be USING an HDMI connector, so it shouldn't care.

 

I do have external monitors connected via DisplayPort through a Microsoft Surface dock but I don't think that matters.

1 ACCEPTED SOLUTION

Accepted Solutions

Hi there, @XenonofArcticus42. We appreciate that you're desiring to bring your Quest 2/Pro on the road with a mobile setup. However, your Quadro GPU is not supported; we require a GeForce GPU. And while the Oculus PC App definitely works with VR-ready laptops, they must be plugged in to a power source to allow the app to run properly, and battery-only function is not guaranteed.

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!

View solution in original post

8 REPLIES 8

MetaQuestSupport
Community Manager
Community Manager

Hey there, @XenonofArcticus42. We definitely understand how concerning it is to run into PC VR issues like this, and we'd be glad to look into it for you. After looking into the GPU that you have, it doesn't appear to be compatible with our devices. Seeing as that's the case we wouldn't be able to provide accurate support or guarantee any fixes. We understand this isn't the response you had hoped for, and we appreciate your understanding. We hope you enjoy the rest of your week! 

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!

Hey guys, your reply is pretty low effort and added no new information to this conversation. I'm already aware that Oculus Desktop considers this hardware incompatible.

However, since it seems to meet the published specifications, and the GPU is specifically identified as on the whitelist, I'm asking for further information about WHY the Oculus software believes it is incompatible.

 

You see, if we buy hardware based on the assumption that it will be suitable, and then despite the specifications being adequate, it refuses to work, it's a bit frustrating. 

 

In the future, how do we avert this? We need a mobile PC capable of driving a Quest 2 or Quest Pro HMD. 

Hi there, @XenonofArcticus42. We appreciate that you're desiring to bring your Quest 2/Pro on the road with a mobile setup. However, your Quadro GPU is not supported; we require a GeForce GPU. And while the Oculus PC App definitely works with VR-ready laptops, they must be plugged in to a power source to allow the app to run properly, and battery-only function is not guaranteed.

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!

I can provide power in the mobile environment. 

 

Why is a non Quadro card sufficient but the higher end Quadro card, which is a superset, is not?

 

This makes no sense. Our government, aerospace and defense clients buy the Quadro options. Why are they not considered sufficient?

 

It's like a game saying a Quest 2 is adequate but a Quest Pro is not. 

Hey @Xenonofarcticus42, I just wanted to jump in here to give my two cents on this GPU situation. Currently, only the GPUs listed on the Requirements to use Meta Quest Link article are compatible and supported for use with PCVR. As support, there isn't really anything we can do to change that.

That being said, if you have a GPU that isn't currently supported for use with Link and are interested in it being supported in the future, I would suggest posting on the Ideas Board here in the Forums. That is where people such as our developers and engineers look for ideas and suggestions from our community, and that will be the best place to get feedback like this seen by the right teams!

Make sure you smash that Kudos button!

durable
Honored Guest

Personally I think the Oculus app uses too many resources whilst I'm using airlink and normal link. That being said I just ditched it all together and used Virtual Desktop, should run fine if you have a 5g network. Your card is VR Ready, might not run extremely well with most games but none-the-less will still work.

WRT the 5g VR, we have actually worked on some projects using that. But in this case, the VR scene will be generated on the mobile computer.

 

As far as the superior Quadro card being rejected in favor of the less capable non-Quadro, I don't really think that's an "Idea". It's common sense. Everything about the card meets your specs, it's a bug that you don't have it whitelisted.

Is there any way for intelligent developers to bypass your silly whitelist when we know what we're doing, apparently better than you do?

I have exactly same problem with samsung galaxybook ultra (32gb ram, gtx 4070, i9 13900h cpu). 

Here is content of my file:

"VideoCardList": [
{
"Name": "NVIDIA GeForce RTX 4070 Laptop GPU",
"WhitelistName": "NVIDIA GeForce RTX 4070 Laptop GPU",
"DriverVersion": "31.0.15.3742",
"LUID": "0x0000000000019c62",
"VendorId": 4318,
"ProductId": 10272,
"SubsysVendorId": 0,
"SubsysRevId": 161,
"VRamMb": 8192,
"HybridGraphicsStatus": "NoOutput",
"Compatibility": 2,
"Compatibility_str": "FAIL",
"IsDriverCompatible": true,
"PassHybridCheck": false,
"VulkanCapable": true,
"total_DVI_port_count": 0,
"total_HDMI_port_count": 0,
"total_generic_DisplayPort_port_count": 0,
"total_internal_DisplayPort_port_count": 0,
"total_external_DisplayPort_port_count": 0,
"total_external_mini_DisplayPort_port_count": 0,
"active_DVI_port_count": 0,
"active_HDMI_port_count": 0,
"active_generic_DisplayPort_port_count": 0,
"active_internal_DisplayPort_port_count": 0,
"active_external_DisplayPort_port_count": 0,
"active_external_mini_DisplayPort_port_count": 0
},

How you see problem not in not supported card. I cannot use my 4070 notebook with quest 3! Any ideas?

Still need help?

Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.

If you need an agent to help with your Meta device, please contact our store support team here.

Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.

Check out some popular posts here:

Getting Help from the Meta Quest Community

Tips and Tricks: Charging your Meta Quest Headset

Tips and Tricks: Help with Pairing your Meta Quest

Trouble With Facebook/Instagram Accounts?