WipeUout

VR vs Pancake and who as an advantage in spotting targets. Pancake use a monitor that has a very good resolution, in most cases over 50 PPD. If you consider that you have a 4k 32'' monitor about 60 cm from your eyes, it would cover about 67 degree of your horitonzal filed of view resulting in a 57 PPD angular resolution. My HMD has a 25 PPD which is less than half of a monitor. To simplify the issue: If we consider a target at a distance that is showing as one pixel in size on the monitor screen, it would need to be at least two pixels in size in the HMD in order to see it. This means that for me (VR user) to be able to see a target at a similar distance as a pancake simmer, I need to have twice the size target to nullify the monitor user advantage. Hense, the case of having adjustable dot size for taking into account resolution. Not all HMD have the same angular resolution and dot size need to be different to account for this. I think that prior to 2.9.6, VR had dots way too big and now it seems smaller but more fair. It is important though to keep in mind that resolution of VR HMDs varies a lot and there need to be different dot sizes, maybe set by DCS automatically?

I use Quadviews with my Pimax 8KX in fixed foveated rendering (FFR) or "without eye tracking" and it is broken as well since latest DCS patch. I get stutters and bad performance. Quadviews in FFR gives a great boost in performance even without eye tracking when compared to Pimax's FFR or OXRTK's FFR. Update: Last patch (2.9.6.58056) corrected the Quadview bug, it is back to awsome fluidity and performance!!! Thansk ED, and thanks again @mbucchia.

It can work, but only if you use SteamVR as your openXR runtime. OpenXR Toolkit is optional. But in any case, it is a huge hit on performance going through SteamVR.

Same, I can't fly DCS without my VR This For the heck of it, I got the old track-IR back up yesterday and could handle it more than 2 minutes... Pancake Simming no more. @mbucchia : Many thanks for your devotion to this community, you should get paid for what you did!!!

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.

What is the contract saying if one party is breaching? What are the remedies and consequences in the contract if there is a breach? How can you suggest such a thing? do you have access to that contract? Let's be a little more patient, all those RB modules are working fine and we can enjoy them no problem.

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

Check and ask on the forum for details (https://forum.dcs.world/forum/248-m-2000/) but afaik no show stoppers are there. The module is pretty mature. It's your decision in the end - buy it if you really like the aircraft. And to add to this about future support, if you look at the second post made by Nineline on the second page of this thread, ED will continue support no matter what :

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.