Quest 2, 6900xt, 5800x3d , Stuttering with ASW (Tray Tool) is worse than two years ago.

[RoboHackfeld]

Hello friends,

I just came back to DCS VR after a break of about 2 years. Last time I was able to run DCS with my Quest 2 and my 6900XT/5800x3D Setup well at 40 fps (ASW 45 On nonforced) and it was a nice experience. It ran smooth without any jittering at Map Objects like buildings, bridges and trees. Only I had those ghosting effect with other Tanks, Jets and ships. 

 

Now I just installed DCS used the same settings and everything is jittering when I turn on ASW. 

 

It only runs smooth if I turn down the settings so I hit the native Frame Rate and turn off ASW but even If I turn on ASW when reaching native fps its jittering.

Did anything change during the last 24 months? I can see there is no Update for the Tray Tool since than so I thought maybe there is an alternative today for Quest Users or do you guys still run DCS without SteamVR with the Tray Tool doing the magic? 

Best regards

Robin

[Qcumber]

4 hours ago, RoboHackfeld said:

Hello friends,

I just came back to DCS VR after a break of about 2 years. Last time I was able to run DCS with my Quest 2 and my 6900XT/5800x3D Setup well at 40 fps (ASW 45 On nonforced) and it was a nice experience. It ran smooth without any jittering at Map Objects like buildings, bridges and trees. Only I had those ghosting effect with other Tanks, Jets and ships. 

 

Now I just installed DCS used the same settings and everything is jittering when I turn on ASW. 

 

It only runs smooth if I turn down the settings so I hit the native Frame Rate and turn off ASW but even If I turn on ASW when reaching native fps its jittering.

Did anything change during the last 24 months? I can see there is no Update for the Tray Tool since than so I thought maybe there is an alternative today for Quest Users or do you guys still run DCS without SteamVR with the Tray Tool doing the magic? 

Best regards

Robin

A lot has changed in 2 years. Too much to summarize here. I would advise going back to basics on your setup. Make sure DCS is clean with no mods. Just use meta link and OTT/ODT to set super sampling. DCS runs via open XR API now via meta link runtime. 

[RoboHackfeld]

Hmm okay, so I think I did everything possible to improve the VR Settings.

The problem ist, back than I was able to get a nice VR Experience when I was hitting minimum 40 FPS. With that 40 fps and activated ASW it was very clear and crisp. Now I have to reach at minimum 72 fps to match the lowest native Framerate of the Quest 2. To get this FPS I have to turn FSR to 0,5 Quality what is okay but not as close to what I got two years ago. 

Anything else to change? Is it possible to make some changes with open XR? I naver used it. 

[Simo]

OXR Tookit might be worth a go - it's Turbo Mode setting instantly eliminated a lot of stutters for me (including with ASW on).

Worth noting it is no longer developer supported - works now, but may break in the future.

[sleighzy]

Might be worth trying Quad Views. You can install Quad-Views-Foveated (https://github.com/mbucchia/Quad-Views-Foveated) and then tick the Quad Views box in DCS under the VR tab. This is somewhat of a replacement of some of the functionality from the OpenXR Toolkit which is no longer supported. Turbo mode is enabled by default. For non-eye tracked headsets it uses fixed foveated rendering and will display a lower resolution image around the periphery with an adjustable multiplier for the main focal area. The focal area can be increased or decreased.

This will increase load on the CPU (and remove some from your GPU) but with your 5800x3D you’ll be fine.

if you don’t like it then just untick the Quad Views box in DCS and remove it. 

[RoboHackfeld]

So I tried the OXR Toolkit. The Turbo Mode gives me a couple of FPS, thats fine but it does not help with the Objects thet are doubled. 

 

In this thread, there was someone some years ago, who had the same issue and I commented it and got a solution what does not help me anymore. IT seems like there is no difference between ASW 45 forced and ASW 45

 

Edited November 7, 2024 by RoboHackfeld

[Rifter]

On 11/6/2024 at 12:33 PM, RoboHackfeld said:

Now I just installed DCS used the same settings and everything is jittering when I turn on ASW.

You may have fallen victim to the latest DCS version's MT-only approach. Certain (individual) hardware configurations have problems with MT along with ASW. And that has absolutely nothing to do with the performance of your hardware (or your settings).

It has to do with the fact that ED's MT approach leads to negative side effects due to synchronization mechanisms (principle-related), which unfortunately only become visible in very specific configurations.
There is no solution. ED will not make any effort because of a few percent of affected users. I have the same problem. Therefore, I stayed on the last ST version until I decided which VR system I want to continue with in the future.

[RoboHackfeld]

So Should I give it a try, to run the ST Version of the DCS.exe or should i completely go back from beta? 

 

Yesterday I came back from vacation and started DCS via VD. The thing in VD is, the SSW Feature does work very good and gives me exactly what ASW gave me in the past. The Problem with VD is, I can not adjust the FOV to get more FPS so get a steady 40fps solution with good visuals.

Edited November 19, 2024 by RoboHackfeld

[Phantom711]

vor 8 Minuten schrieb RoboHackfeld:

 

So Should I give it a try, to run the ST Version of the DCS.exe or should i completely go back from beta?

 

There is no ST version anymore. It was abandoned a couple of weeks ago. Both DCS.exe in the bin as well as the bin-mt folder currently do the same thing as far as I know.

From my experience ASW is noticably superior to SSW with regards to image quality. But YMMV…

I believe you could use OpenXR toolkit to reduce the displayed FOV. Before advised that OXR toolkit might introduce it‘s own problems since it is no longer supported (it might just as well work absolutely flawlessly also).

[RoboHackfeld]

vor 8 Minuten schrieb Phantom711:

I believe you could use OpenXR toolkit to reduce the displayed FOV. Before advised that OXR toolkit might introduce it‘s own problems since it is no longer supported (it might just as well work absolutely flawlessly also).

Yeah I've already tried that but it seems, it only puts black bars on the edges and the pixels behind are still rendered because it does not gove a performance boost even on 50%.

[RoboHackfeld]

Now I think I've found a compromise between Quest Link and Quad-Views-Foveated, @sleighzy mentioned earlier. I get a stable 72fps and deal with it until I get a 5080 or something like that next year.