Introducing Meta Quest 3

[Mr Wave Off]

vor 32 Minuten schrieb Th3ChosenOn3:

I think you're running into the same issues that I and a few other 7900 XTX owners are experiencing with Virtual Desktop. Virtual Desktop seems to have a bug at the moment when you use VDXR and the H.265/AV1 Codec on DCS World. You can get it working by using H.264 but even at 400 mbps it won't look as good as using the oculus app at the moment. Not sure if they're working on a fix or when it might get resolved, so might be best to try out the oculus app in the meantime.

Follow this guide, and you should get to a good starting point with the oculus app:

 

Thanks for your response, this issue gave me headaches for the last couple of days and i couldn´t find a source with further information.

Ok so it makes no sense using VD with an AMD GPU at the moment. I hope they´re working on a fix or else i just spent 20 bucks for nothing.

And thanks too for offering me an alternative with the Video Guide, much appreciated Sir.

[Lorenzo.D]

There Is the beta of virtual desktop see on discord on announcement channels i think they fixed it

Inviato dal mio CPH2219 utilizzando Tapatalk

[Th3ChosenOn3]

10 hours ago, Lorenzo.D said:

There Is the beta of virtual desktop see on discord on announcement channels i think they fixed it

Inviato dal mio CPH2219 utilizzando Tapatalk
 

Virtual Desktop 1.29.3 Beta is the only version I can see, and is unfortunately the one that doesn't work with H265/AV1 on the 7900 XTX.

[AlpineGTA]

I've been considering the Quest 3 as a replacement for my G2 but I've been put off by no display port cable, reports of jagged lines due to the angled displays, screen door effect and battery life, but having seen this through the lens video, I have to say I'm really surprised how good it looks. It's a pity he didn't include the usual through the lens of the DCS cockpit though.

 

[gwizdek]

4 minutes ago, AlpineGTA said:

It's a pity he didn't include the usual through the lens of the DCS cockpit though.

I think it's coming in the next video where he's going to compare Q3 with PCVR headsets.

[Hoirtel]

3 minutes ago, AlpineGTA said:

I've been considering the Quest 3 as a replacement for my G2 but I've been put off by no display port cable, reports of jagged lines due to the angled displays, screen door effect and battery life, but having seen this through the lens video, I have to say I'm really surprised how good it looks. It's a pity he didn't include the usual through the lens of the DCS cockpit though.

 

No display port cable - It works fine. Yes it would be better for PCVR with DP but I think most lower priced headsets are going this way.

reports of jagged lines due to the angled displays - It still has aliasing, but the angled displays reduce this for horizontal lines. Its better than Q2 for sure, certainly won't be worse than G2

screen door effect - Will be same as G2, its really really faint.

[AlpineGTA]

Yes, seeing that through the lens video pretty much negated most of those concerns. It looks really good. And I'm guessing it will look fine through link cable. I never had a problem with link cable and my Quest 2 to be fair but obviously display port is always preferred for PCVR. The only real concern left is battery life and always having to keep the battery charged. That is one thing I always find a pain with my Quest 2. I use a powered hub for that but I've heard reports of the Q3 draining even with a powered hub. 

[Snuten]

Im just gonna share my settings for the Quest 3 that Im quite happy with as a former Reverb G2 user. Sure, with the G2 and 4xMSAA I get much shaper image in centre and can see much further (witch I think is because I used much higher SS but it also was 90hz at 45 fps with Motion Re-projection)

Now Im running in 72fps almost fluid with no motion re-projection(ASW) like 95% of the times, even low over dense areas, with the exception of Marinas Map, that one have issues even over the sea.(I have all maps) 

I do use both DLSS with a DCS PD of 1.35(enter it via the options.lua file) and 1.3x scale @72hz in Oculus app. And I also override this a bit via OpenXR Toolkit and using CAS as scaler(see image). I know that Im using scaling and stuff via several plugins/apps. But I can't see any direct performance hit by doing so. Tried all combos now I think  

But this is running really smooth with some exceptions because I had to move the DCS install to a Sata SSD(to get the multithreading to work without all the constant stutter). So I guess the occasional "evenly burst stutter" I get now is when loading in areas/textures, especially in the first 3-5 minutes, and that it's due to the slower SATA drive. 

All in all, the 72fps, slightly better FOV, edge to edge clarity and the pancake lenses, this wins over the G2 for me.

My specs:

Win10 64bit, AMD 7800X3D, 32 GB 6000mhz Ram, RTX-4090, Quest 3 with an inline powered link cable. 

 

The last image is what it looks like over Haifa in the Syria map.

Unfortunately my Windows Screenshot plugin crashed and did not restart when I took screenshots of nVidia settings, but I think the rest is more common sense.

Forgot about the Swedish in the Nvidia settings. But I think it is listed in the same order?

In the 1st image and in bold text is FXAA=Off and Edge AA=On and Prefer Maximum Performance
In the 2nd image it is Texture filtering and is in order: On, Performance, Allow and On
 

Edited October 27, 2023 by Snuten

[itarrow]

So I am just an old fart of 55 years old, with an Index and a PC that I will soon change as it has an old 2080TI (still working well with my Index tough).

I am considering buying a Q3 both as an upgrade vs the Index as well as for the standalone option, and, for PCVR and Sims like DCS, I was thinking to use it wired so not to have quality problems.

Reading this thread here however intimidates me: is it really so hard to get some quality out of a Q3 in DCS ? I am not talking about wireless remote streaming here... Simple, easy, wired connection from a Q3 to my PC to play DCS, BMS, Elite Dangerous, all seated Sims (so wired is not a problem).

Is it really hard to get some quality from a Q3 wired, so to see an improvement vs my current Index ?

[Dogmanbird]

yeah, unfortunately it's been a lot of fiddling in the beginning

 

Edited October 27, 2023 by Dogmanbird

[sze5003]

It's a lot of testing and messing with oculus settings, resolution, bitrate, back and forth.

I have a quest pro and it's tiring. I can't get the multithreaded version of dcs working for me without it turning into 5 fps on the main menu at some point after some time. It doesn't start like that, starts fine and I can fly ok with stuttering here and there but eventually I have to use my headset controller to quit DCS through Link because dcs becomes unresponsive.

I've stuck to just running the single threaded version for now.

[Vladdo]

Think I finally found out my issue.... friggin Hornet.. it has a known issue of when the radar is on, it pauses every 5 seconds or so.. !@#!^!@#!^%!@#!^!@#!#

It's so nice to finally see it smooth...

[samplethief]

21 hours ago, Snuten said:

Im just gonna share my settings for the Quest 3 that Im quite happy with as a former Reverb G2 user. Sure, with the G2 and 4xMSAA I get much shaper image in centre and can see much further (witch I think is because I used much higher SS but it also was 90hz at 45 fps with Motion Re-projection)

Now Im running in 72fps almost fluid with no motion re-projection(ASW) like 95% of the times, even low over dense areas, with the exception of Marinas Map, that one have issues even over the sea.(I have all maps) 

I do use both DLSS with a DCS PD of 1.35(enter it via the options.lua file) and 1.3x scale @72hz in Oculus app. And I also override this a bit via OpenXR Toolkit and using CAS as scaler(see image). I know that Im using scaling and stuff via several plugins/apps. But I can't see any direct performance hit by doing so. Tried all combos now I think  

But this is running really smooth with some exceptions because I had to move the DCS install to a Sata SSD(to get the multithreading to work without all the constant stutter). So I guess the occasional "evenly burst stutter" I get now is when loading in areas/textures, especially in the first 3-5 minutes, and that it's due to the slower SATA drive. 

All in all, the 72fps, slightly better FOV, edge to edge clarity and the pancake lenses, this wins over the G2 for me.

My specs:

Win10 64bit, AMD 7800X3D, 32 GB 6000mhz Ram, RTX-4090, Quest 3 with an inline powered link cable. 

 

The last image is what it looks like over Haifa in the Syria map.

Unfortunately my Windows Screenshot plugin crashed and did not restart when I took screenshots of nVidia settings, but I think the rest is more common sense.

Forgot about the Swedish in the Nvidia settings. But I think it is listed in the same order?

In the 1st image and in bold text is FXAA=Off and Edge AA=On and Prefer Maximum Performance
In the 2nd image it is Texture filtering and is in order: On, Performance, Allow and On
 

 

Wow just tried these settings on my 4070ti and they work great. Thanks for sharing!

Dont suppose you would mind sharing your VR tab in the DCS settings too?
 

Edited October 27, 2023 by samplethief

[Snuten]

7 hours ago, samplethief said:

Wow just tried these settings on my 4070ti and they work great. Thanks for sharing!

Dont suppose you would mind sharing your VR tab in the DCS settings too?
 

 

Glad you liked it!  In the DCS VR settings tab it just showing my 1.35 PD that I have set in the options.lua (since in DCS you just get increments of whole decimals) And I think I have some numbers on the masking thing where DCS uses AA (if I remember correct) and I think it is about 0.43 or something). I can check again tomorrow.

*Edit, I started it up and took a screenshot.  null

Edited October 27, 2023 by Snuten

[Snuten]

Regarding DLSS I wonder one thing. Let's say that Im using 1:1 in the Oculus app(or in WMR tools/ Steam) and in DCS using 1.0 in PD, I will get one image that is 1:1, what ever the headset is. And then I turn DLSS on in DCS. It will get blurry since now DCS renders in lower resolution and DLSS is upscaling it to 1:1 resolution? What is the amount that DLSS tells DCS(or what ever game) to render at? 

I mean, since it gets blurrier and I must compensate that by increasing resolution. DLSS must somehow tell the game to render at a lower resolution to gain performance, then upscale it by its "magic" AI and stuff. Since the performance gets better but image quality gets worse. So what's is the value DCS is rendering in? Or what is DLSS telling DCS to render in when DLSS is turned on?

Or how is it working? Does anyone know?

 

[samplethief]

1 hour ago, Snuten said:

Glad you liked it!  In the DCS VR settings tab it just showing my 1.35 PD that I have set in the options.lua (since in DCS you just get increments of whole decimals) And I think I have some numbers on the masking thing where DCS uses AA (if I remember correct) and I think it is about 0.43 or something). I can check again tomorrow.

*Edit, I started it up and took a screenshot.  null

 

Thanks. I left my PD on 1.0 here as I doubt the 4070ti could handle it very well much higher.

It runs at a stable 72fps and looks better than it ever has for me with all of your other settings set!

Edited October 27, 2023 by samplethief

[MurrayCod]

I haven't tried VR (yet), but was wondering if the Quest 3 is used just for DCS (and IL2) do you still need to have an active Meta subscription?

[diamond26]

On 10/26/2023 at 9:26 PM, Snuten said:

And I also override this a bit via OpenXR Toolkit

I believe that the resolution you finally use is the one set in the override option in OpenXR toolkit. You can see what resolution DCS was running on in OpenXR toolkit log.

Edited October 28, 2023 by diamond26

[Snuten]

3 hours ago, diamond26 said:

I believe that the resolution you finally use is the one set in the override option in OpenXR toolkit. You can see what resolution DCS was running on in OpenXR toolkit log.

 

Thanks, I'm gonna check that log and see. 

[diamond26]

1 hour ago, Snuten said:

Thanks, I'm gonna check that log and see. 

On my Q2 2 examples (using Quad Views fixed)

 

[Dogmanbird]

On 10/28/2023 at 11:30 AM, MurrayCod said:

I haven't tried VR (yet), but was wondering if the Quest 3 is used just for DCS (and IL2) do you still need to have an active Meta subscription?

An old Oculus account or a basic Meta account is still required, but you don't need a full facebook account from what I can see. I'm just using my old Oculus account.

[Gorn_GER]

Am 24.10.2023 um 00:14 schrieb Grodin:

Could some quest 3 owner vefiry if F16 OSB button texts (HSD, TGP, WPN, SMS etc etc) are easily and clearly readable from the default head position or do you have to move closer to see them well? Trying to figure out how much clarity i would be losing if changing from G2 to Q3.

Because I do not think that your question was directly answered: 

Don’t worry!

I came from G2 and got to Q3. I had problems first that got fixed by setting it up correctly with the Help of Dogmanbird and others here in the Thead and now the visual are almost clear and not just a sweetspot but most of the FOV is nearly as shape as the tiny sweetspot on the G2. Most of MFD visual clearness got lost by DLSS since 2.9 and with this better performance I have to lean in a little on both devices to not have the ghosting but it is just the ghosting that annoys, otherwise it would be clear. I never tested in F16 just in F/A18 and AV8B. Since you sit closer to the MFDs in F16 you may have even better view in Q3 because the FOV is wider and you not have to turn your head. 
 

I am all in all surprised by the Q3, I won’t go back to my G2. I just keep the G2 in case my girlfriend wants to play beatsaber in the same time, I want to play DCS because the G2 still is a good headset. Just not as good as the new Q3. 

vor 11 Stunden schrieb Dogmanbird:

An old Oculus account or a basic Meta account is still required, but you don't need a full facebook account from what I can see. I'm just using my old Oculus account.

Behind my meta account there is an extra Facebook account linked and I think this link is needed. But since this account is separate and I have no contacts or information in there, it is the same as if you need a PICO/Steam/Pimax account

[Snuten]

On 10/28/2023 at 12:52 PM, diamond26 said:

On my Q2 2 examples (using Quad Views fixed)

 

Thanks, and sorry for late reply.  

This is what mine says, so it seams like it is overriding it:

[OXRTK] 2023-10-31 16:18:10 +0100: Requesting extra extension: XR_KHR_win32_convert_performance_counter_time
[OXRTK] 2023-10-31 16:18:10 +0100: Application name: 'DCS World', Engine name: ''
[OXRTK] 2023-10-31 16:18:10 +0100: Using OpenXR runtime Oculus 1.89.0
[OXRTK] 2023-10-31 16:18:10 +0100: Using OpenXR system Meta Quest 3
[OXRTK] 2023-10-31 16:18:10 +0100: Overriding OpenXR resolution: 2910x3150
[OXRTK] 2023-10-31 16:18:10 +0100: Using OpenXR resolution (no upscaling): 2910x3150
[OXRTK] 2023-10-31 16:18:10 +0100: Using OpenXR resolution (no upscaling): 2910x3150
[OXRTK] 2023-10-31 16:18:13 +0100: Using Direct3D 11 on adapter: NVIDIA GeForce RTX 4090
[OXRTK] 2023-10-31 16:18:13 +0100: Open menu with CTRL+NEDPIL
[OXRTK] 2023-10-31 16:18:13 +0100: Creating swapchain with dimensions=3784x4096, arraySize=1, mipCount=1, sampleCount=1, format=29, usage=0x21
[OXRTK] 2023-10-31 16:18:13 +0100: Creating swapchain with dimensions=3784x4096, arraySize=1, mipCount=1, sampleCount=1, format=29, usage=0x21
[OXRTK] 2023-10-31 16:18:15 +0100: Projection calibration: 0.21166, 0.19319 | -0.21166, 0.19319
[OXRTK] 2023-10-31 16:18:17 +0100: Late initializeInterceptor() call
[OXRTK] 2023-10-31 16:35:32 +0100: xrEndFrame: XrResult failure [XR_ERROR_SESSION_NOT_RUNNING]
    Origin: OpenXrApi::xrBeginFrame(m_vrSession, nullptr)
    Source: D:\a\OpenXR-Toolkit\OpenXR-Toolkit\XR_APILAYER_MBUCCHIA_toolkit\layer.cpp:3251
[OXRTK] 2023-10-31 16:38:10 +0100: xrEndFrame: XrResult failure [XR_ERROR_SESSION_NOT_RUNNING]

[Dogmanbird]

Hi, has anyone's headset updated to v59 yet (announced a few weeks back)?   I'm still on v57 and it hasn't found any updates.  The update apparently has a couple of qol niceties for PCVR users

[Hoirtel]

14 minutes ago, Dogmanbird said:

Hi, has anyone's headset updated to v59 yet (announced a few weeks back)?   I'm still on v57 and it hasn't found any updates.  The update apparently has a couple of qol niceties for PCVR users

Not when I last checked a day or two ago. Having been a meta user for couple of years I know that updates come almost randomly. Sometimes I've had them immediately, other times I've waited ages. 

What are the PCVR changes? Didn't see any mentioned.