WipeUout

I think it is more complicated than this. What airframe do you use? What map? SP or MP? Preferred scenario, bombing, dogfight? And also, what are your HMD's options/features? Making a track and re-using it for your own benchmark, in accordance with the type of flying/map/airplane you prefer, is not that complicated. You replay the track and then tweek your setting and replay. With an integrated benchmark, you would change your setting, run the benchmark, then change settings and replay benchmark. No? I think that a complete guide on all common settings (Steam, OXRTK, DCS) that is well maintained and include particulars per HMD would be far more useful. The info is out there but all over the place. Such a guide would be a time saver.

Even if you jump into VR later on, the 4080 will be more than sufficient for quite a while also. I am driving a Pimax 8kX at native resolution with my 4080 and it is glorious!

Opencomposite is not required anymore since DCS has native support for OpenXR. Opencomposite is a bridge to use OpenXR runtine with an OpenVR application. You should simply remove the mod.

Update: Menu problem reported to mbucchia on discord. PimaxXR broken but SteamVR working fine.

For haze reduction, I lower gamma slider to 1.4 and crank up backlit in the HMD. Not as efficient as 3DMigoto mod but good enough for me. Reducing glass reflection is also achievable with TAZ0004's "clear glass" trick, post here:

Although PimaxXR seems broken in menus, the performance improvement with MT is very good. I have noticed a 1.5ms decrease in CPU FT running my test track (F-18 caucasus), and also a 0.5ms decrease in GPU FT. If I turn flat shadows blurring off, the gain is even better with 2.1ms drop in CPU FT and 1.1ms drop in GPU FT. We are back to 2.7 performance and even slightly better! Running my 8kX at 60hz with no reprojection and native resolution at 4k per eye. Thanks ED, this is very nice!

Seems that PimaxXR is broken. I have tried 0.3.0 and 0.3.2 and both have the same issue: HMD tracking is screwed up in Menus. Once in the cockpit, all is good and performance is great. But, when in the menus, it wobbles like crazy. Using SteamVR has no issue, running fine. The issue has been reported on discord to @mbucchia.

Seems that PimaxXR is broken. I have tried 0.3.0 and 0.3.2 and both have the same issue: HMD tracking is screwed up in Menus. Once in the cockpit, all is good and performance is great. But, when in the menu, it wobbles like crazy. I will leave a post also in the native openXR thread.

3DMigoto already was working with OXR or SteamVR. See here for details:

You will never get as good a result as with 3DMigoto but close. You need to use CAS and apply at least 80% sharpening to start seeing acceptable result. Nowadays, I use 90% and it is just glorious in the 8kX at native resolution.

For me Reshade was useful to improve sharpness and color but with OXR, I find OXRTK providing a better way. Sharpening in OXRTK is very effective with minimal (if any) increase in GPU FT compared to Reshade costing 2-3 FPS on my system. Same with color adjustments, you can tweak this also in OXRTK. Depending on what you were using Reshade for, OXRTK may be a good and simpler alternative. 3DMigoto is also very good for sharpening and color but with higher FPS cost because of the extra features. Haze reduction is really good also in 3DMogoto but you can use the gamma slider in DCS to reduce haze a well. I use a gamma setting of 1.4 and crank up backlit in my HMD, it is surprisingly good at reducing haze.

4080, it's in my signature block. Stability mostly, it reduced stutters for me. But it is the only way to have DCS native OXR work in OB with a Pimax.

Ok, a bit of math first. You have a pixel density of 1.5, which increases your resolution by 225% but also, you reduce resolution to 60% in OXRTK. Assuming you have an 8kX, you are effectively reducing your final resolution at 90%, or 3456x1944 pixels. Set pixel density to 1, and use only OXRTK to change resolution as it will be more efficient. Unless you reduce the demand on your system further, the jitter will not go away because your GPU can't keep up with that much pixels to render. If you want to keep close to native (100%) resolution, then you will have to consider using smart smoothing or 1/2 vertical synch (smart smoothing, but always on). Which bring me to another important aspect: what is your HMD's refresh rate? My 8kX is an older model that has 60/75/90 hz refresh rate and I use the lowest. If you have the newer model, you may have 90 hz only as an option. This means that your GPU must pump 90 FPS in order to have a smooth video and with a 3080, it is too much. You need to use smart smoothing or drop the resolution considerably. The other way is to reduce DCS settings. Disabling shadows completely, clouds to low, all the AA features off and keeping all texture low will help. You can also improve performance by enabling fixed foveated rendering in OXRTK, that is what I do an the performance gain is substantial. Note that Fixed foveated rendering option in Pitool does not work in DCS, you have to use the option in OXRTK. Getting a smooth experience in DCS, no matter what is you HMD, is a balancing act that we all spend way too much time on. It is the price to pay for the most immersive VR experience. Last bit of advice, Pimax is a great HMD but it requires lots of horsepower to fully enjoy it. Save and get yourself a 4080 or 4090.

You need to provide more info, what are your settings (pitool, DCS Stable or OB, OpenXR or SteamVR, etc) and what is your hardware...

Pimax does not use HMDI, it uses display port. The HMD has to be connected through one of the GPU connector or it will not work. Usually, you have three display port connector on your GPU card.

Some time ago, I had a 2080ti and this was great as I could finally fly in 4k with a good level of details. Then, I got myself a 60" screen and the experience was amazing with TrackIR. DCS is the closest we can get to fly in combat airframes and we all want to experience it in the most immersive way. The technology is evolving and it is bringing us closer to the real experience and this is great. Stepping into VR was incredible, I've been flightsiming since the first version of MSFS and nothing has made such a huge difference than going VR. I wish to everyone to try VR and enjoy the immersion level. Unfortunately it is very costly and demanding.

If you are playing at 2k, then I agree that you do not need to empty your wallet for a 40 series card. Just don't try any VR headset playing DCS and you will be fine.

There is a much simpler way, get yourself a pimax...

Have you tried to revert to your previous nvidia driver to see if the problem is still there? Try to do a clean install using DDU (google "display driver uninstaller").

1.0.1.284 is a beta version, not the official release. I was running on .277 and pitool never signaled me that there was a newer version. After installing .284, I was notified by pitool that a new firmware was also available and I installed it. This might be the issue you have but the recipe for DCS native OpenXR support to work is: DCS OpenBeta 2.8.2.35759 Pitool 1.0.1.284 PimaxXR 0.3.0 OpenXRToolKit 1.2.4 No OpenComposite Start DCS.exe with command line arguments: --force_enable_VR --force_OpenXR ...and the magic should work.

4080 user here. I am driving a Pimax 8kX at native resolution (4k per eye) with good level of details and great resolution that does not require absolutely MSAA. Vram is a strange issue. it seems that the more you have the more it get filled. I do not see or feel an issue so far, even in MP flying in South Atlantic. My advice is save money on GPU, get a 4080, sell the G2 and get a Pimax 8kX. The difference in immersion will blow your mind away.

In games where rBAR is working and has been implemented, there is noticeable and even substantial increase in performance of up to 22% from what I saw in this youtuber's tests: I doubt very much it is implemented in DCS. From my own testing, I did not noticed any significant performance difference either.

I used to have to endure the MSAA performance hit in order to have an acceptable level of shimmer with my pimax 5k super. Same with my 8k+ as I was not able to supersample enough to get rid of most of the shimmers. Now with my 8kX and DCS native OpenXR support, I am able to fly at native resolution. 4K per eye is the sweet spot for me, the higher resolution is truly the cure to reduce the aliasing to an acceptable point. It's not that I would not like to switch it on, I did try using it and it eliminates almost all aliasing. Maybe when we get the upcoming "shadow options" and multithreading I will be able used it again. It's a balancing act no matter what is your setup, you just can't have it all.

It's working fine. Click import and point to DCS.exe, then go in your settings and you should see DCS in the game list. when you start the game with the shortcut, Pitool will detect dccs.exe and apply whatever setting you defined specifically for it.

Have you tried importing the DCS.exe from your game list? If imported, it will become available in the game specific setting as "DCS" and you might be able to make it work that way. I will give it a try and let you know if it works.