I suggest leaving your msfs config file at stock 1.0 and change your ODT pixel density, top item = 1.30. All other ODT settings defaults/zeros except asw = forced 45fps asw off, distortion Low, and encoding bitrate = 500mbps.
Then use dlss/balanced. Also, adding the latest dlss 3.8.10 also helps (google how to do this). You don’t really need the OpenXR Toolkit anymore imho. Just make sure your meta-link settings have the oculus runtime selected as the default OpenXR runtime.
System Specs: 7950X3D / 64GB 6000MHz RAM / 3080Ti / Samsung 970 Pro/Evo NVMe drives (1TB and 2TB) @ PCIe 3.0x 4 lanes / Single monitor - LG CX 120Hz HDTV with HDMI connection
VR Hardware: Valve Index with 3 base stations, controllers not used
VR Software: SteamVR running 150% SS at 120Hz refresh rate with motion smoothing enabled.
OpenXR toolkit running FFR at 80% inner at 1/2 resolution / 90% outer at 1/4 resolution, render mask on, forced to 40 FPS, no SS/AA.
I changed secondary scaling to 1.2 and it’s so good I’m taking a break from tweaking settings to enjoy the clarity and smooth performance of VR. I truly did not have it this good in 2020. It is almost as if I upgraded my GPU. 2-3% drop in headroom via OpenXR toolkit, and that is the momentary dips. It goes right back to the 27% headroom I had before the change.
OpenXR toolkit is the sundae and secondary scaling is the cherry on top. Props to the OP and all who contributed. You rock!
Generał comment:
If you post any results without listing the headset you are using your posts are not bringing much value, as each headset is different when it comes to resolution and driving software.
Also listing GPU/CPU is recommended.
Why this forum doesn’t have a signature feature so everyone could add specs in that, miss that.
You can change like you want, not changing the dlss preset to F it’s all peanuts and butter.
Definitely preset F with Performance or Balanced is the starting point before doing anything else. I think that goes for any headset.
I agree. DLSS performance with VRSecondaryScaling 1.5000 looks beautifull in quest 3. And there is 80% gpu load, when using SSW (45 x 2 = 90fps). I have 4090 and 7800x3d paired with quest 3 (reverse tehtering method). Latency is acceptable.
You changed the preset to F?
I haven’t gone back and tried E after Diego’s video. I may experiment and see if there is a difference in clarity or performance. I’ve just been finally enjoying the sim.
For me the image is sharper now than I can get my eyes aligned with on the Pimax Crystal. I can never get my eyes in the perfect spot on the Pimax, even with custom H/V adjustments. I have to grab the headset with my hands and hold it a certain way to get a sharper view.
Is this in 2024 ??I have the crystal but haven’t bought 2024 yet due to reports it was lacking in VR ??
No, i had F allready.
VR is decent with God like pc (4090 etc). There is bugs yes, but hope they are getting fixed in 6 months or so.
Thanks … My rig is similar to yours (7800X3D/4090) but I’m a PC dummie and will probably never be able to “tweak” as much as you guys do. I’m going to wait a bit longer before purchasing. I did read a major patch was expected soon that would help with the VR issues.
There is quite a bit of confusing info out there, but the tweaking needed isn’t that hard if you follow some of the guides. It’s mostly copying some files and running a few files.
I started 2024 with terrible performance out of the box. Then got it a little better with updating DLSS and then dialed it to great performance with clarity using the presets and Performance settings. I have most everything else on defaults.
There are some nasty VR bugs with the mouse and menus. Many of the default airplanes also didn’t fine tune the collision meshes. The collision meshes are what burns me as I doubt developers will put in the needed efforts. It shows they aren’t testing airplanes in VR. Out of all airplanes in the sim, the C172 should be the most polished airplane and it’s just not.
Does anyone have comparison shots between preset E and preset F? I am not convinced F is the way to go.
Just test it. It’s very subjective. Depends on the resolution and headset model. You will not see the difference in the through the lens photo, it’s subtle.
Glad to see I’m not alone. 
Now since you mention UserCFG.opt is there any way to get the section below back that was in 2020 usercfg.opt? It has a huge impact fix for me in 2020 which is was to set sharpen 1 to 0. it eliminated double vision and shimmering clear skies with Quest/4090. however it is back in 2024, but the section no longer exists in the new usercfg.opt
{PostProcess
Enabled 1
EyeAdaptation 1
ColorGrading 1
Sharpen 0
Can you make a bug post about it and then link that here? We can vote on it.