Werewolf_fs

It's the Turbo mode of OpenXR toolkit, turn it off and it won't happen as often. Turbo Mode exacerbates a bug in the Oculus driver that mBucchia has already reported to Meta, but that needs to be fixed. MBucchia has fixed it in Quad View Foveated, we hope to add this fix to the OpenXR toolkit soon.

There are also more sound cuts than with the previous version.

I have been lucky enough to test almost all the vr devices on the market since 2017, (except Varjo) and this Quest Pro is the one with the best black on an LCD screen and the best night in DCS by far, it is not perfect, but it is the better than I've ever seen. I don't see that foggy mess, neither do I nor several of my colleagues who also have the Pro, I hope it's a possible configuration problem, because it doesn't make sense. Although tit is true that VR has a lot of subjective and physiological assessments that make the experience very different for each person.

DLSS 3 and 3.5, use a DLAA technique as default antialiasing method. Nvidia itself say that

DLAA is working by default wint DLSS, if works togerther ALWAYS if DLSS is active and, I have the same quality loss with DLSS and with DLAA without DLSS, the one that creates that loss is the AA DLAA filter in both cases.

DLAA is working by default wint DLSS, if works togerther ALWAYS if DLSS is active and, I have the same quality loss with DLSS and with DLAA without DLSS, the one that creates that loss is the AA DLAA filter in both cases.

It is a problem with the STN of the DATA LINK of each group. All 4 members must be in the same rank.. if it is 01203, ALL will start with 01..., (01203, 01204,01206, ect..), if it is 11203, ALL must start with 11... (11203, 11204,11205, 11026), if any member of the group is with another rank,,, (01203,11204,11205... ) = CTD

In OpenXR tool: https://mbucchia.github.io/OpenXR-Toolkit/ in performance In Oculus Tray tool: https://www.apollyonvr.com/oculus-tray-tool option VISUAL HUD ---> APPLICATION RENDER TIME In Oculus Debug tool: https://developer.oculus.com/documentation/native/pc/dg-debug-tool/ option Visible HUD ---> APPLICATION RENDER TIME With subtitles why is it in Spanish

I am lucky that my USB-C port on my motherboard (Gigabyte Aorus Z690 Elite DDR4), holds the charge and after 6 hours of use the battery is around 60%

This tutorial is in Spanish, but you can add English subtitles. I come from G2, and with these configurations right now it looks clearer even better than with my previous G2.

hat has nothing to do with the QUAD FOVEATED. In the DCS VR tab options you can choose to make the mirror full resolution.

I have both working fine, but it causes a 2-4 MS increase in CPU and GPU usage, compared to just DFR

I have them sporadically, since v54, I don't use HTCC. I hope that with v55 it will be solved.

Same... It was before

Tested. The improvement is substantial, I already use the FIXED foveated and even so the improvement is noticeable. What surprised me the most is the Sharpening that this application adds, much better or more noticeable than that of OpenXR tools, the improvement by eliminating glare and flicker and so on is brutal in the scene. On the other hand, I continue to have problems with the tube mode, the ASW adds more artifacts and, apart from that, if I take off my heatset even for a second and put them back on, the DCS loock and CTD. Sometimes it also does so when returning to cockpit from the F10 map. This already happened with the Tubo Mode in OpenXR tools in MT mode, that's why I didn't use it, deactivating it solves it. Great job @mbucchia, you are the best! Tested in 13900K, 64Gb, 4090