flavnet

Resolved. Thank you. That's exactly the setting that involved the double launch.

Hi everyone! I don't understand why when I press the button assigned to release one (ONLY ONE) missile, instead two (!!!) missiles are regularly released. If I press once, nothing happens, if I press again nothing happens, if I hold the button down for two seconds (approximately) two missiles are released!!!! I exclude the malfunction of my controller (perfectly working). Who knows what abstruse mechanics the Russians must have devised for a trivial action like releasing a missile!!!! Thanks in advance to anyone who, having fortunately understood it, wants to share it.

Hi everyone! Maybe I'm doing something wrong in the editor settings, but the Ka-52 refuses to attack the programmed targets. I have the mission .trk file attached to this post. A suggestion would be very welcome. Ka-52 no fire.trk

Should the CH Ka-52 be placed in the "Mods\tech" or "Mods\aircraft" directory? Thanks in advance for the indication.

HI! I tested the mission of attacking a column of Russian armored vehicles made up of six BTR-82s followed by six T-90s with an F-15E armed with 13 MK-20s. The result, as Badger1-1 had predicted, was that the BTR-82s were immediately destroyed but, despite being within the submunition trail, the T-90s remained unharmed. Therefore, the lethality of the KGMU-2 is similar to that of the MK-20, while, unfortunately, in DCS there is no Russian counterpart of the CBU-97 to equip the Su-25 and make it an effective anti-tank weapon.

Hi everyone. I had the same problem a while ago. In the missions that I created with the mission editor and in which I had to deal with ground targets, even though they were present, they then disappeared when taking action. In my case, the culprit was a mod associated with the F-22, to be precise the one called "F-22 External Weapon". I reinstalled the F-22 mod without "F-22 External Weapon" and everything was fine again.

First of all, thank you all for your contributions and help. You are truly fantastic! The problem is precisely that in TWS mode you have to wait for all the tracks to go from Search to Track (in the first case they are represented by small solid squares, then they become larger solid squares) and it is exactly at this moment that you press TMS right short (see point 4 of my list). Then, the tracks will become empty squares and the first missile can be launched. Everything OK. The Migs are all fried!

Hi everyone. I am pleased to note that every time the program is updated, it is necessary to study procedures that are already widely known again. Really funny!!! So, up until the DCS 2.9.1.48111 Open Beta update the following is the procedure I used SUCCESSFULLY to engage multiple aerial targets with the F-16C's TWS function: 1) AA mode selection; 2) AIM-120C selection; 3) TWS selection; 4) as soon as all tracks appear on the radar (there are three MIG-29s ahead), TMS right short and all selectable tracks are listed (from solid symbols they become empty); 5) TMS right short again, the closest track is locked; 6) launch of the first AIM-120C; 7) TMS right short again and the second track is locked; 8) launch of the second AIM-120C; 9) last TMS right short and the third track is locked; 10) launch of the third AIM-120C. At 90% all bandits were shot down. After the last update, with the first TMS right short I can only select and hook the first bandit. The other two, although visible on the radar in TWS mode, are not selected (their symbol remains solid). Then, after launching the first AIM-120C, I have to switch to the RWS and manually lock on the remaining targets (making the TWS useless!!!). The question is: what happened?!?! Is this a bug or has the TWS target selection process changed? Thank you in advance for your kind attention.

Hello everyone! I have read the various posts. What I don't seem to have read is a response from ED about a fix to be released soon. As others have written, I reiterate that, if the release of the fix were announced, I would not bother to personally fix the problem which, I would like to point out, does not concern other aircraft but only the Hornet and every time an update of any importance is released.

Hi everyone! In order to help those who, with a hardware configuration like mine, have had graphics performance problems with version 2.9, I attach the image of the graphics options page with my current settings, the result of many tests. Now the simulation is really fluid - even with many subjects in action - and, from a graphic point of view, I think that the SSS option (after the latest update) brings great realism to the scenario. The defects of the DLSS have been largely resolved (ghosting is greatly reduced, although to a small extent it remains for FC3 aircraft). Ultimately, ED performed to its usual very high standard and DCS remains the king of aerial simulations!

Hi everyone! I report a graphic problem regarding the F-15E pilot. I attach a .trk file that demonstrates the problem. Visually it is quite ridiculous: the pilot seems to be suffering from convulsions, is he afraid of flying?!? F-15E tremors.trk

Hi everyone. Before 2.9 I had the same settings indicated in the first post from CommandT and with my i7 13700K+32GB RAM+RTX 3080 everything went smoothly. Now, with 2.9, if I keep these settings the game is unplayable (very slow and sometimes freezes). I have already performed the solution indicated by Flappie without any appreciable benefit, if I keep the MSAA 4x. Of course if I use DLSS everything goes much much better but... the price is a poor image definition and an annoying ghost effect on the HUD and MFD which make them unreadable. Even using only the DLAA, things are no better, in fact... they are worse than using only the MSAA 4x. I think this update is only appreciated by those who have the RTX 4090. I hope for a future update and, until then, I think I'll put DCS in the drawer.

Flappie thank you for the reply. I followed the instructions listed. With the 4x MSAA configuration (my previous great configuration with 2.8), the 2.9 remains unplayable. If I adopt the configuration with DLSS, the situation is significantly improved. I can play decently at 3840x2160 with DLSS balanced and 0.6 sharpening but... the DLSS is horrible: it mixes up all the details and the images have horrendous definition, furthermore there is an annoying ghost effect on all the indicators, especially the digital ones, which make them illegible. I remain sad.

Before the 2.9 update I was playing DCS at 3840x2160, MSAA 4x, SSAO on, SSLR on, and all settings at maximum (except chimney smoke density set to zero), everything was smooth as silk. Great! Then.... came 2.9. With the same settings as above I now see my past actions in slow motion! I'm really angry. My system is based on the i7 13700KF, 32 GB RAM, RTX 3080, DCS is installed on a 2TB NVMe pciexp4. P.S. DLSS sucks.

Hi CurrentHill! The Merkava 4M would be an interesting novelty for the Middle Eastern theater. Also because the Trophy system can finally be simulated quite well.

I finally solved the problem! What created the software conflict was one of the VSN mods (probably the one dedicated to the F-4 Phantom, but I uninstalled all of them). So, when you experience a graphical anomaly on the game's original aircraft controls, it is highly likely that you will need to uninstall a mod. The VSN F-4 mod had been installed for a long time and he had never caused problems, but update 2.9 must have generated a software conflict with the unpleasant result on Flaming Cliffs 3 planes. Thank you all for your kind attention.

Unfortunately the video does not provide the answer to why if I activate the AG mode (key 7) the pointer appears in the extreme upper part of the HUD (so much so that to see it I have to lower my head with the TrackIR). In the normal case (as in the video posted) the pointer appears in the center of the HUD (if I am looking straight ahead). The problem does not only concern the SU-25 but all Flaming Cliffs 3 aircraft. For example, I attach some .trk files of other aircraft that have the pointer completely off the vertical axis (extremely high in the HUD). Mig-29A nohud.trk Su-25T nohud.trk Su-33 nohud.trk

First of all, thank you again for your kind assistance. As you can see from the new file I attach, the problem is a little more complex. In fact, the pointer still remains completely at the top of the HUD and is not visible (unless you flatten your head at the bottom... quite inconvenient!). Did something happen in the update that affected the HUD view values? Su-25 nohud 2.trk

Hello and thank you for your kind attention! I attached the .trk file and I discovered that the AG pointer appears but, as you can see, it is so high up on the HUD that only by tilting your head forward very much can it be visible. So it's useless and the plane is unusable! Su-25 nohud.trk

After updating to version 2.9, the Su-25 lost AG mode as the pointer to use in conjunction with the laser rangefinder no longer appears on the HUD. I hope this problem gets resolved because the Su-25 is a lot of fun to use for CAS.

Hi everyone. One question: can naval units equipped with cruise missiles be resupplied with these missiles by naval transport units located nearby? Thanks in advance for your answers.

HI. The transition from pilot to WSO only serves me to activate the laser pod, I don't act on the flight controls. When I return to the pilot's seat the plane is losing altitude and the autopilot is disabled.

The autopilot is automatically disabled when switching from pilot to WSO and vice versa. It would be appropriate if this did not happen. I hope for the next patch.

Hi everyone. When you change seat (pilot/WSO) in flight and the autopilot is active, it appears that it is automatically deactivated. So it happens to me that going from pilot to WSO and vice versa, I notice that the plane has to restore the lost route and altitude. I ask if this is an intended effect or can it be fixed to keep the autopilot on all the time and disengage it when I want.

I apologize for the incorrect report: I misremembered the settings for launching the LGB. In fact, erroneously, in the AG delivery options, I selected: AUTO, RP single, N/T. This setting is incorrect for LGB. In fact, by selecting: AUTO, STEP, N/T, the bang is guaranteed! The laser codes are perfectly matched between bombs and TGPs. Again sorry for the procured not real alarm.