How to use Oculus Quest and Aces High on Steam

[Mister Fork]

So... been spending about 50 minutes trying to figure out how to get Aces High started with a Quest via steam instead of Monday Night Madness. How in the hell do you get it to work? When I select the Oculus version in the steam startup for Aces High, it goes "Aces High does not currently support your currently active headset."    HAAAALP

[FLS]

You'll want to start the Oculus program and Steam, then start AH3, then select use oculus VR. That's how it works with the CV1 and Rift S. I haven't tried it with Quest. Hopefully it works the same way when tethered.

One thing to check, when you are tethered and in the Oculus program, see if AH3 is available from the store. That should show you if you're in the Quest version or the regular version of Oculus. I expect you need to be in the regular Oculus program for AH3 to work.

[Mister Fork]

You'll want to start the Oculus program and Steam, then start AH3, then select use oculus VR. That's how it works with the CV1 and Rift S. I haven't tried it with Quest. Hopefully it works the same way when tethered.

One thing to check, when you are tethered and in the Oculus program, see if AH3 is available from the store. That should show you if you're in the Quest version or the regular version of Oculus. I expect you need to be in the regular Oculus program for AH3 to work.

I followed those steps and it goes "Aces High does not currently support your currently active headset." 

[FLS]

Which version of Oculus are you using? It's listed under settngs/general.

What happens if you select Steam VR after you start AH3?

When you look at devices on the oculus program is everything ok?

[Vulcan]

I use the non-steam AH3, at the prompt for Oculus say OK and it just works.

edit: is your Quest showing up as the Active Headset in the Oculus app?

[Puma44]

So... been spending about 50 minutes trying to figure out how to get Aces High started with a Quest via steam instead of Monday Night Madness. How in the hell do you get it to work? When I select the Oculus version in the steam startup for Aces High, it goes "Aces High does not currently support your currently active headset."    HAAAALP

Why did you choose to do it with steam vs MNM?

[Drano]

I use the non-steam AH3, at the prompt for Oculus say OK and it just works.

edit: is your Quest showing up as the Active Headset in the Oculus app?

Same here.


Sent from my iPad using Tapatalk

[Puma44]

I use the non-steam AH3, at the prompt for Oculus say OK and it just works.

edit: is your Quest showing up as the Active Headset in the Oculus app?

My method also.  KISS principle.

[FLS]

There is no difference between starting the Steam version and regular version of AH3 when using the Rift or Rift S.

The issue the OP is having is using the Quest with a tether. 

It's likely an Oculus issue but so far we're still looking for more information.

[Drano]

FLS to that point I think I read on the oculus forums that at least as of this morning, the Quest link was not working on the PTC version of the software and this is a known problem. If you have a Quest, are trying to use the cable and having no success, try opting out of the PTC and going with the stable version.

Of course it still may not work depending on which cable you're using as what I'm getting is that it's still kind of an issue.



Sent from my Moto Z (2) using Tapatalk

[FLS]

What Vulcan and I have been trying to confirm with the OP is that the Quest is working as a tethered device and not just as connected to power.

Oculus claimed that Oculus Link software will work with most high-quality USB 3 cables.

They also spec the cable as USB 3.2 Gen 1 Signaling 5 Gbps USB 2Backwards Compatible which isn't what they originally said.

[Vulcan]

Yeah I had the PTC issue. It was on version 13 and the Quest was on 12. Just turn off the PTC box (public test channel), it will roll back the version.

[FLS]

I got my Quest working with AH3.

I started the Oculus software.

I started the Quest by itself.

I plugged the Quest into my PC.

I got a pop-up asking if I wanted to use Link and acknowledged it.

I saw the regular Home screen I see with the Rift instead of the Quest screen.

I started Steam and started the Steam version of AH3.

I selected use Oculus VR.

I got a message saying my device wasn't recognized. I clicked OK and AH3 started and ran normally.

The performance is not as smooth as the Rift and Rift S but it does work.

[Mister Fork]

I got my Quest working with AH3.

I started the Oculus software.

I started the Quest by itself.

I plugged the Quest into my PC.

I got a pop-up asking if I wanted to use Link and acknowledged it.

I saw the regular Home screen I see with the Rift instead of the Quest screen.

I started Steam and started the Steam version of AH3.

I selected use Oculus VR.

I got a message saying my device wasn't recognized. I clicked OK and AH3 started and ran normally.

The performance is not as smooth as the Rift and Rift S but it does work.

Ok, I'll take a look at this method tonight to see if that resolves the issue.   As for the PTC comment... what? What is PTC? What is Oculus software version issue between v12 and v13?  Sorry, I'm out of the loop on this issue with Oculus and the PTC version of the software.  Can someone give me a colesnotes version? Please?   

[Drano]

Well in the oculus software there's an option to choose whether to participate in the PTC or Public Test Channel (beta version currently v13) of their software. If you haven't checked it you're not in it and that means you're on version 12.x. That's as good as it's gonna get for you if you're using the quest and link. If you HAVE checked it and your quest isn't working via the link that's likely the reason why. It's a known issue with the PTC and the quest w/link. In that case just uncheck it and the software will revert back to the known stable release (v12).

Either way there has been performance issues since they decided to homogenized all their software and drivers into one version. This has not really optimized anyone's HMD. My Rift S isn't running the same FR as it was in mid December before they did this. They're working on it. Say they've identified the problem.

Sent from my Moto Z (2) using Tapatalk