Silver_

Sorry teacher, you are right. The fact is that I put my question here about DLSS and QVF because we are in a forum in which DCS issues are discussed and how could I not talk about the new graphic implementations introduced by developers and how it affects those of us who use QVF . I didn't see a better place to put it than this problem (in another place they probably wouldn't have understood me). I say the same as @Qcumber. Sorry.

It's going really well my friend, thank you. The only problem I see is that the image of the TGP in motion is not good, like torn. The radar cursors also fade when moved across the MFD screen. This is all due to DLAA and DLSS but what I am doing is using TAA or MSAA instead and this problem disappears, at least until DCS solve it.

I'm sorry, it's true, I forgot to say it. I have AMD Rayzen 7 5800X CPU and Nvidia RTX 3090/24 Gigas, my headset are the HP Reverb G2.

For DLAA+QVF to give us less blur, a parameter must be raised in the QVF configuration (focus_multiplier). At x1.6 they give a good relationship between performance and focus, the higher you raise it, the sharper everything looks at the cost of losing lots of FPS. For now I'm sticking with MSAA (the old one) because I observe that when applying these new smoothing techniques, frames are increased but image quality is lost and a series of unwanted artifacts/errors such as ghosting and others are also added. . If you look at the radar cursors, for example on the F16 (my favorite plane), they fade as they move across the screen and if you look at the TGP images, they are not sharp at all, they blur and the objects leave traces, on the other hand in MSAA this does not happen. At the moment I have not found a configuration that satisfies me, but if you have it and see everything perfect with the new DCS implementations, I invite you to share your experience here.

Thanks for your discovery, it worked for me too. At least it works, the problem is that I still can't adjust the size of the mask. But this is already a lesser evil.

Go to here:

Yes, I updated today. Exactly I use QVF foveated rendering. I have the HP Reverb G2 with an RXT3090 graphics.

I have exactly the same problem, any value that changes, of the two that there are, in the NVD_common.hlsl file has no effect in the simulator, at least in VR. However, if I change the values of the NVD_HDR.fx file, the change is noticeable. @Taz1004 I think there is some problem with the names or at least in VR they don't work, I didn't try it in 2D.

Thanks my friend, no problem. Thanks for you great job , I'll wait impatiently for that correction to come out.

What can I do to avoid the problem of my gamma going to 2400 instead of 2.4? It happens to me when I open with this launcher. Thank you.

Personally, I think that I like the noise in version 1.2.0 more than in the latest version 1.4, which I see as very artificial and not the typical noise of electronic equipment. Please note that this is constructive criticism. Either way, great job mate.

You can touch the friction screws to correct it with an allen wrench. I don't know what you mean by sync lock.

Try to adjust the friction of both axles as similar as possible, if you have them adjusted well (one axis is not harder than the other) then the problem is one of electronic calibration rather than software calibration (which I imagine you already have calibrated many times!!). Winwing in your app, and this is a very personal suggestion, should have a software adjustment to correct these possible offsets between axes.

I'm trying to make a backup copy of the presets, in the "Graphics Preset Settings" tab, when trying to recover them the configuration was deleted and I had to put it back in by hand. I didn't do something right. Basically what the correct process would be. I would also like to know if it is possible to make a Backup of the flight controls of each aircraft. Any help is appreciated.

I have uncheck some parameters that I had configured in Windows, such as the "GPU hardware acceleration" and the "Variable refresh rate", that is in Windows 11. Within DCS I have unchecked ,in config VR window, the option "Use the same resolution that DCS ". On my AMD 5800X and RTX 3090 system the stuttering has decreased significantly. I don't know if this will have the same result on other systems. I use Turbo Mode in ON. I forgot to say to also enable "Optimize for Performance" mode in WMR. You will notice how the three spinning balls change size while loading DCS but that does not prevent DCS from displaying quality in my G2.

You need to assign a curve, in DCS, to that axis to avoid the sensitivity problem.

I used other nuts to take advantage of the suction cups that came in the kit, the round head nuts are impossible to fit into the aluminum guide that holds the rail where the throttle lever travels. I have not had to drill anything.

Today, is it better to have it activated or not? I've tried both ways and I don't really appreciate the difference in DCS, I've also tried too with variable synchronism and no changes. I ask this because they say that it is better to deactivate it but the posts where I have read it are very old. The tests are with MT and in VR with an RTX 3090 24 Gb.null1.273 × 853

For me with the latest Orion 2 firmware (V 1.12) the problem was fixed.

Thanks my friend, I recovered it.

How can I recover my old Preset I made a backup but I can't see it anywhere

Thanks for the help finally it was fixed with your solution but for some reason my Options.lua has disappeared and I don't know how to recover it, now DCS loads in default mode. I also do not know how to do with this application to send a new profile to DCS and that it is automatically loaded at the next start.

I have this problem when I switch to the Graphics Preset Editor window with the lastest version. https://gyazo.com/a3c16f15f4277cf1b273ebfece4be181

I have noticed that my Reverb G2s have more sttutering when I run the MT .exe than when I run the standard beta version. I run both versions in OpenXR mode, the first brings it natively and the second I force it with Opencomposite. When I refer to sttutering, I mean when I turn my head in the cabin, looking at the buttons, they move with little smoothness creating an annoying effect. This does not happen to me if I use the normal .exe (DCS.exe). I have no idea what it is for. I have an X570 chipset, AMD Rayzen 7 5800X and an RTX3090 with 24 gigabytes.

I have been told by Winwing that they will try to solve the problem for the next patch. I hope it.