Introducing Meta Quest 3

[samplethief]

1 minute ago, Snuten said:

Thanks, I just read the release notes from the News section.  But that's a bummer. For some reason MT for me is the worst stutter-fest. Don't understand why. I even upgraded my whole computer from i9 900k + 3090 to 7800x3D and 4090. Exactly the same extreme stutter with MT.

But I tried both DLAA, TAA, and it looked awful, blurry mess even though Im running about 3000x3000px per eye. So back to ST DCS and MSAA 4x @72hz

Snuten, do you have the game installed on an NVME? Might sound crazy but try installing it to a sata ssd instead. 

Fixed microstutters for me. Nothing else worked. Even when I upgraded to a 7800X3D.

[Snuten]

2 minutes ago, samplethief said:

Snuten, do you have the game installed on an NVME? Might sound crazy but try installing it to a sata ssd instead. 

Fixed microstutters for me. Nothing else worked. Even when I upgraded to a 7800X3D.

Hmm yes I do. Darn it, could that be the problem? I just bought a new dedicated NVME for DCS . Is it possible to just move the whole DCS folder to a Sata SDD, or must I reinstall it?(question open for those who knows)

[samplethief]

2 minutes ago, Snuten said:

Hmm yes I do. Darn it, could that be the problem? I just bought a new dedicated NVME for DCS . Is it possible to just move the whole DCS folder to a Sata SDD, or must I reinstall it?(question open for those who knows)

Yep give it a try and ill be interested to know if it worked for you too.

I believe I just moved the install directory in steam. So try that. (or manually copy them i guess)

I dont think this fix is very widely known. I searched high and wide for it and stumbled across one thread somewhere. When i mentioned it to somebody else, they just laughed and said I was crazy haha

Edited October 20, 2023 by samplethief

[Dogmanbird]

For 700x3D owners, do you have the AMD chipset drivers installed? (from AMD website)

I've read a couple of messages where users of 5800x3d, who moved to 7800x3d and new motherboard, were unable to achieve the same performance of 5800x3d in DCS for some reason. Might be motherboard bios related?

edit - i'm still using a 5800x3d

 

Edited October 20, 2023 by Dogmanbird

[Snuten]

Just now, samplethief said:

Yep give it a try and ill be interested to know if it worked for you too.

I believe I just moved the install directory in steam. So try that. (or manually copy them i guess)

Aha, I guess steam have a fancy tool to move. Im using stand alone version. But I will update you when I have tried it.  Thanks

1 minute ago, Dogmanbird said:

For 700x3D owners, do you have the AMD chipset drivers installed? (from AMD website)

I've read a couple of messages where users of 5800x3d, who moved to 7800x3d and new motherboard, were unable to achieve the same performance of 5800x3d in DCS for some reason. Might be motherboard bios related?

 

Yes, I have latest chipsets and latest stable Bios installed. But it have exactly the same "for no reason" stutter as I had on my i9 000k. About the same frame times as well. 

[samplethief]

4 minutes ago, Dogmanbird said:

For 700x3D owners, do you have the AMD chipset drivers installed? (from AMD website)

I've read a couple of messages where users of 5800x3d, who moved to 7800x3d and new motherboard, were unable to achieve the same performance of 5800x3d in DCS for some reason. Might be motherboard bios related?

 

I do have the drivers installed. But thankyou

[Hoirtel]

1 hour ago, Dogmanbird said:

I'm cabled link

I'm using dcs in-game VR setting pixel density for  supersampling. It's at max 2.5

I don't use openxrtoolkit for anything except for hand tracking emulation in MSFS, but it's res override option achieves the same as doing it in game. Set it to max with in-game at 1

Oculus debug tool is set to defaults except for;

Link sharpening = quality

Encoder bit rate 500

Codec H264 (but not much noticeable difference with H265)

I've got ASW set to 30Hz and headset running at 90Hz - if not aware, grass and road vehicles seem to animate at 30 fps/Hz if ASW is set at 30, therefore no interpolation to 90 (so may have some ATW ghosting), while most other graphics (buldings / terrain / trees) will be interpolated to 90Hz and shouldn't have ghosting/doubling appearance

 

So far I've not been able to get VD or airlink to look as good as cable

 

 

 

Great, thanks for the details. So I have supersampled and it improves DLAA, still less sharp in distance but that is probably the price of no shimmering at all. Probably done DCS VR for too long and got used to it. Now it's a bit of blur and ghosting, totally different experience. 

I used openxr overide but then did 1.2/1.3 in ODT which I feel is much the same but prefer the multiplier to a pixel level option.

Also running 940 bitrate. Anything else looks compressed on the terrain.

The old advice was not to use in game PD, but I suppose its all new rules now! Maybe I will try that. 

I will also try your 30hz setting, I usually run at 80fps/40 reprojected. It's that rendering a third of the frames and reprojecting more? 

With all this SS I feel I really need to keep a closer eye on my 12vhwpr cable... Eek. 4090 seems to love the punishment though! Runs well even with all that and high settings. Nuts. 

Edited October 20, 2023 by Hoirtel

[Lange_666]

30 minutes ago, Snuten said:

For some reason MT for me is the worst stutter-fest. Don't understand why. I even upgraded my whole computer from i9 900k + 3090 to 7800x3D and 4090. Exactly the same extreme stutter with MT.

Do you run OpenXR Toolkit?
In it, setting Turbo Mode to ON removed my stutters in MT.
Comes with a bit of a drawback because there's a bit if "small" black banding flickering on the edge of the FOV when moving your head quickly (Rift-S, not a Q3). 

Edited October 20, 2023 by Lange_666

[samplethief]

16 minutes ago, Hoirtel said:

Great, thanks for the details. So I have supersampled and it improves DLAA, still less sharp in distance but that is probably the price of no shimmering at all. Probably done DCS VR for too long and got used to it. Now it's a bit of blur and ghosting, totally different experience. 

I used openxr overide but then did 1.2/1.3 in ODT which I feel is much the same but prefer the multiplier to a pixel level option.

Also running 940 bitrate. Anything else looks compressed on the terrain.

The old advice was not to use in game PD, but I suppose its all new rules now! Maybe I will try that. 

I will also try your 30hz setting, I usually run at 80fps/40 reprojected. It's that rendering a third of the frames and reprojecting more? 

With all this SS I feel I really need to keep a closer eye on my 12vhwpr cable... Eek. 4090 seems to love the punishment though! Runs well even with all that and high settings. Nuts. 

 

Curious if you get audio stuttering through the headset when running at 940 bitrate?

Seems ever since I enabled that setting in the oculus debug tool, my oculus audio constantly stutters and crackles. 
(Using the link cable)

I have been using my normal headphones instead.

Edited October 20, 2023 by samplethief

[Hoirtel]

1 minute ago, samplethief said:

Curious if you get audio stuttering through the headset when running at 940 bitrate?

Seems ever since I enabled that setting in the oculus debug tool, my oculus audio constantly stutters and crackles. 
(Using the link cable)

I have been using my normal headphones instead.

 

I don't use the headset audio anyway. Just prefer headphones. 

[Dogmanbird]

i get the occasional audio stutters at anything over 500

 

i think the dcs update is quite stunning. the wind through the trees and grass is terrific

though I can't work out how to get the VR controller working. is that another thing mentioned in the changelog?

Edited October 20, 2023 by Dogmanbird

[Snuten]

1 hour ago, Lange_666 said:

Do you run OpenXR Toolkit?
In it, setting Turbo Mode to ON removed my stutters in MT.
Comes with a bit of a drawback because there's a bit if "small" black banding flickering on the edge of the FOV when moving your head quickly (Rift-S, not a Q3). 

 

Yes, I'm using the Toolkit. When I turn on Turbo Mode with the Q3, it just freeze.  Not sure if it's because of the Q3. Did not freeze with Turbo on my G2. But it did not help with the stutter though. But thanks for the tip.

[Snuten]

1 hour ago, samplethief said:

Curious if you get audio stuttering through the headset when running at 940 bitrate?

Seems ever since I enabled that setting in the oculus debug tool, my oculus audio constantly stutters and crackles. 
(Using the link cable)

I have been using my normal headphones instead.

 

I got serious audio cut outs when I was using 900 bitrate. Lowered to 500 and it was gone, but looks bad. So I increased it step by step, and now Im running 800 and have not had any cutouts yet. Also changed my USB port. I was using a USB-C 3.2 Gen 2 x2 or was it is called, but saw that I got different speeds every time I did the Cable test via Oculus app. It went from 2.9gb/s down to 1.9 GB/s. But with the other "default" USB-C port I get constant 2.6 GB/s when testing. Perhaps that also helped against the audio cuts?

[Lange_666]

3 hours ago, Snuten said:

Yes, I'm using the Toolkit. When I turn on Turbo Mode with the Q3, it just freeze.  Not sure if it's because of the Q3.

No it's not because of the Q3. I have the same with my Rift-S. When i change the Turbo setting in MT, ON or OFF doesn't matter, 8/10 it freezes and then DCS crashes.
But there is a workaround to set it to ON. Just set it to on in ST. Since the toolkit settings are shared between ST and MT, next time you run MT Turbo will be on and it will not crash.

[Gorn_GER]

Am 17.10.2023 um 13:25 schrieb Dogmanbird:

Will be keen to hear what you think. I had a Q1 for about 7 months 

One of the 512gb models arrived today, so just starting to give her a go. So far I do see more screen door, the amount being somewhere between quest pro and reverb g2. Fov maybe slightly bigger than a faceplate-less reverb g2. i use thin pu padding directly attached to the g2 housing without any frame. My eyelashes almost touch the lenses  

So, my Quest 3 arrived and I have some what mixed feelings at the moment. The Lenses are fantastic and Quest standalone games work perfect (a little too less Batterie playtime but okay)

Now it comes to DCS and if I did nothing wrong with my Link setup, i am very disappointed with Quest 3 and DCS. 

While the HP Reverb G2 has a way too small sweetspot, but looks overall very shape and beautiful when you look at it, the quest3+link has washed out colors (everything seems a bit gray) and there is edge flimmering that i do not have with HP Reverb G2. 

 

I very hope that I have wrong settings and this will all be better when I fix it but at the moment, I favor to use my HP Reverb G2. 

[sze5003]

So, my Quest 3 arrived and I have some what mixed feelings at the moment. The Lenses are fantastic and Quest standalone games work perfect (a little too less Batterie playtime but okay)
Now it comes to DCS and if I did nothing wrong with my Link setup, i am very disappointed with Quest 3 and DCS. 
While the HP Reverb G2 has a way too small sweetspot, but looks overall very shape and beautiful when you look at it, the quest3+link has washed out colors (everything seems a bit gray) and there is edge flimmering that i do not have with HP Reverb G2. 
 
I very hope that I have wrong settings and this will all be better when I fix it but at the moment, I favor to use my HP Reverb G2. 

The quest 3 does not have the same color pallete as the quest pro so colors will be more muted. You definitely will need to change settings in the oculus debug tool.

Increase the encode bitrate depending on your specs, enable link sharpening to see if it helps with the colors..this is for when connected to link cable.

Try different encode bitrate and increase the resolution all the way to the max in oculus home. It will be a trial and error until it looks and performs the way you want.

[Snuten]

6 hours ago, samplethief said:

Yep give it a try and ill be interested to know if it worked for you too.

I believe I just moved the install directory in steam. So try that. (or manually copy them i guess)

I dont think this fix is very widely known. I searched high and wide for it and stumbled across one thread somewhere. When i mentioned it to somebody else, they just laughed and said I was crazy haha

 

So, I gave it a try.. And true that!  By running DCS(just copy and pasted the whole docs folder into my Sata SSD and created a new shortcut with --force_openXR and stuff) with a Sata SSD it worked, when I turned Turbo Mode on all the stutter was gone! THANKS a millions times!   Is this common known you think? I mean if others had the stutter problems with NVME discs? 

Now I have also tweaked and tweaked. So far Im at 1.5 in Oculus resolution. 800 in bitrate(no sound cutouts), Link Sharpening Quality, Distortion= Low. And in DCS I have medium vis. range. Textures to high on both. Selected DLAA, then I selected DLSS and some sharpening. And DCS DP at 1.4. And it runs in 72fps almost everywhere except Marinas(must be some optimization problems on that map).  Super happy, virtually no shimmer at all with DLSS/DLAA. It do have a look of "water color-filter" though, as I always thought DLSS looked like. But the stability of the image is awesome, thanks to your suggestion about the Sata SDD I would never been able to utilize my 4090  I think Im at the edge of the card, since I tweaked the fixed fovetated render notch lower as well to achieve a stable 72fps. But damn the Sata SDD was slow, compared to the NVME disc. Did't know that DCS loaded in textures blurred an din steps with the NVME disc. But totally worth it! Thanks again! 

 

Tomorrow Im gonna see if I can set Ocuclus PD to 1.0 and increase the DCS PD more.

Edited October 20, 2023 by Snuten

[samplethief]

2 hours ago, Snuten said:

So, I gave it a try.. And true that!  By running DCS(just copy and pasted the whole docs folder into my Sata SSD and created a new shortcut with --force_openXR and stuff) with a Sata SSD it worked, when I turned Turbo Mode on all the stutter was gone! THANKS a millions times!   Is this common known you think? I mean if others had the stutter problems with NVME discs? 

Now I have also tweaked and tweaked. So far Im at 1.5 in Oculus resolution. 800 in bitrate(no sound cutouts), Link Sharpening Quality, Distortion= Low. And in DCS I have medium vis. range. Textures to high on both. Selected DLAA, then I selected DLSS and some sharpening. And DCS DP at 1.4. And it runs in 72fps almost everywhere except Marinas(must be some optimization problems on that map).  Super happy, virtually no shimmer at all with DLSS/DLAA. It do have a look of "water color-filter" though, as I always thought DLSS looked like. But the stability of the image is awesome, thanks to your suggestion about the Sata SDD I would never been able to utilize my 4090  I think Im at the edge of the card, since I tweaked the fixed fovetated render notch lower as well to achieve a stable 72fps. But damn the Sata SDD was slow, compared to the NVME disc. Did't know that DCS loaded in textures blurred an din steps with the NVME disc. But totally worth it! Thanks again! 

 

Tomorrow Im gonna see if I can set Ocuclus PD to 1.0 and increase the DCS PD more.

 

Hahaaaaaaa awesome. So glad it worked for you.

 

No it seems this isn't that widely known. As I say, I mentioned it before on Reddit and then had some nerds reel off all these stats about nvme Vs SSD and why I AM WRONG. 

Of course I know that an nvme SHOULD be better but this is DCS after all...

I am too really enjoying DCS VR with the quest 3. I have a 4070ti and have managed to tune it to a nice balance of performance and visuals using quest link. I can only imagine how awesome it looks on a 4090.

 

[Dogmanbird]

Thanks for the tips above. 

Next battle is to get multiplayer to run smoothly so will give them a try for that

[Hoirtel]

8 hours ago, Snuten said:

So, I gave it a try.. And true that!  By running DCS(just copy and pasted the whole docs folder into my Sata SSD and created a new shortcut with --force_openXR and stuff) with a Sata SSD it worked, when I turned Turbo Mode on all the stutter was gone! THANKS a millions times!   Is this common known you think? I mean if others had the stutter problems with NVME discs? 

Now I have also tweaked and tweaked. So far Im at 1.5 in Oculus resolution. 800 in bitrate(no sound cutouts), Link Sharpening Quality, Distortion= Low. And in DCS I have medium vis. range. Textures to high on both. Selected DLAA, then I selected DLSS and some sharpening. And DCS DP at 1.4. And it runs in 72fps almost everywhere except Marinas(must be some optimization problems on that map).  Super happy, virtually no shimmer at all with DLSS/DLAA. It do have a look of "water color-filter" though, as I always thought DLSS looked like. But the stability of the image is awesome, thanks to your suggestion about the Sata SDD I would never been able to utilize my 4090  I think Im at the edge of the card, since I tweaked the fixed fovetated render notch lower as well to achieve a stable 72fps. But damn the Sata SDD was slow, compared to the NVME disc. Did't know that DCS loaded in textures blurred an din steps with the NVME disc. But totally worth it! Thanks again! 

 

Tomorrow Im gonna see if I can set Ocuclus PD to 1.0 and increase the DCS PD more.

 

Out of interest did you go from your system drive (c) nvme to an additional data SSD, or were they perhaps both additional drives. Just wondering what this might be I have DCS on gen4 NvME SSD and while it's not a stutter fest, it could be smoother. 

[Snuten]

1 hour ago, Hoirtel said:

Out of interest did you go from your system drive (c) nvme to an additional data SSD, or were they perhaps both additional drives. Just wondering what this might be I have DCS on gen4 NvME SSD and while it's not a stutter fest, it could be smoother. 

No, I have one dedicated Nvme for windows only, then I have/had one dedicated Nvme for DCS, so not from C System drive. Then I also have 2 older 1TB Samsung Sata SSD's installed. So I just moved it to one of those.

Im thinking it has something to do with (not an expert) bandwidth/PCIe/Nvidia/Windows/DCS multithreading . Now when running on the Sata instead, there is absolutely zero stutter. And if there is, it is because of framedrop/performance as I also can see in the FPS counter.  Super-smooth and sharp!

I have Gen 4 PCIe as well (and PCIe Gen 5 Ready MB)

And BTW, I had DCS on the same NvME disc on my older system(i9 900K + 3090) as well. So I guess I did not have to upgrade it if I knew this. But now I have a 4090 and a faster CPU  

Edited October 21, 2023 by Snuten

[falcon_120]

So, my Quest 3 arrived and I have some what mixed feelings at the moment. The Lenses are fantastic and Quest standalone games work perfect (a little too less Batterie playtime but okay)
Now it comes to DCS and if I did nothing wrong with my Link setup, i am very disappointed with Quest 3 and DCS. 
While the HP Reverb G2 has a way too small sweetspot, but looks overall very shape and beautiful when you look at it, the quest3+link has washed out colors (everything seems a bit gray) and there is edge flimmering that i do not have with HP Reverb G2. 
 
I very hope that I have wrong settings and this will all be better when I fix it but at the moment, I favor to use my HP Reverb G2. 

I think you need to keep trying different settings. Just received my quest 3, 2 days ago. After some testing and tweaking and going back to my G2 I've decided i cannot stand my G2 anymore, everything is blurry outside the sweetspot and much worse vertical FOV.

For me using DLAA abd increasing the resolution with oxtoolkit, along with increasing colours and saturation on OXTK has increase a lot the image quality.

Ive taken out the FSR at 0.8 that i used through OXTK as that made the image a bit washed out.

IDK I just felt in love with the edge to edge clarity abd how well ASW works, almost no ghosting in the wingtips or helicopter blades compared to MR.

Enviado desde mi ELE-L29 mediante Tapatalk

[Dogmanbird]

On 10/21/2023 at 10:20 AM, Dogmanbird said:

Thanks for the tips above. 

Next battle is to get multiplayer to run smoothly so will give them a try for that

The OXRTK turbo mode did the trick - thank you for the heads up on that. At 30Hz ASW, it's even beautifully smooth in multiplayer! 

If anyone else has issues turning turbo mode on and it causing DCS to freeze/crash, uninstalling / reinstalling OXRTK might fix it for you as it has for me.  

Now my gripe is for the VR controllers no longer working since the update. I was really enjoying using the hand tracking emulation to do everything

Unfortunately with all this setup needed for Q3, it seems the game controller latency is nearly double what is experienced when using the reverb g2 

edit..... re: OXRTK with turbo turned on - in MT mode, the game won't start unless the headset is awake. If the Q3 screens are off, dcs will pause at a black screen and a rotating hourglass for me. I need to put my finger over the sensor if not wearing it at the time of launching the game. Same for removing the headset and it sleeping. I'm guessing it's because of the timing messages being blocked? Semi opaque tape covering the sensor keeps it awake

Edited October 22, 2023 by Dogmanbird

[Dogmanbird]

19 hours ago, Gorn_GER said:

the quest3+link has washed out colors (everything seems a bit gray) and there is edge flimmering that i do not have with HP Reverb G2. 

 

try running the drivers that are included in the occulus support folder. I think this cured my overexposure / washed out appearance (not sure why)

Use turbo mode in the OXRTK

Set ASW to 30Hz. I posted a batch file to activate it little back in this thread.

in dcs multi thread mode, use DLAA for antialiasing

turn the in-game pixel density setting up as far as you can (or use OXRTK res override or debugtool pixel density - all achieve the same result for me). Test performance in marianas map. If you get it running smoothly there, you'll probably be smooth in all the other maps. 

good luck  

Edited October 21, 2023 by Dogmanbird

[alip]

I got a Quest 3 a couple of days ago, and I am new to DCS VR. I am rather lost in with all these settings...

I have a 3080 12gb, so far the best experience I've had is attempting to reach a constant 72 fps with ASW off and medium/low DCS settings with DCS pixel density set at around 1.4. This has given me a mostly smooth experience and acceptable image clarity in non demanding missions.

Headset set at 72hz and render resolution 1.0 in oculus app. In the debug tool I have ASW disabled. I am using this link cable. 

I have the OpenXR toolkit installed but have not found any success fiddling with that.

Using windows 11 and DCS MT version.

So, am I completely off base with this strategy? Should I be using ASW and targeting a lower frame rate?

I also have a strange issue of seemingly random severe stuttering and freezing up, especially in the DCS main menu with an hourglass visible, any ideas what might be causing that?

My latest settings are attached.

 

 

Edited October 22, 2023 by alip