Quote
Anyway, no big deal. Maybe I'm just missing something that got lost in the translation, lol!
Probably : my English is not so good
I apologize
I f you mean AFS2 probably works the same without Oculus OpenXR runtime, I agree but as I am using three different simulators including MSFS, activation of OpenXR runtime for Oculus is is recommended at least for this last one : as it does not harm AFS2 keep it activated
Quote
Hello Toorop,
i have the same PC configuration . Please can you post your settings which you have in AFS2.
Yes of course :
For extremely heavy sceneries like France VFR 's Paris Ile de France with Airport Pack I use the settings just below and get 35 fps as minimum (but smooth) even with the heaviest parts of the scenery in view. Lowering graphic settings allowed me to increase pixel density to 1,2 (but visuals are quite good too with 1 like with the "Ultra" settings below and you can get more fps).
Obviously these 35 fps are a minimum (despite playable) but on lighter parts of the scenery you get much more
Strangest thing is that 35 fps was totally unplayable in the Rift but seems pretty smooth now with the Quest 2 : the same in MSFS (no explanation at the moment)
Note : fps in the Hud and in MSFS dev mode are the same but do not use tools like Fraps : they are measuring the mirror fps and some apps like Flyinside reduce the Mirror Refresh rate so you could get very low unrealistic fps with Fraps
So, for extremely heavy sceneries :
For more "normal" sceneries (included detailed ones with good cultivation) I get constant 72 fps with these settings :
For all kinds of sceneries :
Remember : always launch in VR mode (Aerofly FS2) like this :

- In Nvidia parameters you can use VSync "Disactivated" or "Fast" (no other one)
I_ n Nvidia parameters I suggest to keep Low Latency Mode "Disactivated" but you are allowed to try changing for "Activated" or "Ultra" : did not see any significant changes in Flight Simulation
Additional infos for Oculus settings : be conscient some settings may reset to default when restarting the App. Fortunately they are not the most significant ones and you can ignore them (just to let you know...) 