Snuten

Haha And yes, perhaps it was fixed in that 2.9 patch, did't think of that

Guess what I did just now? I copied DCS install folder back to my very same NVME disc again, and now it works without stutter. Quite weird though. But Im happy since now I have decent loading times again. The Sata SSD took ages to from start DCS to cockpit with textures. (And yes, I triple checked that I'm running from the new location and MT version) It would be cool to know if this would work for you as well. And don't move the folder, just copy paste it, in case it's not working for you.

Yes it is a bit confusing, but I have found that using resolution override in OpenXR gives me better fps than just increasing the DCS PD more. And also it seems to get sharper(less blurry ) in distance by doing so. Also, I can't get more PD (SS) from the oculus app, and Oculus Debug tool resolution override don't work for me. I have increased it in OpenXR TK even more and I am now super happy. Not sure about you not getting OpenXR TK to work. Perhaps you need to force openXR via your DCS.exe shortcut?

Im doing it but just lowering the Saturation(and that works).

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]

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

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?

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

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

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

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.

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?

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.

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 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.

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)

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

I would really like to test the new AA modes. But I can't select any other than MSAA 2x/4x. And Upscaling is set to OFF, and can't change that ones options either. NEW: Anti-Aliasing. If Upscaling is set to OFF, three anti-aliasing modes are available. Multi-Sampling Anti-Aliasing (MSAA) Temporal Anti-Aliasing (TAA) Deep Learning Anti-Aliasing (DLAA) Im using the Q3 right now with Link Cable and forcing DCS with OpenXR and using OpenXR Toolkit. PD in DCS is 1.0. No scaling in the toolkit settings either. Or does the 1.5x in Oculus app count as Upscaling, and therefore not being able to use other AA modes? Does anyone know? Or is it only with the MT version it works? (7800X3D with RTX4090)

Just bought the VD. And I can't get DCS to run OpenXR with OpenX Toolkit, need foveated render and its motion projection. And running DCS via VD-> SteamVR sucks, and running DCS via "Launch game..." option in VD does not activate OpenXR Toolkit, even though I point it to my shortcut of DCS that have the --force_OpenXR thingies. And the motion projection default from VD suck big time. I get sea sick of it, the whole screen "wobbles". Or did I miss something to get it work right? Any other setting? So now Im back just using Oculus Link(cable) and using 900 in bitrate and 1.6x override resolution, looks almost as it did with godlike setting and AV1 decoding. But the AV1 decoding did look a bit better though. Running in 90hz and 45 fps with motion reprojection. RTX 4090

Do I need to have it wireless to have AV1, I have no Wifi6 And does VD replace the windows Oculus app? Or do you need to have them both running? Thanks!

Perhaps a stupid question, but are your link cable good enough and connected to USB3?

I read some info about using something with VD but never understood how and why. At first my experience was like an old VHS movie, no matter what I did. But then I came across a reddit forum that was for Quest 2. There a guy explained the settings in the oculus debug tool. And also that you could increase the bitrate by pasting in the digits rather than typing and that you could go up to 960mbit. But I think a setting that is supposed to distribute the pixels more to the center and lesser to the edges, distortion setting(don't remember what it was called, not at the computer:) ), and it should be on "low" instead of default or high. After this it looked more like a 4k movie rather than VHS. But if VD would make it even better I should give that a try. Can you explain what it is with VD that makes it better? Im using Oculus runtime and using --force_enable_VR --force_OpenXR in the DCS .exe start line. Not sure if that's the way to go though.

Yes, I think I need something like this. Thanks!

Just gonna post some thoughts about Q3. I have been using Reverb G2 since it came and liked it a lot. I always chased 45 fps since I want max resolution and clarity(I wish I could have that in 90fps though) I now have a 4090 card and could increase it even more. But I recently bought the Q3(release date) and I have now tweaked the Oculus settings to my likings. Im running it with cable and max resolution (1.6x?) @90hz and also 800 in bitrate(you need to write 800 in like notepad and copy/paste the value in the debug tool, otherwise the max value is like 600 or something), then forcing DCS to openXR and using OpenXR Toolkit with foveated render at 45 fps. At first I did not quite like the video compression feel of it. But after a while I overcome the annoyance of the "video quality" it has. I know I must say I am quite satisfied with it. And I think that is the pancake lenses+resolution+FOV. The sweet spot is everywhere. So the speed sensation is much higher since I "see" things on the sides that otherwise was out of focus because of the G2's fresnel lenses. Not sure if Im gonna replace the G2 though, need to make some more comparisons between the two. But I can say, if you have something worse than the G2, I think the Q3 is a good upgrade. The G2 is much sharper in the centre, perhaps since it is direct feed video in the G2. The biggest con is that it drains battery even though it is on my "charging" USB-C port. So I hope I'll find some USB-C cable with external power supply soon. (I know about the Pico, but not sure about the compatibility with OpenXR and how the software for tweaking is.)

I think I, most likely, found the problem! Mixed Reality OpenXR tools, I disabled "Use latest Preview OpenXR runtime" and now it is fluid again. I have always used the latest preview one here. But this time it seemed to create problems. After looking at the performance monitor I could look in one direction with my head fixed, and the GPU time could go like +25ms to -25ms up and down, like it would be a CPU on a MP server. And since I was using a single player map with nothing on it moving except trains it figured it must be something with the VR drivers or something. Normandy 2.0 is also super smooth in 30fps with Motion Projection. Now Im gonna fly the Spitfire like never before! Hope this helps others with Mixed Reality. Cheers!

Hi, I haven't been flying for a while, and I updated to the last version of Open Beta, deleted the shaders/fxo in saved games and also run a repair. I have never had GPU Bound before and I have not changed any settings. Using Opencomposite as always locked at 30 fps with motion projection. I always had enough head room for all maps(except for Marinas) and 1:1 resolution using CAS(OpenXR). Was fluid with no stutter or performance issus last time I flew. I just tested one map now, The Channel Map. Tried to lower the resolution to 85%, no difference. Have anything changed regarding the maps? Lost the interest to try other maps and I think there is no idea to even test Normandy 2 that I just bought. Sorry for sounding bitter, but really planned to fly tonight and don't wanna sit with the hassle to revert to the previous OB either. But would be happy if other have noticed this and have a solution RTX 3090, i9 9900K, Reverb G2, 32Gb, SSD, Win10, OpenComposite/OpenXR Cheers