WipeUout

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.

Great post @everest101, thanks for starting this. I have not tried with my 5k Super but will do eventually. As for my 8kX, the native OpenXR DCS support is providing even more performance compared to using opencomposite. I have gained 1ms in GPU frametime and 1.3ms in CPU frametime with my test track in Caucasus with the f-18. I set pitool at native resolution, 60hz, normal FOV with a bit of backlit increase. No compulsive smoothing whatsoever and no fix foveated rendering as it does not work in DCS from pitool. In OXRTK I use fix foveated rendering at 55/80/100 and the performance gain is really good. The Pimax HMD is the ideal VR headset to use fix foveated rendering because of the large FOV, but personal preferences may vary. I use also CAS sharpening at 80%, no modification of the resolution. 4k native is very nice and clear, I do not use MSAA anymore as the higher resolution is the best cure for aliasing. If you have the newer 8kX with 90 hz minimum refresh rate, you might still need some compulsive smoothing or to scale down some settings.

I paid 900$ for my refurbished Pimax 8kX directly from pimax. 4k per eye, 170 degree FOV... Not going back to tunnel vision!

You will not be able to lunch from Pitool but this does not prevent settings in pitool to apply. You can still set whatever setting you want in the "Common Settings" and they will apply. The "DCS.exe" shortcut with the command line arguments is required to run in OpenXR and this is well explain at the start of this topic. You still have to option to use opencomposite as before but by using the native OpenXR support within DCS, you will gain even more performance. I have gained 1ms in GPU frametime and 1.3ms in CPU frametime using native over opencomposite, this is quite significant. Make sure you use the latest versions of PimaxXR (0.3.0) and OpenXRToolkit (1.2.4) for this to work, and also very important, latest pitool version (1.0.1.284).

I don't think that rBAR is working in DCS. Did a bit of research and when a feature is working, in the game profile of nvidia profile inspector, the little gear beside the feature is green. If the feature is not working, the little gear icon stays blue. nullnull

Yes and No. We now have native OpenXR support in the latest OB. I gained quite a bit with about 1ms in GPU frametime and 1.3ms in CPU frametime. Of course, results vary depending on your particular hardware. Look here to see "how to":

OMG, finally got OpenXR to work with DCS Native support from latest OB version. I did not have Pitool 284 installed and this was causing the issues. The results are stunning, I have a GPU frametime improvement of 1.0ms and even a CPU improvement of 1.3ms with same settings running my test track file.

When I downloaded it, I created a folder for OVGME and labelled it "OpenComposite 0.6.3"...

..or simply hide the HMD from the lighthouse for 1 second. BTW, one lighthouse is fine if you only do DCS or any VR in sitting position.

Have a look at your log if you can notice any error at the end. Since you say that single player works fine, then this is weird. Post a new bug with your dcs.log, dxdiag output and as much details as possible.

Yes, the OB 2.8.2.35759 only. Very confusing indeed but the first two post here are very clear and detailed: https://forum.dcs.world/topic/318004-dcs-now-supports-openxr-natively/

I use now the opencomposite dll to switch from OpenVR to openXR runtine and bypass DCS native OpenXR. This version (0.6.3) is the one that works fine with PimaxXR 0.2.8, it is attached and it goes in the dcs\bin folder, as you probably know. If I you want to use the DCS native openXR support, you do not need the opencomposite switcher but need to have PimaxXR 0.3.0 and OpenXRtoolkit 1.2.4, and add two arguments to the command line (see first subject in vr forum), but in my case, it does not work well. openvr_api.dll

I just switched the 8k+ for a refurbished 8kX by Pimax. Wow, what a difference! Running native 4k at 60hz with no repro or MSAA and the image is simply stunning. Resolution is the cure to aliassing, MSAA is not required anymore. Running at 60hz gives a lot of breathing room and I can use low shadows, normal clouds, medium water, high textures in any scenario without exceeding 16.7ms frame time. Of course there is always the exception such as missions created for DCS-liberation that eat up your CPU like crazy. But even in Syria, I am flying without need for any reprojection. Native 4k per eye is so beautiful! Unfortunately DCS Native OpenXR introduced with 2.8.2 does not work good for me though. I had to revert back to using opencomposite instead of the command line switch to force OpenXR. Even using Pimax XR 0.3.0 and OXRTK 1.2.4 did not help. The issues I had were two fold: 1. Stutters when moving my head up/down right/left. 2. Blurry image out of focus or having left/right image synch problem. Going back to PimaxXR 0.2.8, OXRTK 1.2.1 and opencomposite 0.6.3 solved the issues. Wonder if this only related to the 2075 serial number 8KX or also present in 2076 models?

If it is only in MP server mission that you have this issue, it might be related to your client not being ''pure''. Do you have any mods running that breaks IC? There is an icon that is either green (OK IC) or red (IC broken) on top of the server list. The other issue could be that you are missing a required/compulsory module to access the mission. This should show in the bottom left corner in the server description when the specific server you want is selected.

Difficult decision. I would tend to go with the 4070ti because of the new architecture and DLSS 3.0 support. Because it is faster than a 3090. Because its power draw is much less than the 3090 and depending on the power of your PSU, it might be necessary to upgrade it as well. Because used hardware has higher risk of defect, abuse or plain scam. There is also the option to wait and save a little more to get that 4080 or even the 4090 which will give you incredible performance for years to come. The G2 has a high resolution and being able to enjoy it to its full potential takes a lot of GPU power.