gonvise

Sorry but not; I'm using only DLAA, and the move from DLSS 3 to DLSS 4 has greatly improved ghosting, almost eliminating it.

I forgot! Since I usually use TGP on target, I don't need to do CZ or I do it without thinking, but it's true that I didn't do it on the ground. Thanks!

I also use that waypoint, but in the second mission, following the alignment instructions as usual, although the alignment works and when moving from one mav station to another with the NWS button I can clearly see how both the TGP and the MAV point to exactly the same place, suddenly the waypoints in HUD (1 selected) are more than 60 miles away, I don't know what I'm doing wrong. On the other hand, the HSD still shows the correct WPs.

Sorry, but if there are two videos about the cold start, which in this campaign are supposed to be made faithfully to reality and respecting communications with the ground crew, and neither of them says when said alignment is made, I think the question is not out of place.

Is it necessary to align the mav's? I don't see anything indicated about it in the cold-start tutorial

Yes, I tried it, but the result was the same, after a few mission loads the effects compilation would get stuck... maybe just on my computer, the fact is that it doesn't anymore, but I don't know which of the effects I removed was the culprit, and I also thought that if they weren't checked they wouldn't compile, but it seems that all the ones in the folder are compiled.

I have removed all the reshade effects and left only the VREM ones. Since then I have not had the error of an effect getting stuck loading again. I only use HDR, and the possibility that with VREM it is applied only to the cockpit is a game changer for me, thanks.

First test checking the option "technique only for VRview" in VREM, and in this moment... ReShade.log

Where exactly do you see this duplication in reshade.ini? I just wanted to check it myself.

For example, this time it was by enabling the Technicolor2_for_VREM effect and modifying its strength, in this case it even crashed DCS... ReShade.log

Using VREM HDR all day in differents missions; the effect works, it's awesome, but every four or five DCS starts, this happens an HDR VREM doen's work:

I was doing a step by step to give you all the information but, in short, it turns out that with your DCS_VREM it now works perfectly... and I say this because yesterday I tried to do what you say, that is, start from zero, and the only thing that has changed is your file. I'll send you my old DCS_VREM file in case you notice something that could cause the color saturation or what you mention about the double compilation. DCS_VREM.ini

Of course, the shadow doesn't matter. The same thing happens in Syria. With "refresh technique" nothing change. Attach reshade.log with free fight in syria with saturated colours after "capture frame". ReShade.log

First of all, sorry for the quality of the screenshots, I'm remote... the effect is the same in 2D and VR Loading several missions in Caucasus, one after the other, all good... Loading first Afghanistan mission...saturated colors Loading again same caucasus mission, saturated colours... And after load first mission, this shadow appears in the menu, it is the cockpit frame of the plane...

Any aircraft, the thing is that after loading a mission in Afghanistan, the colors appear saturated or darker, I couldn't say, and if you then load one in Caucasus the same thing happens again. The HDR continues to work in all cases only in the cockpit. I'm going to try to delete the shader directories.

A very rare bug... I load Free Flight F16 fast mission in Caucasus, everything is fine, HDR in cockpit only; I exit and load Free Flight F16 Afghanistan; very saturated colors outside; I exit, load Free Flight Caucasus again, saturated colors outside. Only HDR VREM selected in reshade effects, and nothing enabled in VREM except techniques.

After a clean install of Reshade and VREM 7.2, I confirmn that reload works, and even when restarting the effect continues to work in inner and aouter Quad views. I insist, the HDR effect in the cockpit individually is fantastic, since in my opinion the cockpits are over-illuminated compared to the exterior.

And you perceive same ghosting in same conditions in cable link?

Yes, it works, in 2D and VR... I prefer to edit the registry since I know what I'm doing, whereas DLSS tweaks I don't know what they do.

Yes, at first at some point pressing reload the effect worked fine in Quad all view, but during the tests I had this warning several times, reshade stayed like that indefinitely, so it was somewhat difficult for me to carry out further tests.

Hud overlay can also be enabled/disabled via regedit...

Thanks @Fiztex, but again the same results with VD. Quest Pro, at 90 Hz, VDXR Godlike (Via dedicated wifi-6 router), DCS PD 1.3. Same configuration as I already mentioned in QVFR, DLAA (DLSS 4). - Visual quality is worse than with cable link, I have tried several speeds and I always notice some compression. I have also tried to increase the PD. - Similar performance talking in "FPS", but taking into account that with the quest pro I notice the flickering of 70Hz, I have to put 90Hz, so although I have between 60-80 FPS, without reprojection I can't stand the lack of fluidity in view rotation at those FPS, and with VD reprojection... I better not talk about it, it is inferior to ASW from my perception, with ASW the movement of my head is practically natural (like in life itself), without stutters and with very little ghosting, only perceptible in some very fast scenes or sudden head turns. Overall, although I could lower my expectations a bit in terms of quality, I can't get anywhere near the fluidity that ASW gives me. Again, I've tried, as I told you, I bought a wifi 6E router just for this, but in the end each of us has our own perceptions, and yet, no matter how much I turn up everything, I still can't get the image quality and fluidity that I have with a cable. The point is that each one uses what works best for them. Thanks!

HDR effect works, only in cockpit selected, but only affects center of Quad view foveated area, even with "all view" selected. Because of this, the transition between the foveated central area and the peripherical area is very noticeable. But the HDR only in cockpit... wooooooow!!! If you can get it applied to the whole area, I think the community will really like it. Thanls.

Quest Pro (with eye tracking), mbuchia QVFR, DLAA (with last DLSS 4 dll and preset K)

I like my current setup, but I have no problem changing them, in fact, I'm always trying and trying, I spend my life like this ;-), and I'm open to anything that improves quality and performance... I don't want to convince myself or anyone else, just prove that it's what I perceive better DCS with. To start with, as you say, comparing the Quad View configuration on a Quest Pro, which really has eye tracking, with a Quest 3, which doesn't, can lead us into difficult comparisons. I don't need vertical offset, with that QVFR configuration and eye tracking, I simply don't perceive the transition from the center foveated area to the peripheral area. Also as you say, if the reprojection is not as good as ASW, for me it's a negative point, but of course I will try everything you say as soon as I can.