Search the Community

I started this topic to track and discuss challenges with getting the best performance out of the system. I usually test each setting a couple of times. 27-1-2025 Nvidia 571.96 DLSS 4.0 Installed the new drivers. 25-1-2025 Adjusted GPU Overclock Increased CPU PBO Scalar and reduced some of the GPU overclock to further increase fps and frametimes. Time will tell if it also stays stable on the MP-servers. 18-1-2025 Clean W10 Complete reinstall of W10 returned another 5fps and better frametimes. Over the years the system got bloated with all sorts of traces from old hardware that I upgraded (2x GPU and CPU) and software that I tried and not fully removed. The system is snappy and clean again! I considered W11, but there are too many bad stories out there, no clear advantage for AMD and GUI modifications with taskbar etc W10 is easier. The only thing I still notice is that it seems that when I hit the FPS limit some sort of trouble in FPS and frametimes appears. When I stay a bit below 90, like 88fps, it is more stable. 27-12-2024 Current Overclock settings 64GB ----- EXPO: ON (timings default as stated on the DIMMS) 9800X3D ----- Turbo Game Mode: ON PBO: +200 Curve Optimizer: -20, FCLK Infinity Fabric: 2200 UCLK DIV1 Mode: UCLK=MEMCLK, SCALAR 10X 4090 ----- Core Voltage: +100 Core Clock: +120Mhz Memory Clock: +900Mhz, Fan: Power Limit 133%, Temp Limit 84. This GPU overclock is stable and gives me 4-5 extra FPS, even when i am CPU bound. My setup Windows 10 - latest version - Windows 11 will not happen until I will get serious latency advantages. Motherboard: ROG STRIX X870E-E Gaming WIFI Systemboard VR Headset: Varjo Aero SSD for DCS and Windows, separated DCS Settings Most are set to the max. SSS, Secondary Shadows, SSAO, SSLR are disabled; they do not bring much visually. Visibility Range Extreme. I have Visible Range set to High. Increasing this further is not bringing much visual improvement and really takes away performance. MSAA Mask Size 0.42 is my sweetspot. Testing Setup and approach My Windows has been heavily tweaked and optimized and I am currently still running the same Windows I started with 5 years ago. I upgraded my systemboard, CPU and GPU a couple of times but did not reinstall Windows. I think at certain moments in the past I even went too far with tweaking and should have dialed back and better register what I was doing. So a clean install will be somewhere in the near future because I am certain I have left quite some performance on the table. For the basic quick test of setting adjustments or hardware/software updates I start a the default A-10C mission Runway Startup on the Marianas Map. I use Marianas because this mission is quite demanding and quite stable almost from the start with AI not doing much. I let it run a couple of times for 20 seconds and track the performance with CapFrameX to calculate the average FPS, 1% and 0.2% lows of the runs. Many other missions give me 90FPS, so adjusting settings with such missions will not give me noticeable visible differences. If I want to visually see the performance I open up the the FPS overlay inside DCS. I sometimes also open up the new XRFrameTools application to visualize my frametimes. Once a setting looks pretty okay I log into our Wing's Multiplayer server, startup OBS recording and give it a spin to see how it goes. I usually get 90FPS flat in this setup, while running OBS recording. Testing log From now on I will start adding my complete testing logs to this main posting. Where relevant I will add charts to visualize the difference between certain options. Certain tests were eye-openers. It was/is a dreadful process going through all the settings and quite a few settings were insignificant in my case. Frame Times, average FPS, 1% and 0.2% Lows My main goal is to find the ones that will bring more stability (reduction of intrusive stutters) and performance (increase of FPS/frametimes). Sometimes it is like searching for a needle in a haystack. Seeing the settings that made a difference might bring quick wins to others as well. Overall the average FPS is not improving that much by all the tweaking, it is easy though to screw up your system and reduce FPS. But once the FPS are pretty decent it is hard to get substantial improvements. My biggest wins are with the 1% and 0.2% lows, reducing these give a much better overall experience than to have 1-2 more average FPS. The overall FPS can be high, but when you have a few microstutters here and there it is very annoying and for me breaks the immersion in VR. Caution Please be careful, not all what works for me might work for you. Do everything at your own risk. I had some crashes, especially with the overclocking, so always make backups and restore points. I also don't have my overclock software start automatically anymore when tweaking, because that also caused an issue once causing me to keep rebooting into a crashing configuration. null null null

Hey there, today I tried the new Somnium VR-1 in DCS using their OpenXR runtime. i got extreme bad performance and heavy spiking frametimes. Also the Ingrame FPS overlay was totally off to the DCS FPS limiter or the VR-1 build in FPS counter. in steamVR everything is just fine. maybe some OpenXR experts can have a look at the log file. dcslogfile.log

* EDIT 2/21/2023 - SOLVED - needed to update OpenXR Toolkit to latest version, 1.2.4 * Hi all, After having DCS crash on multiple attempts to host or join a server, I started troubleshooting. I determined that OpenXR is no longer working, most likely due to the last round of Windows updates that came through over the last couple days. **edit** I also updated to the latest Nvidia drivers sometime this week, when they released. OpenXR still works with OpenComposite, and SteamVR still works fine, but DCS crashes while loading the mission every time if I use native OpenXR with my shortcut. I had been using native ever since it was announced, so my shortcut is not the issue. I also repaired DCS (open beta), I use no mods and have none installed, and I of course restarted my system, to no avail. After successfully loading into a mission with SteamVR, I tried native OPenXR again, and it crashed. I then tried OpenComposite and successfully loaded in, then tried native OpenXR again and it crashed. I run Windows 11, and I can provide any other information if any is needed. Good luck, and thanks as always for all the hard work!

I have been testing my VR configuration/stability & visual improvements with my Pimax5k Super HMD since DCS provided OpenXR support. At first, tests where KO and could hardly just get to the flight phase. But a recent break through has occurred and has changed the testing results by 180 degrees for the better. The big game changer happened yesterday when I found out that the OpenXR Toolkit was revised to v1.2.4. to improve usability with DCS OpenXR implementation, see note 1. I will spare you the testing details and jump directly to some results/configurations that work for me. Hardware configuration: (if you wish to compare, here are my PC details) Mobo: MSI X570-A PRO/PCIe 4 CPU: AMD RYZEN 9 3900X (12 CORE) GPU: EVGA-RTX 3080Ti RAM: DDR4-32 GB (3200MHZ wt XMP) HMD: PIMAX-5K SUPER Software configuration: DCS World Open Beta v 2.8.2.35759 (latest as of 3 FEB 2023 & wt OpenXR support) PiTool v1.0.1.284v - Version 284 is required as per PimaxXR requirements. See note 1. PimaxXR v0.3.0 - This app is the runtime required for OpenXR to work with PiTool and to bypass SteamVR. PimaxXR runtime is needed to avoid PiTool kick starting SteamVR by default. Install PimaxXR and make sure that PimaxXR is selected as the OpenXR runtime. See note 2. OpenXR Toolkit v1.2.4 – Latest version as of 2 FEB 2023. See note 3. OpenXR Explorer v1.4 - Optional application to analyze OpenXR runtimes & OpenXR Toolkit app that is installed. Not required for success in implementing OpenXR with DCS. See note 4. OpenComposite - This application and its DLL implementation into DCS is not required for success in implementing OpenXR with DCS. However, you may need it for other VR games or simulators that are designed to use the SteamVR app to run them in VR. See note 6. Recommendations: Always make sure that the PiTool app is UP and running regardless of what VR runtime (SteamVR or OpenXR) you use. Otherwise, your Pimax HMD is not available for your VR sessions. If you have configured a DCS game start icon in PiTool and wish to test OpenXR runtime, avoid using that game start icon. Starting DCS from the PiTool/My games/DCS icon will kick start SteamVR. Having DCS started via SteamVR while OpenXR is configure for the game will likely cause undesired results. If you are going to run or test DCS OpenXR VR method (bypassing SteamVR), for safety, just delete the game start icon in PiTool as you will not really need it anymore. Instead, do the following… Exploit the DCS command line features to start the simulator as these will be useful to you. Make yourself some DCS game start window shortcuts to facilitate things. Here are some windows shortcut command line targets that I use. Make a DCS game start shortcut for each of the following shortcut targets & see note 5 for other DCS post link; "your game install path\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_OpenXR - to start DCS with OpenXR support. Make sure that SteamVR is not running. Make sure that OpenXR Toolkit is enabled. At first, use the default Toolkit shortcuts. Also, make sure that active OpenXR runtime is ticked back to OpenXR within the PimaxXR app. This will enable bypassing SteamVR and will avoid SteamVR from being called. "your game install path\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_SteamVR - to start DCS with SteamVR support. If you revert back to using SteamVR, make sure that the OpenXR Toolkit is disabled (tick the disable switch in OpenXR Toolkit) and that active OpenXR runtime is ticked back to STEAMVR within the PimaxXR app (start PimaxXR app and select SteamVR as the runtime). "your game install path\DCS World OpenBeta\bin\DCS.exe" --force_disable_VR – to start DCS without VR so that DCS displays on your primary display screen. This could useful for HOTAS configuration, etc. Without guaranties, this methodology should work for Pimax4k, 5k or 8k HMD owners. Can all these pieces of software & apps co-exist at the same time on your PC. YES, however, configuring the apps correctly is required if you wish to use DCS with SteamVR or with OpenXR. See comments above depending on the shortcut command lines that you are using to start the DCS simulator. You need to experiment with the OpenXR Toolkit settings. Do that using the Toolkit shortcuts while in the game. Settings will likely vary if you have a Pimax4k, 5k or 8k HMD. When your satisfied with your Toolkit settings, share them with the community by writing your own post. Using OpenXR... Generally speaking, I am getting better control of my FPS frame rates, better control of color effects and better control of sharpness inside the cockpits. Since using PimaxXR v0.3.1, stuttering when switching from F1 to F10 and back to F1 views has disappeared. Use OpenXR Toolkit to experiment with OpenXR setting while in the simulator. Use default OpenXR Toolkit shortcut combos to facilitate your setups. So far, multiplayer seems OK. Hope this helps you enjoy OpenXR with your Pimax HMD. Everest…Out! Notes: 1- For PiTool v1.0.1.284v, see https://community.openmr.com/t/pitool-1-0-1-284v/39823 Version 284v is not available for download from Pimax Support site. select the supplied link to Pimax's OpenMR community to get PiTool v1.0.1.284v. 2- For PimaxXR v0.3.0, see https://github.com/mbucchia/Pimax-OpenXR A new (unreleased as of 8 FEB 2023) version of PimaxXR is available, V0.3.1. See the following forum post to download a pre-release version of PimaxXR v0.3.1. GO TO FORUM POST LINK 3- For OpenXR Toolkit v1.2.4., see https://mbucchia.github.io/OpenXR-Toolkit/ 4- For OpenXR Explorer v1.4, see https://github.com/maluoi/openxr-explorer/releases/tag/v1.4 Be aware that this app is not required for OpenXR implementation with DCS. It is included here as reference only and is recommended for folks that do application development work. 5- For DCS news letter regarding OpenXR implementation, see the following forum post: https://forum.dcs.world/topic/318004-dcs-now-supports-openxr-natively/ 6- For OpenComposite & OpenComposite switcher, see https://mbucchia.github.io/OpenXR-Toolkit/opencomposite.html Note that no revision is mentioned for OpenComposite probably because this is actually a DLL which did the work of throwing DCS VR runtimes to PimaxXR before introduction/support of OpenXR in DCS. OpenComposite solution is no longer required to operate OpenXR in DCS.

Any chance in a future update we could get a checkbox to toggle OpenXR from within the game, rather than needing a command line argument?

I have been testing my VR configuration/stability & visual improvements with my Pimax5k Super HMD since DCS provided OpenXR support. At first, tests where KO and could hardly just get to the flight phase. But a recent break through has occurred and has changed the testing results by 180 degrees for the better. The big game changer happened yesterday when I found out that the OpenXR Toolkit was revised to v1.2.4. to improve usability with DCS OpenXR implementation, see note 1. I will spare you the testing details and jump directly to some results/configurations that work for me. Hardware configuration: (if you wish to compare, here are my PC details) Mobo: MSI X570-A PRO/PCIe 4 CPU: AMD RYZEN 9 3900X (12 CORE) GPU: EVGA-RTX 3080Ti RAM: DDR4-32 GB (3200MHZ wt XMP) HMD: PIMAX-5K SUPER Software configuration: DCS World Open Beta v 2.8.2.35759 (latest as of 3 FEB 2023 & wt OpenXR support) PiTool v1.0.1.284v - Version 284 is required as per PimaxXR requirements. See note 1. PimaxXR v0.3.0 - This app is the runtime required for OpenXR to work with PiTool and to bypass SteamVR. PimaxXR runtime is needed to avoid PiTool kick starting SteamVR by default. Install PimaxXR and make sure that PimaxXR is selected as the OpenXR runtime. See note 2. OpenXR Toolkit v1.2.4 – Latest version as of 2 FEB 2023. See note 3. OpenXR Explorer v1.4 - Optional application to analyze OpenXR runtimes & OpenXR Toolkit app that is installed. Not required for success in implementing OpenXR with DCS. See note 4. OpenComposite - This application and its DLL implementation into DCS is not required for success in implementing OpenXR with DCS. However, you may need it for other VR games or simulators that are designed to use the SteamVR app to run them in VR. See note 6. Recommendations: Always make sure that the PiTool app is UP and running regardless of what VR runtime (SteamVR or OpenXR) you use. Otherwise, your Pimax HMD is not available for your VR sessions. If you have configured a DCS game start icon in PiTool and wish to test OpenXR runtime, avoid using that game start icon. Starting DCS from the PiTool/My games/DCS icon will kick start SteamVR. Having DCS started via SteamVR while OpenXR is configure for the game will likely cause undesired results. If you are going to run or test DCS OpenXR VR method (bypassing SteamVR), for safety, just delete the game start icon in PiTool as you will not really need it anymore. Instead, do the following… Exploit the DCS command line features to start the simulator as these will be useful to you. Make yourself some DCS game start window shortcuts to facilitate things. Here are some windows shortcut command line targets that I use. Make a DCS game start shortcut for each of the following shortcut targets & see note 5 for other DCS post link; "your game install path\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_OpenXR - to start DCS with OpenXR support. Make sure that SteamVR is not running. Make sure that OpenXR Toolkit is enabled. At first, use the default Toolkit shortcuts. Also, make sure that active OpenXR runtime is ticked back to OpenXR within the PimaxXR app. This will enable bypassing SteamVR and will avoid SteamVR from being called. "your game install path\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_SteamVR - to start DCS with SteamVR support. If you revert back to using SteamVR, make sure that the OpenXR Toolkit is disabled (tick the disable switch in OpenXR Toolkit) and that active OpenXR runtime is ticked back to STEAMVR within the PimaxXR app (start PimaxXR app and select SteamVR as the runtime). "your game install path\DCS World OpenBeta\bin\DCS.exe" --force_disable_VR – to start DCS without VR so that DCS displays on your primary display screen. This could useful for HOTAS configuration, etc. Without guaranties, this methodology should work for Pimax4k, 5k or 8k HMD owners. Can all these pieces of software & apps co-exist at the same time on your PC. YES, however, configuring the apps correctly is required if you wish to use DCS with SteamVR or with OpenXR. See comments above depending on the shortcut command lines that you are using to start the DCS simulator. You need to experiment with the OpenXR Toolkit settings. Do that using the Toolkit shortcuts while in the game. Settings will likely vary if you have a Pimax4k, 5k or 8k HMD. When your satisfied with your Toolkit settings, share them with the community by writing your own post. Using OpenXR... Generally speaking, I am getting better control of my FPS frame rates, better control of color effects and better control of sharpness inside the cockpits. I do experience a bit of stuttering when switching from F1 to F10 and back to F1 views...not sure what would cause that. So far, multiplayer seems OK. Could the experience be better...YES. Correcting the stuttering when changing views needs to be addressed but I am not sure to who I should shot the requests ...to DCS regarding their OpenXR implementation, to the PimaxXR folks dev team or to OpenXR Toolkit dev team...don't know! Hope this helps you enjoy OpenXR with your Pimax HMD. Everest…Out! Notes: 1- For PiTool v1.0.1.284v, see https://community.openmr.com/t/pitool-1-0-1-284v/39823 2- For PimaxXR v0.3.0, see https://github.com/mbucchia/Pimax-OpenXR 3- For OpenXR Toolkit v1.2.4., see https://mbucchia.github.io/OpenXR-Toolkit/ 4- For OpenXR Explorer v1.4, see https://github.com/maluoi/openxr-explorer/releases/tag/v1.4 Be aware that this app is not required for OpenXR implementation with DCS. It is included here as reference only and is recommended for folks that do application development work. 5- For DCS news letter regarding OpenXR implementation, see the following forum post: https://forum.dcs.world/topic/318004-dcs-now-supports-openxr-natively/ 6- For OpenComposite & OpenComposite switcher, see https://mbucchia.github.io/OpenXR-Toolkit/opencomposite.html Note that no revision is mentioned for OpenComposite probably because this is actually a DLL which did the work of throwing DCS VR runtimes to PimaxXR before introduction/support of OpenXR in DCS. OpenComposite solution is no longer required to operate OpenXR in DCS. PS...If you like this post, please rate (@ top of post) or like it...

Hello forum. Since last updated and moving to OpenXR, game crash after some minutes. No matter if 2D or VR; MT or ST. I have checked logs and I cant find any pattern. I have repaired, cleaned and deleted metashaders. Version: Open Beta 2.8.4.36529.1 Hope someone can bring some light. Thanks. dcs.log-20230501-191728.zip

So im having some troubles getting dcs to open in vr mode. It will open in desktop just fine. The link below is the clossest issues I've been able to find to mine just to give an idea what I've been dealing with. https://forum.dcs.world/topic/328037-solved-open-beta-not-starting-in-openxr-when-ultraleap-gemini-software-is-installed-with-openxr-support-enabled/#comment-5238289 Attached my dcs log file for you to check out. Appreciate any info you can give me, and thanks for taking some time out of your day to give me a hand. dcs.log

This is really a two part question. And I will start with saying that my guess is the RTX 3060ti just can't pump out the frames for VR. I am getting poor fps and quality on my setup but heard OpenXR may improve performance. I just don't know if it will work with PSVR. Here are the questions: 1) Can PSVR use OpenXR? 2) If so, how? I am brand new to VR after upgrading my graphics card to a RTX 3060ti. I found a good deal on a used PSVR and figured why not give it a try. I play DCS in steam and bought the PSVR IVRY software. It is working but the picture quality is lacking. I am wondering what the issue is, if it is settings or my hardware just isn't good enough. Maybe someone can help? When playing on the monitor without VR, I am running at about 140 fps on Normandy in my P-51D at 1080P and mostly high settings. With VR on and using my PSVR I have to turn most of the settings down pretty low. With so many layers, IVRY, SteamVR, DCS, Nvidia Control Panel... I just don't know how they interact. Any help would be appreciated. Computer Specs: Windows 11, Steam, RTX 3060 ti (OC'ed), 24 GB (dual channel 8x8, 4x4), Motherboard Gigabyte Z390 Auros Elite, Intel Core i5-9600k (OC'ed), 650 Watt PSU (circa 2010), 1 TB SSD.

Issue description When attempting to start DCS Open Beta 2.8.6.41066 with the --force_enable_VR --force_OpenXR command line options of the DCS.exe, DCS starts in 2D mode and not in VR mode. This happens for both the single threaded and multithreaded versions of DCS. Furthermore, the issue occurs no matter if Windows Mixed Reality or Steam VR are used as OpenXR runtime. Skimming through the dcs.log file (see attachment), I noticed the following error related to OpenXR: 2023-06-13 09:39:09.356 ERROR VISUALIZER (Main): OpenXR exception: XrResult failure [XR_ERROR_FILE_ACCESS_ERROR] Origin: xrCreateInstance(&createInfo, &instance) Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:299 2023-06-13 09:39:09.357 INFO VISUALIZER (Main): LAUNCH IN VR ed_FakeVR: ed_FakeVR 2023-06-13 09:39:09.358 INFO VISUALIZER (Main): render thread initialization... It seems that DCS cannot access the OpenXR library file in the file system. Other OpenXR applications like the demo included with OpenXR Tools for Windows Mixed Reality work fine. When not using the --force_OpenXR command line option with the single threaded version of DCS.exe, DCS starts in VR. The system runs a fresh, clean and fully updated installation of Windows 11 Pro and the latest drivers for the installed NVIDIA RTX 3080 Ti with a HP Reverb G2 WMR headset. An Ultraleap Leap Motion Controller and the corresponding Ultraleap Gemini hand tracking software installed. Solution that worked for me: The Ultraleap Gemini hand tracking software includes an OpenXR plugin. DCS also supports the Ultraleap Leap Motion Controller and includes the corresponding library but seems to come with an outdated and/or conflicting version. So, this is how I could fix the issue: Copy this file: C:\Program Files\Ultraleap\OpenXR\LeapC.dll To the following folders and overwrite the existing LeapC.dll files there: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt After this, I could successfully launch DCS in OpenXR VR mode. dcs.log

This is in the MT branch, and only happens with steamvr. OpenXR works just fine and even if I set steamvr as the OpenXR runtime it still crashes every time. Have tried adjusting the settings including MSAA to no avail. dcs.log.old

So OpenXR is now a thing in DCS, but not the hand-tracking part. Can we get OpenXR hand-skeleton translated to the DCS's hand-skeletons? E.g. the ones leap motion and other interfaces use? This would give quest2 users much better hand tracking that even leap motion has (much wider field of view for example, no overheat and extra USB cable). E.g. a low hanging fruit of skeleton-to-skeleton interface, and given how many people own quest2 it might be worth the effort. OpenXR hand tracking interface documentation here: https://registry.khronos.org/OpenXR/specs/1.0/html/xrspec.html#XR_EXT_hand_tracking The OpenXR hand skeleton is already projectable to DCS, just being ignored by the game logic:

Recall in 2.8, if you set the OpenXR custom resolution down low to improve performance, it would introduce some pretty bad screen artifacts that no amount of AA could fix. Well, in 2.9 that has changed. Kudos to the devs for this amazing improvement! With OpenXR at 49% and DLAA I get no artifacts. I still have to test the full range, but this is huge. These shots are with my HP G2 at 60hz. Without MR enabled I was getting a solid 70fps. That makes MR a good option when you can stay above the refresh rate.

I just tried to swtich from steam vr to openxr and i got dcs to open with the vr but there is no menu. This is force opening open xr on a dcs shortcut. When I go to open dcs its just a black screen. BTW I just deleted steam vr. I have an HP reverb headset. Could anyone help me out?

I have updated this first post to try to clear up some of the chaff now that DCS supports openxr natively. The original post in it's entirety is in spoiler tags below, I have lifted portions of it for this but I wanted to retain it for archival purposes. Since writing this I have upgraded my GPU from the 3070 to the 3080ti, as such I now have a little more knowledge on higher end hardware. Similarly DCS itself has changed in the ever marching way of progression that it has habit to do so, VR performance is now currently a little slower than it was 11 months ago. This is based on my experiences and testing, specifically with my set up. It isn't an all encompassing guide and by all means feel free to add your own insights and observations First things first set some baselines of what you want to achieve, do you want: - A clear, stable picture? All the bells and whistles? All the FPS? For performance metrics use the tools built into openxr toolkit. For tuning create a test mission that has your typically heaviest passive GPU workload, I use a rooftop pass over the top of Beirut. Some naming conventions: - OXR = OpenXR (Installed with windows by default) SVR = SteamVR (Steam App) WMR4SVR = Windows Mixed Reality for SteamVR (Steam App) OXRTK = OpenXR ToolKit (Obtainable from github) OXRDT = OpenXR Developer Tools (Also known as OpenXR Tools for Windows Mixed Reality - Sourced from Microsoft App Store) MR = Motion Reprojection For detail of the functionality of the excellent OpenXR Toolkit by @mbucchia please see the features list here. A clear, stable picture? Doing the following will typically be running DCS at framerates below the headset refresh rate, as such there will be some associated ghosting/stutter. Some scenarios will be smoother than others. Within the OXRDT set resolution to 100% and disable motion reprojection. This will give the ultimate image quality but with the caveat that you have to tune DCS to keep framerates above your own personal comfort threshold for stutter (mine is 50fps). If you're struggling to get it fast enough to eliminate the stutter for your test scenario, then the first thing to do is set the resolution in the OXRDT to default, this will set the resolution based upon your VRAM quantity. The calculation is based on the size of the three backbuffers with 4xMSAA applied should be no more than 10% of total VRAM. For the reverb having a 100% resolution of around 3160 pixels wide, the 8gb 3070 defaults to around 60-65%, the 12gb 3080ti defaults to around 95%. Within the OXRTK menu you can enable foveated rendering and upscaling to gain some frames back but at the expense of some image quality. Turbo mode can subjectively claw some FPS back in certain scenarios; typically it can help you gain 10-20% when running below refresh rate. It has been found that throttling the framerate to 55fps within OXRTK produces a minor improvement in apparent object stuttering when the headset is at 90Hz. This appears to be a sweetspot that has be correlated against by several different people, it may be different for you but it's easy enough to find your personal best compromise - fly low and level with the framerate throttled to 45fps, look out of the window whilst altering the framerate throttle and when you see an reduction of object ghosting leave it there. Based on the above, if you can consistently keep >60 FPS then it is worth trying out 60Hz refresh rate. Being above the refresh rate is nirvana and is ultimately smooth with zero artifacts. A couple of caveats to bear in mind: - the reverb has an apparent refresh rate flicker in 60Hz mode than can be hard to stomach, some people can, some people can't. It may be possible to train yourself to get used to it, treat it like getting your VR legs again. A little at a time is key, build it up in short sessions over days at a time. If you FPS drops below 60 then the smoothness of the display is not a good as 90Hz when below refresh rate. Therefore you ideally need some GPU overhead available to compensate for this - I use 60Hz and work on having a typical GPU frametime of 13ms or so which equates to around 77fps. All the bells and whistles? Doing the following will typically be running DCS at framerates below the headset refresh rate, however motion reprojection will be inserting synthetic frames to make it appear to running at refresh rate and will be very smooth. Image clarity suffers slightly and visual artifacting can be distracting. Within the OXRDT set resolution to 100% and set MR to always on (don't use auto, that's for app specific configurations and not implemented for DCS as of yet). Within the OXRTK menu make sure that MR is set to unlocked. With MR enabled and unlocked, DCS is now able to smoothly display framerates from 90 all the down to 30. This is a huge range and it will allow you to run far higher settings than you would think. Your FPS will be displayed as 90, 45, 30 or 22 (I've found 22 reprojected to not be pleasant) with occasional movement a few frames either way for a second or two when it changes reprojection fraction. The further from the 90hz refresh you get the more reprojection has to pick up the slack so will introduce more artifacts. The coding behind the OXR implementation of MR is virtually identical to WMR4SVR so should behave the same. The OXR MR can reproject at fractions of the refresh rate - 1, 1/2, 1/3, 1/4. For 90hz the fraction brackets work out at approximately 11ms 90fps, 20ms 50fps, 30ms 33fps (and we'll ignore 22fps because you don't want to be here), there is a small MR overhead to account for so the numbers aren't exact. WMR4SVR can only reproject at 1/2 refresh rate, therefore below 20ms 50fps it disables itself entirely. When tuning DCS you ideally want to be aiming to keep your FPS away from the bottom end of a fraction bracket. Therefore if you're getting 18ms you will be skipping between 1/2 and 1/3 brackets, best to turn some settings up and push it down into the 1/3 bracket. MR will keep things smooth but at the expense of some warping/ghosting particularly on edges of wings/cockpit frames. The slower the relative motion between the two edges the less it will artifact. If you're suffering with watery looking distortions/artifacts then ensure that you don't have shaking reduction enabled as the two don't play nicely. If you're ok with the artifacting you can run phenomenal settings, let it sit at 30hz reprojection and be on your way, unless you're in a weaker GPU then the world is your oyster. All the FPS? Within the OXRDT set resolution to default or below and MR to disabled. Within OXRTK enable upscaling of your choice (I wouldn't recommend dropping below 75% to retain most image quality) and enable foveated rendering (you can use a preset or play with the custom settings, it doesn't make a huge difference in performance). You may well be able to achieve the 90hz refresh rate by doing this although the use of upscaling will introduce additional shimmering that you will not get rid of. It is possible to balance out portions of the above to achieve a desirable outcome; it's not gospel, play with it yourself to find your own ideal. My current settings are as follows: - Reverb @60Hz, resolution override to 3200 pixels wide, MR disabled. FFR on Quality/Wide preset, Turbo mode enabled. NIS upscaling @75% with no sharpening. With DCS settings as follows I can comfortably keep below 16ms (>60fps) on Syria on all but the heaviest of missions in which case the CPU gets swamped - the GPU is still producing frames fast enough, the CPU simply can't supply it fast enough. The multithreaded engine update should hopefully alleviate this issue moving forwards.