WipeUout

I just tried also and it solves the problem but not 100%. Occasionally, the lag/wobbles will start but will not last very long, it will go away as soon as you start rolling the aircraft. Another way around is to use PimaxXR 0.2.4 instead of the latest 0.3.2. This will remove the lag/wobbles but may introduce some micro stutters which was what I experienced. The previous workaround is better for me. I used 61 FPS for frame rate throttling (since my HMD refresh rate is set to 60) along with turbo mode "ON". I did notice a slight loss in performance of about 0.5ms increased GPU frame time though. Not a huge problem. @mbucchia (author of PimaxXR) commented on github that he will not able to get back to his PimaxXR project before May, we will have to be patient for a more elegant solution.

Sad but relieved to learn that it's not only me. I have installed OXRTK 1.3.0 and it did not correct the issue, on the contrary I got back the wobble/lag in the menus again! I can't rule out either PimaxXR or OXRTK for causing the issue, this is puzzling. I'm thinking about rolling back to Pitool 1.0.1.281, since this is the stated "better" option for compatibility with PimaxXR 0.3.2 according to the wiki on github, and see what happens.

Instable experience so far. Not sure what is causing it but when using PimaxXR and OXRTK with the MT version, I get what looks like HMD tracking issue with image lag and wobbles as soon as I move my head. This starts when I switch view from cockpit to map but not all the time. The wobbles and lag goes away after a while but not always. I haven't found what is causing this nor how to stop it. This issue was also present in menus prior to the latest OB but not anymore since OB 2.8.3.38090. I have to try OXRTK 1.3.0 to see if this will correct the issue, I am still using 1.2.4. When my "tracking" problem is not happening, my performance is great with MT. My CPU frame time dropped dramatically from 8.2ms down to 3.3ms. On the GPU frame time, there is also a good drop from 12.9ms to 11.6ms. This is GPU performance that is even better than what I had with DCS 2.7.18. As a result, I can now use MSAA 2x and maintain 60 FPS and 100% native resolution in any situation including flying in Syria over Aleppo at 1000ft. I'm using same settings in OXRTK with fixed foveated at 55/80/100 and nothing else. In Pitool, I increased backlit and brightness to compensate my gamma setting in DCS. I now use a DCS gamma setting of 1.3 which effectively reduce haze quite a bit but requires higher level of brightness/backlit. I do not use smoothing or reprojection, nor fixed foveated in Pitool as it does not work. I keep same settings in DCS with clouds normal, flat shadow with blur off, no anisotropic filtering, vis. range ultra and now MSAA 2x.

I have this problem and use the ST version with SteamVR to minimize the problem. The worst is with OpenXR with MT, stutters and wobbles come and go all the time and very sickening. Even MT with SteamVR is bad with stutters every 2-3 seconds. Not sure if it is pimax related but one thing for sure, we are still in beta for MT...

Last DCS update corrected the menu issue but now I have instability in-game every now and then. The tracking becomes lagy when I switch to map or external and stabilized a while after, very annoying and difficult to reproduce. Any having these issues? I am back to SteamVR with the ST version for now.

For me there is a significant improvement, close to 1ms GPU frametime decrease. This might be very different depending on hardware. Unfortunately, PimaxXR is not working well in MT with the menus but ok once in the cockpit. Test I ran using MT with native DCS OpenXR support brought me back to 2.7.18 performance at the same level of details and settings!

Firmware update with Pimax needs a bit of polishing. I did it with three different HMDs and none worked on the first attempt! Fortunately, it did work on the second try and guess I was lucky. Seems that some issues with Pimax are persistent even if you reboot, I had to completely unplug all cables and wait a minute, replug and restart the PC for issues to go away. There is a price to pay for this wide field of view...

Lots of rationalization and anecdotic facts here. Pimax 8kX is the ultimate immersion experience, tried many other HMD and tunnel vision is not good in flight sim. Try a well optimized 8kX setup at native resolution and you will be blown away. Will not speak about the Crystal until I try one but right off the bat, its FOV is not as good as the 8kX. ...speaking from experience

New MT compatible version was uploaded. Go here:

It s a balancing act. When the simulation spends time recording and saving input (head movement, keyboard, joystick, etc.) it takes resources away from the main task: Simulate! The reason why tracks are not 100% accurate is probably because the capture frequency (or sampling rate) is not keeping up and you end up loosing input. To solve this you need to bump up sampling rate and consequently you redirect resources that should simulate instead of doing telemetry. So the other solution is to re-design the capture engine, lots of work. Make a track, keep it short and that will do the job. Just don't use the F-14, it is broken as far as track recording.

A DCS track is an automatic recording of keystrokes and controllers input captured while flying a mission. In order to fly a mission, you need the map and the aircraft module. If I understand what you propose, you would have community members creating the tracks with all possible combinations of airframe/map/mission type, and then have those tracks selectable as part of a benchmark? Not simple nor easy. Everyone has the liberty to create tracks that are relevant to their gameplay, more easy and flexible!

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...