Jump to content

Oculus Quest 2 - Worth it!


Recommended Posts

I have extensive experience with the Varjo XR-1 used for flight simulation due to my work. So I can't give you a comparison against the G2 but against the Ferrari of VR/MR (at least it was until the XR-3 came out about a month ago). It still has way higher sweet spot resolution than the G2 (XR-1 60 ppd vs. G2 22ppd).

 

Compared to the eye-wateringly expensive "human eye resolution in sweet-spot" of the XR-1:

Has the XR-1 higher resolution? Yes.

Much better? No.

Is there a "oh my god this is amazing compared to Q2" in the XR-1? No.

Price to Performance? Q2 blows everything else on the market out of the water.

 

So to say I am impressed with the Q2 would be an understatement. Ontop of Oculus Link providing a brilliant PCVR experience due to ASW support, you also can use it in wireless mode via Virtual Desktop which works flawlessly (e.g. Half Life Alyx). Though this may not be of any interrest to you if you are only looking for a device for seated simulation. But to me this is an immense feature. I am certain that wireless VR is the short term future, once Virtual Desktop is able to add ASW or a similar technology into the mix (ATW is already supported).


Edited by Vitralette

Intel i5-8600k | 4.8GHz 

ASUS GeForce RTX3070 Dual | 1980MHz | 8GB GDDR6  

G.Skill Ripjaws V DDR4-3200-CL16 | 32GB   

Oculus Quest 2

F/A-18C Hornet | UH-1H Huey

Link to post
Share on other sites
11 minutes ago, Vitralette said:

I have extensive experience with the Varjo XR-1 used for flight simulation due to my work. So I can't give you a comparison against the G2 but against the Ferrari of VR/MR (at least it was until the XR-3 came out about a month ago). It still has way higher sweet spot resolution than the G2 (XR-1 60 ppd vs. G2 22ppd).

 

Compared to the eye-wateringly expensive "human eye resolution in sweet-spot" of the XR-1:

Has the XR-1 higher resolution? Yes.

Much better? No.

Is there a "oh my god this is amazing compared to Q2" in the XR-1? No.

Price to Performance? Q2 blows everything else on the market out of the water.

 

So to say I am impressed with the Q2 would be an understatement. Ontop of Oculus Link providing a brilliant PCVR experience due to ASW support, you also can use it in wireless mode via Virtual Desktop which works flawlessly (e.g. Half Life Alyx). Though this may not be of any interrest to you if you are only looking for a device for seated simulation. But to me this is an immense feature. I am certain that wireless VR is the short term future, once Virtual Desktop is able to add ASW or a similar technology into the mix.

 

Very interesting. I've wondered what these Varjo's are like but as I'm a mere mortal I wont expect to find out🤣. Interesting what you say about it compared to the Q2. 

 

Have you used the xr-1 in dcs? I presume that it's just too demanding for dcs with its current demands on a CPU thread.


Edited by Hoirtel
Link to post
Share on other sites
On 1/13/2021 at 7:53 AM, Brainfreeze said:

Check out the cockpit with a G2 and your Quest2 cockpit will look very much blurry to you 🙂

Not that reply is any help . Thanks but no thanks this is a quest2 thread . 🤔

Sniper G1 - Z87 ~ 4690K @ 4.3 - AMD Vega64 - HyperX 32 :GB @ 1866 - Win10 - 64bit Pro - T-50 Mongoose - CM2 Throttle - VKB T-bar Rudders - Trackir5 . I'm a dot .

Link to post
Share on other sites

Is the Q2 much of an improvement on the rift s in terms of actually being able to read dials/displays in the cockpit? If it is a big improvement does this have a big impact on performance? 

I currently use a rift s with super sampling set to 1.3 in the OTT, if I had a Q2 could I get similar performance with SS at 0 but be able to read stuff in the cockpit better?

Link to post
Share on other sites
32 minutes ago, Flyingfish said:

Is the Q2 much of an improvement on the rift s in terms of actually being able to read dials/displays in the cockpit?

It will depend on cockpits.  For me I can't use the INS panel on a mirage without zooming on the Quest 2.  In the harrier, the MFD is also not readable without zooming most of the time (reflections etc). most of the other stuff is normally pretty readable. It is not super sharp but clear enough. 

i7 10700@2.6Ghz / RTX 3080 / Reverb G2 / TrackIR

Link to post
Share on other sites
4 hours ago, Flyingfish said:

Is the Q2 much of an improvement on the rift s in terms of actually being able to read dials/displays in the cockpit? If it is a big improvement does this have a big impact on performance? 

I currently use a rift s with super sampling set to 1.3 in the OTT, if I had a Q2 could I get similar performance with SS at 0 but be able to read stuff in the cockpit better?

I've just switched from a G2 to a Q2. I used to use a rift S at 1.5ss. I much prefer the oculus ASW and general feel over the G2. The Q2 for me at the moment is better than my rift, bit sharper but no screen door. However to get this I am throwing a sh*t ton of power at it (3090) as the link cable is a downside. I run at 80hz +full res in oculus device graphics, 1.2 SS in oculus tray tool with a res width of 4000 and bitrate on 500. 1.3+ SS look really fantastic but sadly it gets laggy on deck of SC and low level flight so no good. I feel that the quest 2 can look great but link cable needs more power than it should to get there. Hope that helps!

 

Link to post
Share on other sites
On 1/9/2021 at 2:55 PM, Vitralette said:

Oculus App lets you set the render resolution not pixel density. 

 

To achieve native resolution (3664x1920) in the sweetspot you will need to set render resolution to 5408x2736 (due to lense barrel distortion). This is the most confusing part about the Q2 setup because most people think setting the slider to 1.7x at 72Hz or 1.5x at 90Hz (=5408x2736) is a supersampling multiplier, which it isnt. This Tweet by Volga Aksoy explaines this.

 

 

What are your VR settings in DCS? 1.0 pixel density?


Edited by Caster
Posted twice

Fly fast and leave a pretty wreck

Link to post
Share on other sites
3 hours ago, Caster said:

What are your VR settings in DCS? 1.0 pixel density?

 

Don't use PD. Use pixel override in oculus debug tool or supersampling in oculus tray (3rd party app - just controls the debug tool for you). 

Link to post
Share on other sites
12 minutes ago, Hoirtel said:

Don't use PD. Use pixel override in oculus debug tool or supersampling in oculus tray (3rd party app - just controls the debug tool for you). 

Soo.... Set it to 1.0?

Fly fast and leave a pretty wreck

Link to post
Share on other sites
10 minutes ago, Caster said:

Soo.... Set it to 1.0?

1.0 is no change. Anything over 1.0 is super sampling anything under is undersampling. Start with 1.1 and work up until it won't work anymore. Depends on your system power. This has a big effect on performance and visual quality. 

Link to post
Share on other sites
Am 18.1.2021 um 21:59 schrieb Caster:

Soo.... Set it to 1.0?

 

Am 18.1.2021 um 21:46 schrieb Hoirtel:

Don't use PD. Use pixel override in oculus debug tool or supersampling in oculus tray (3rd party app - just controls the debug tool for you). 

 

 

Don't use Oculus Tray Tool (OTT) because its not being supported any longer by the dev.

If you have to then leave all settings to default. Meaning PD = 1.0.

 

Oculus Debug Tool (ODT): Same as OTT. Leave everything at Default. "Pixels Per Display Override" = 0 (same as PD =1.0).

 

DCS - PD = 1.0

 

The only slider you crank up until your PC melts is the render resolution slider within oculus software.

If you can set it to max (5408x2736) your Q2 will run at native resolution without any up or downsampling.


Edited by Vitralette

Intel i5-8600k | 4.8GHz 

ASUS GeForce RTX3070 Dual | 1980MHz | 8GB GDDR6  

G.Skill Ripjaws V DDR4-3200-CL16 | 32GB   

Oculus Quest 2

F/A-18C Hornet | UH-1H Huey

Link to post
Share on other sites
58 minutes ago, Vitralette said:

 

I dont know why you think that, version 0.87 was released just 3 days ago, the autoupdate function in OTT works perfectly just click update. 
ApollyonVR is doing a good job with it. Can be somewhat hard to find if one likes to download a installer also apart from just clicking autoupdate but  I have been able to locate them so far 

https://forums.oculusvr.com/community/discussion/47247/oculus-traytool-supersampling-profiles-hmd-disconnect-fixes-hopefully/p1

58 minutes ago, Vitralette said:

 

Don't use Oculus Tray Tool (OTT) because, its not being supported any longer by the dev.

If you have to then leave all settings to default. Meaning PD = 1.0.

 

Oculus Debug Tool (ODT): Same as OTT. Leave everything at Default. "Pixels Per Display Override" = 0 (same as PD =1.0).

 

DCS - PD = 1.0

 

The only slider you crank up until your PC melts is the render resolution slider withing oculus software.

If you can set it to max (5408x2736) your Q2 will run at native resolution without any up or downsampling.

 

 

Link to post
Share on other sites
8 hours ago, Vitralette said:

 

 

 

Don't use Oculus Tray Tool (OTT) because its not being supported any longer by the dev.

If you have to then leave all settings to default. Meaning PD = 1.0.

 

Oculus Debug Tool (ODT): Same as OTT. Leave everything at Default. "Pixels Per Display Override" = 0 (same as PD =1.0).

 

DCS - PD = 1.0

 

The only slider you crank up until your PC melts is the render resolution slider within oculus software.

If you can set it to max (5408x2736) your Q2 will run at native resolution without any up or downsampling.

 

 

Yeah agreed about the OTT tool, just use the debug tool.

 

I personally have the oculus resolution slider maxed and set 1.2 in the debug. I personally find this improves the visuals by a good margin, 1.3 and 1.4 look even better but its very demanding on performance!

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...