Silver_

I don't know how thinking this has marked like "not a bug" you simply have to read and understand. I think.

Thanks for nothing .

You need evidence and I need a bit of logic. There are many things currently in DCS that do not support the reality. I will not be the one who tells you I imagine that you will know them because you have his evidences.

Hi @Lord Vader I think it is not necessary to explain to what the AUDIO 1 switch does, as the name implies is to control the audio in first RADIO (UHF Radio). In the OFF mode the Squelch is deactivated, in the SQL mode the auto-squelch is activated and in the GRD mode the radio goes to guard channel (passed to be able to perform a transmission (only TX not RX) through the guard channel, fast form to pass the radio in case of notifying to the mesh an emergency). In your case, the OFF mode deactivates Squelch (OK) the SQL mode changes the frequency at which he wants. Normally the first channel. (Not Right) the GRD mode changes to guard channel (OK) All this is perfectly documented in the F16 Handbook

I know perfectly how this switch works, it is perfectly explained in the manual. Apart from all this, when I enter the cabin, it is not synchronized with the flight control, and only passes to this switch. The rest of the lots of switches are going well and it is also necessary to interact in them to perform different functions as you says but this is not the case or the problem. Simply synchronization friend.

As the Title says the CAT I / CAT III switch does not correctly synchronize with the Hotas when entering the game, the rest of the switches goes well.

Basically what happens is that when I put the radio in preset´s mode (with for example channel 1) and then I commute the AUDIO 1 from SQL to GRD the radio changes correctly, as it is observed in the ICP (GUARD) but when I return to the Normal SQL situation, the radio is no longer in the PRESET 1 but in the frequency of the alternative radio that is not in use (I have the C&I Knob switch in UFC, not in backup). In a normal situation , PRESET 1 should be appear.

At the moment I have no problem with the preset J, moreover, I see it better than the K.

If you had to stay with a preset with which one would you stay with the J or K? Personally I keep the J, it seems to give me more contrast and focus although I was also going well with the E but with more ghosting.

I also tried the preset J with the latest NVDIA 566.36 and of course I had to modify by script in NVPI to get the J mode (checking this within DCS with DLSstweaksconfig, GlobalForcedPreset in default and HudOverride actived to check it). What I notice is more sharpness in the cabin and all well defined small letters, even in the MFDs of the F16 but what I notice outside cockpit is like a water effect, double image sometimes on the ground, nothing of sttutering , the aircrafts are ok without ghosting. This makes the terrain not see, far, clearly. In cockpit, yes, everything is OK. My graphic card is a 3090 with Quest 3 , I think that in moderns cards it could goes well.

DCS doesn't need anything to make it stutter, it does it on its own. [emoji3] [emoji38] Enviado desde mi SM-A336B mediante Tapatalk

Obviously friend, I know them all, even Fighter Pilot by Digital Integration on the ZX Spectrum needed resources but that has nothing to do with it being poorly optimized.

This is not, as I have read here, about the software being ahead of the hardware; in my youth I have programmed a lot in assembler and I have never seen this before. In fact, programmers use current hardware and not more advanced hardware that no one has (this is ridiculous). All of this is a bunch of excuses for not telling the truth, that the software is poorly optimized!!!. It may be very pretty on the outside and painted pink (good graphics) but on the inside it is rotten. Of course, all this has an easy solution and it is the one that some have pointed out here, "I buy the most advanced and expensive machine and I'm sure it will work well for me" this, and sorry, even my little boy knows it, who has no idea of computers. Anyway, as others have pointed out, and well, even if you buy the best machine there are still problems in various situations (it does not always work at 90 FPS). This is due to only one thing: "You have a utility car powered by a Ferrari engine", obviously with some adjustments the utility car will run a lot with this engine but you will never have the line or design of a sports car and you will get vibrations ( sttutering) everywhere. I hope I have explained myself well with the comparisons.

Quad View Foveated have Turbo Mode too, my friend.

The DCS FPS limiter is not the best option apart from the fact that it does not allow you to set exactly 72, so you have to leave it at maximum (300 FPS) and limit it externally with the NVIDIA graphics options (this allows you to set it to 72). Personally, if I use a reprojection (ASW) with 72, it is good to limit it to this value, although in reality we will then obtain exactly half (72/2= 36 Fps) for a more fluid experience. I stopped using OXRTK a long time ago because it seems that DCS is now more oriented to QVF, for this reason I make the limitation in NVIDIA's own options.

Personally, I have noticed that the Frame Time improves a lot when I run the DCS mirror in full screen. In window mode, it has always given me more micro stuttering because it interferes with other Windows apps and you can see that the Sim synchronization is not the same. However, it is more comfortable when you touch things behind DCS, such as apps that hang, etc.

I'm returning to this topic in case someone else comes up with something else, I've looked at several posts on this forum and on the internet I haven't been able to come up with any solution, Thrustmaster also seems to have no idea. The problem I have is that on the "game devices" screen the warthog stick appears as "Thrustmaster Virtual Game Controller (root)" and not as "Thrustmaster Combined". If this were just the problem, the name change, I wouldn't care; The problem is that sometimes the joystick freezes when I load the script and I blame it on this, it doesn't always happen and other times it works fine but the name "Combined" does not appear anywhere. I have created a new test user on my computer (with administrator rights), I have installed all the software and it appears as "Combined". I have cleaned the registry, uninstalled, reinstalled and nothing solves this. I don't know if any of you have found the solution, which I would appreciate if you could tell me how you did it because I'm running out of options.

Actually it happens to me too.

As the title says, there is a bug with the latest update that affects only some clouds, not all. If you load the Caucasus instant mission with the F16, you will be able to see it. In some clouds you can see many points, like a texture error. I leave the link to the demo video: https://1drv.ms/v/c/d748c16240d10095/ERI-ngtthEVEuFfjLLQMmk8B8c4NuxyJGv5Et3IVsnUFTQ

I think these random blinks are a DCS thing, it doesn't happen in other games. I use cable link and from time to time, there are times when it doesn't, it flashes to black and then the image returns. I have also observed that in the latest Meta Quest Link software the flickering is not seen but the hourglass appears and suddenly disappears.

I have read this post but I think that the solution given ("button mode" in winwing) is not a solution because in the end what is achieved is having a lot of slack in the cursors, making it equally impossible and even more difficult to select any unit on the WPN page. For me the only solution was to make a curve in DCS, it is at least the least bad.

A question to @SkateZilla. Is there a possibility to create a shortcut icon to run DCS and launch various necessary programs? (vaicom, openkneeboard, etc). I normally do it by clicking on "DCS LAUNCHER" but I would like to do it from an icon on the desktop.

Regarding using E or F and if the first has more quality than the second, it depends on how we use it. If you are activated from the DCS settings, obviously mode E is sharper than mode F since in the first "Quality" is being applied and in the second "Ultra Performance". For some reason DCS gives more quality to technique E and not to F, but secondly, I understand they are two very different techniques that have nothing to do with quality but rather with the way of treating/processing the graphics. To achieve what I'm telling you, you have to put the "Quality" option in DCS and force everything to work like F mode with DLSSTweak. You can check with the HUD override enabled that it is in F mode but with great graphic quality and from my observations it seems that DCS graphics fare better in this mode and have less ghosting. Note: to test I always look at the image quality that the TGP gives me on the F16

Option F eliminates a lot of ghosting but does not cancel it completely. It doesn't matter if you use the latest version of DLSS or the one that comes standard with DCS, the effect is the same. For my part, for now I'll stick with F.