WipeUout

I am with you, but two conditions: Same 8KX FOV and a 5090.

Yes, the only way to make this go away is to "Restart Service" and then "Restart Headset" through Pimax Play. After that I am good for the rest of the day. And it only happens at 90hz.

Hard to tell. If the pixel count is lower with the Micro-OLED, then it will be less demanding and offering better performance. What is puzzling here is that the 57ppd lens would mean a lower FOV if the panels are, as indcated, 4k each. FOV is important as well. Even the QLED 50ppd with a whopping 29 M Pixels will require a monster GPU. Hell, my 4090 is not even powerfull enough to fully output what my 8KX can do. In any case, wait and see what the first reviews will say about this. Only then, consider upgrading.

If you want to use CAS sharpening, the OXRTK CAS is more efficient for the same result as using it in QVFR. Do not use sharpening in DCS settings as it is less efficient than CAS in OXRTK also. OXKTR CAS is even lowering GPU frametime compared to not using any sharpening!!

Disabling e-cores would not be advisable in general, but applying this only for DCS.exe plus increasing priority is very good to eliminate stutters particularly on 13th and 14th gen Intel CPU. Consider using ''process lasso'' (https://bitsum.com/), it is a free app that gives you the ability to prioritize and assign specific core to applications. For me, it gave the most fluide and smooth rendering ever. @Bossco82 for your other problems, consider running a repair on you DCS, disable any mods and test incrementally. Also, the last update has broken quadviews foveated rendering and causes huge issues. You can find a workaround in the VR Bugs forum until the next patch that is supposed to fix this.

You might be trying to enter a slot on an ennemi location. At mission start, only the slots on Nalchik can be used as it is the only blue location.

Got it to work but only if I use SteamVR as the OpenXR runtine. Not good as a big loss in performance. Other issue, lots of effects do not work in 3D, just some such as monochrome or anything playing with color palette. I tried all the AA stuff with no visible effect in the HMD. No solution here.

Roger that. Will use the huey instead and see if I get same issues.

I was on the ground in a UH-60L just after capturing the water processing plant... ...and just experienced another CTD, here is the log: dcs.log

Fixed wing, I tried several (F-18, F16, A-10, F-14) with same result, no points after landing. I did try to capture locations with a UH-60L without any issue except when I landed on Beslan, right after unloading troops and had a CTD. When flying around and taking out targets (land and air), they are registered and accounted for without any issue. It is only when landing back that nothing happens.

Does not work, effects are applied only in the mirror image, not in the HMD. In which folder did you install reshade? bin-mt or bin? I tried bin-mt and it does not work.

Hi @cfrag, balance seems much better from a single player perspective. However, I noticed a couple of issues: 1. No detection of landing back at blue airfield, not getting any points earned. no error message displayed. 2. Upon landing and off-loading troops at Beslan to capture the airfiled, game crashed completely (CTD). I will look at saving the log next time it happens, sorry i did not save it.

Solved the issue by uninstalling OXRTK, deleting folder and re-installing.

I've been using Quadview with my Pimax 8KX because it is far more superior to fix foveated rendering feature in Pimax Play or OXRTK. It is borken for me as well, and even OXRTK does not work anymore. Please fix this, I am going back to 2.9.5 as it is the only temporary fix for that 2.9.6 stutter fest and 2D DCS is not an option.

Seems that OXRTK does not work anymore, no effect applying (CAS) and detailed FPS reporting not working either. Access to interface still works from within VR though.

OXRTK is a set of tools in addition to OpenXR which is a runtime. I do use PimaxXR, Quadviews and OXRTK without any issue in DCS with my 8KX.

RAM increased form 32 to 64 provided a more constant experience, not better performance but less micro-stutters. As far as eliminating stutters, using "process lasso" made a significant difference for me, and it is free BTW (https://bitsum.com/). Having the ability to "reserve" performance cores for DCS is great help. Also, having the ability to set priority level for all running programs while using DCS helps to eliminate other sources of stutters. With process lasso, I feel more like I am moving in a world as the video stream is so smooth.

I wanted to test this and kinda forgot about it, so I gave it a go. I as expecting that using quadview CAS sharpening would provide best performance since it is only the focus are that is getting sharpen? I was wrong, something else is at play here. Results show not a whole lot of difference between sharpening options but clearly, CAS in OXRTK has the edge not only for a lower GPU frametime but also for lower CPU frametime. Also of note, OXRTK sharpen offers a slightly better performance than not using any sharpen option! I repeated my testing several times and results are consistant at +/- 0.02 ms. It is entirely possible that you could get different results for other HMDs. As far as quality of visual, OXRTK CAS and QV CAS offer similarly sharp visuals at 100% and DCS a little less sharp at 100%. Note: DLSS B = balanced setting, FT= Frametime in milisecond.

I avoid using DCS pixel density as the whole image gets supersampled and is a big hit on performance. To improve clarity you may try using Quadviews to supersample the focus area and OXRTK CAS at 100% for sharpening. Do not use DLSS performance as it will blur too much, use balance or quality. Your gain will be reduced but with a small gain nevertheless along much better sharpness. You can also use CAS from Quadviews but I find CAS in OXRTK to be more efficient and leave sharpening in DCS and Quadviews at 0.

Had a 4080 and was getting good results but went to a 4090 and gained about 10-15% more. It all depends on your HMD. I use a Pimax 8kX which has a lot of pixels (4kx2=16.5 MPixels) to render and even with the 4090 I can't get to the maximum possible quality my HMD can provide. If your HMD has less resolution, the 4080 will give you a very good experience at high refresh rate. Your CPU may also be important in the equation, it could be the bottleneck in some scenarios.

There are lots of report out there about the instabilities of the 13th and 14th gen i9 CPU because mobo makers do not follow intel's recommended settings as default in the BIOS. There is less issues reported for the i7 but in any case If you follow these settings, no issue and your CPU will last several years. If intel set max recommended power to 253 watts, set it up in the BIOS. As far as selection of a mobo, it is a good choice to go with a Z790 but do not spend too much, just the basic Z790 is more than enough and provide access to all possible settings for the CPU voltage, power , etc. Overclocking is not a good idea as it will shorten the life of your CPU but the Z790 is required to access important BIOS settings for a K sku.

Sorry @Aapje but this makes sense depending on what you are looking for. There is place for different opinion on this and I never said the X3D was bad, on the contrary. Everybody is entitled to their own opinion, no need to bash other's if they are different than yours. I stand by my comment that single core performance is critical for DCS but not so much in other games that fully exploit mutlti-threading. Going to AMD will require new DDR5 RAM which adds to the cost also. If cheap and fast is what you are looking for, then the i7 with a DDR4 mobo is the best choice.

Hi @Ski01 The key metric I use for DCS is single core performance. Allthough DCS went Multi-thread, it still uses very few cores and generally the rendering core gets overwhelmed as soon as there is too much action in a mission. Having a fast single core performamce will help ensure you have most headroom. Having a 3D cache (7800x3D) certainly helps but in the current market, you can get an i7-14700k for the same price with signnificantly more horsepower as far as single core performance. I would say 1st choice is i7-14700K, second 7800x3D. If you need to avoid buying new RAM, you can still find intel mobos that support DDR4 also. All depends on your wallet size and if you also play other stuff than DCS. For other games, the 7800x3D is a better choice.

DCS now has multi-threading which means CPU tasks run in parallel. There are two pipelines taken care by the CPU, simulation and graphical. Seperating the two pipeline, i.e allocating different cores to tackle each is helping the CPU to keep frametime below the target. If any of the two pipeline takes too much computing power, the result is a frametime too high and stutters. It doesn't matter which pipeline is not keeping up, the result is the same: Stutters. Yes, this means that your GPU is not being used to it's full potential but low usage of the GPU can happen even if your CPU has low usage as well. This means you can crank up your settings until you reach a frametime just below the corresponding value for your HMD refresh rate. Personally, I use 90hz refresh rate. I always try to keep my GPU frametime around 9 to 10ms, aiming to keep it under 11ms 99% of the time. My CPU is not a limiting factor but I make sure only the performance cores are being used for DCS through Process Lasso.

Since DCS 2.9.3 there is only the "stable" version, there are no Open Beta version updated anymore. The MT version is in the bin-mt folder yes. In any case, it is better to use the latest version of DCS which is 2.9.5.5518 now. As for WMR and the G2 and how to use OpenXR as your runtine (required to use MT), I don't have much knowledge about this as I am a Pimax guy...