Silver_

I only experience stuttering and therefore frame drops when I enter missions with a lot of troops attacking on the front lines. If it's a mission with a low load, I don't even realize it exists. This happens to me especially at the beginning of a campaign. I'll have to try the antivirus exclusions thing you mentioned, but I'm not entirely sure it will fix it.

I've done a lot of testing with this, and I personally prefer preset E because on my 3090, in J and K modes, it eats up frames and also makes the image look less contrasted. Perhaps those latter modes would work better on more advanced graphics cards, but not for me. Enviado desde mi SM-A336B mediante Tapatalk

Thanks for the clarification, my friend. I wasn't aware of this. All of this leads to errors because in previous versions of DCS, the bomb's code could be programmed through the avionics, hence my confusion. The fuse types were removed in a patch, and in FMU-152, it was claimed to be configurable from the cockpit. I'd like to imagine that in real life it will be as you say. I've always been clear that this has never been possible in the F16, and this approach has been maintained in this aircraft but, in the F18, it's simply changed from one day to the next. Conclusion: I no longer use the CODE button on the "weapons page" because it's useless. (I do use it in the TGP for LTD and LST because it needs tuning.)

So, from what I understand, and I understand less and less, has this become just a label? (Red arrow in the drawing.) A friend from the wing told me this, and I couldn't believe it. I set up the FMU-152 fuse, which is supposed to be set in the air, and it didn't work either. IT ONLY WORKS IF YOU SET IT ON THE GROUND. INCREDIBLE. Please put these drastic changes in mechanization in red letters on the ChangeLog.

Exactly, it only happens at night. I forgot to mention that this happens to me in VR (Quest 3 in my case; I don't know if it happens to other headsets) and with DLSS enabled (mode E). If I revert the changes and leave DCS as it originally was (green monitor), this doesn't happen. My friend, don't worry about fixing it right now. Get your computer up and running first, that's the most important thing. I'm in no rush, and I'm very grateful. Thank you.

Hi @CapnCoke congratulations for this mod because I love it, I use it since it came out. The only thing I notice is that in Night Missions (dark whithout moon) the fonts are chosen becoming illegible as you have the shine up. To be able to read them I have to lower the brightness to the minimum and raise the contrast a bit. With the original fonts this does not happen. I do not know if you anticipate putting some kind of improvements in upcoming updates to correct the readability of the MDP at night or selecting Night mode. Thanks for your work my friend.

yes, it's right my friend. I didn't think on this. Enviado desde mi SM-A336B mediante Tapatalk

But from what I understand, what it does is apply a common DLSS configuration (preset K in this case) to the entire computer. Or am I wrong? Enviado desde mi SM-A336B mediante Tapatalk

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.