DLSS tweaks, openXR toolkit and performance in VR

I live in Launceston, although originally from Hobart.

I had been doing a world tour in MSFS 2020, visiting the many POIs, but so far in '24 I haven’t left Tasmania (apart from some training missions) , it really is the ideal place for GA flights with so much variety in the landscape and coastlines.
I haven’t tried gliding yet, I must do that!

Yes, I’m really hoping the upcoming patch will sort out the issues with controls and UI etc

2 Likes

I’ve somehow started to understand the controls system :sweat_smile:

In the Draco I found what I think is a bug in that the center tank control only pulls from one side. The L/R positions work fine.

I’ll have to check Tasmania out. I’m in Florida, which lacks terrain.

1 Like

Wow. Just tested this with Virtual Desktop and Quest3 and it works great. Thank you so much!

1 Like

nice video, thank you. Tried to install the DLSStweak file but my game is from the MS Store, hence I can’t access the .exe file location. Where do MS Store users place the DLSStweak file?

What magic is this? It looks just a little worse than the TAA, much, much better than the stock DLSS, how can it be that it is not included in the game, in VR it is a big difference

It’s in the Content folder. I was able to access it without issues.

I’m wondering the same thing! It’s nice we have the ability to make these tweaks at least.

Do you notice any impact on performance when using profile F vs default?

managed to get it work with my Aero, 4090. Using preset F, Performance, super sampling in the OpenXR toolkit to 5000 something. Slightly better visuals on the displays BUT massive performance gains. Thank you for sharing this!!

1 Like

Slightly better compared to what? I’m trying to work out whether profile F in itself has any performance impact, independent of the DLSS scaling.

Just in case it can help people wondering (like I was) if this applies to MSFS2020, it seems to work equally well… Just tested with Quest 3 (link cable) and latest DLSS driver (which seems to be ok despite some warning in the logs).

To be honest I was maybe expecting too much after reading all the reports here, for me the visuals are more like Quality mode (with still sensible difference from DLAA), but achieving this in Performance mode is already a very nice improvement in terms of GPU headroom :slight_smile:

2 Likes

compared to the ‘standard’ in-game DLSS Quality setting. Didn’t test other presets, only ‘F’

1 Like

And you had massive performance gains with F compared to default profiles with same scaling?

Crystal Original, 7800x3D, 4090, A2A Comanche (steam gauges)

I experimented with Performance and preset F.
Comparing with my reference setting: DLSS Quality, default preset, supersampling to 4500 x xxxx in OXRT,
DLSS Performance, preset F, supersampling to 5400 x xxxx gives me slightly better image (less shimering on the distant objects). If I go down with supersampling the FPS is slightly better than my reference DLSS Quality setting.
Not a revolutionary change, for example improvement from 36 to 39 FPS (up to 10%). So I will probably stick with Performance, preset F, 5000 x xxxx supersampling.

As usual what matters is the resolution thrown at the GPU (combination of the DLSS setting and the supersampling level), but seems like the DLSS magic works slightly better for MSFS with preset F.

Fixed Foveated Rendering in OXRT (Quality, Wide preset) gives me another 2 FPS more (5% increase).

2 Likes

Feels like some understand “preset F” as something that would improve performances per se (in terms of FPS/stutters…).

This is not the case (it could even be the contrary for a given resolution factor).

It’s rather about improving the image quality for a given resolution factor. So you can approach the image quality you would get with a “higher” preset (say “Quality” mode), while selecting a preset with a lower resolution factor (say “Performance” mode).

In the end you get better performances, but that’s not because of the preset itself, it’s because you can afford lowering the resolution while preserving good image quality.

(I think one could get the same results in any mode provided that you select the appropriate factor (like 0.5) with the appropriate preset (F). Whatever the name, “Performance” or anything else, it’s just a label for a given configuration).

4 Likes

It’s really difficult to digest people’s performance with all these differing variables… CPUs, GPUs, headsets, sim settings, aircraft etc etc. We are all comparing apples to oranges.

For those of us with Pimax Crystal OG and Light headsets and 4090’s we really need to reduce these variables by standardising our VR graphics settings, aircraft type and flying location, together with fixing other variables like live weather off and clear skies, plus whatever I have left out off the top of my head.

Maybe we also need a separate thread for Crystal users battling with DLSS tweaks. We certainly need to be using the same graphics template or a sim graphics preset so we can judge things better.

I get roughly similar results to you, even though I’m using a 5800x3D compared to your 7800x3D, but then again I don’t know your in-sim settings. Just one variable like trees set to high or medium can change things, as can altitude.

Sigh. :face_with_diagonal_mouth:

No F, mode doesn’t change performance, but it gives a sharper image at the expense of a little shimmering, so it works better for glass copits, the performance part is you can use lower dlss setting and get a sharper image.

Preset F, is what dlaa and ultra performance mode use by default, E is everything else by default and as of the latest dlss, E & F are the only two.

You guys are giving me hope, here. I’m still running 2020 waiting for good MSFS 2024 VR reports to come out. And this post is one of the more promising ones.

I have:
i914900k / 4090 / 64GB RAM and a Quest 2.

Like I said - you guys in this thread are giving me hope and maybe nudging me closer to picking up 2024 to play around with over the few weeks I will have off work around Christmas… But any other feedback would be great.

Thanks!

Works great in 2020 with TAA / DX11 at full render res (using the Oculus app and only turbo mode on with OXRTK).

I have messed with DLSS in 2020 and hated it due to the blurriness of everything inside the cockpit/flight deck. Couldn’t read instruments. So I went back to TAA and haven’t messed with things since.

In 2024, has DLSS improved to the point where instruments/gauges/text inside the flight deck is clear and readable? Any other visual degradation with DLSS and 2024?

a

One setting(s) that I can’t figure out is “sharpening” - there are so many places, especially with Virtual Desktop on my Quest3, and OXRTK, and… I would like to improve the appearance of the “outside” world wheras I am satisfied with the in -cockpit clarity. The outside scenery imagery just seems to be less satisfying. Any ideas?

This is exactly what I thought, thanks. Was a bit confused why people were making it seem like profile F increases performance per se.

Also confused why they (the programmers) don’t make F the default if it makes it look better :sweat_smile:

What exactly do these profiles even do?