Search the Community
Showing results for tags 'a-10c 2'.
Found 6 results
-
Ciao Stavo verificando quanto moduli ED ha ancora in EA e mi sono accorto che l'A-10C Tank Killer II non è tra questi ma manca ancora la radio in oggetto. Ora mi chiedo ma quanto è difficile sviluppare questa benedetta radio? perché ci vuole cosi tanto? Non riesco a capire cosa ci sia realmente dietro a questi sviluppi.... da fuori sembrerebbe semplice e banale copia incolla per genere il menu comandi che funzioni sulla frequenza impostata e che quindi mezzi che usino la stessa frequenza possano interagire. Ma evidentemente la mia è una estrema semplificazione... e questo mi sfugge....
-
>>Preface<< "This mission has been edited to have the possibility of using three different and most commonly used modules on the same Syria map: F-18C, F-16C and A-10 II". >>Briefing<< We are in the theater of war of the Sirya, it is of fundamental importance to hit some strategic objectives through a "Strike and CAS" mission. If we decide to fly an F-18C or a Viper, we will have the exact same objectives, namely an enemy Command and Control Center and a SCUD missile post inside a military base south-east of Aleppo. Group A-10 II will have a different target, CAS mission northeast of the Aleppo position. The objective is to hit an enemy heavy gun emplacement with the help of the JTAC. During the mission, however, information that may be useful for the success of the mission will be displayed. In flight there will also be other packages managed by the AI, so pay attention to any type of information while browsing. This is a simple Strike and CAS missions for all aircraft listed. Each flight package has its WPs available until the target is reached. It starts from Incirlik airport, runway 23 authorized with exit on WP 02 Gate Venus. Once at WP 03, indicated as AAR Minesota, a refueling with the available Tanker must be carried out before arriving on the target area. The mission is accomplished the moment you receive the notification that the targets have been hit. I recommend that you follow all the procedures, as well as being an operational mission, it can also be useful for training. Attention to Taftanaz Area, area is restricted due to the possible presence of enemy surface-to-air missile positions. Download file.miz and please leave a comment if you liked the mission. Thanks
-
Hey all, After the last update the A-10 has had some bugs it seems. Bugs: On startup there are errors including: IFFCC fail CADC fail GCAS fail Left Gen fail Hud fail This seems to be online only in hot and cold started planes. This was with me and 2 others in my group -
I was wondering if anyone could help me out with A-10C II not showing up in the "Missions" category. I see it in Instant Action, Create Fast Mission, Campaigns, etc pretty much everywhere else except for the Missions folder. This is the Update purchased in Steam. Any advice would be appreciated. Thank you, John -
Does anyone know how to change what programs the CMSC selects for a given threat indication when in Semi or Auto mode? To be clear, I know how to edit the CMSP chaff/flare dispense sequences in the cockpit and the defaults in the "AN_ALE40V_params.lua" file, but I want to change the CMSC program selection criteria. As it stands, these are the programs selected when exposed to the given threats: PRGM A: SA-6, SA-8, ZSU-23-4 RWR indications PRGM B: SA-10, SA-11, SA-15, SA-19, Roland, Patriot RWR indications PRGM D: SA-2, SA-13, HQ-7, Rapier RWR indications PRGM L: SA-3, Hawk RWR indications PRGM M: MWS detected launches (like MANPADS) without a correlated RWR warning (ie, if you are pointing your belly at an SA-13, where the Missile Warning System detects the launch of a missile, but is in a blind spot of the Radar Warning Receiver so it doesn't detect the SA-13's radar, it will dispense PRGM M, whereas if the aircraft was circling the SA-13 site with the SA-13 radar in the field of view of the RWR sensors, it would dispense PRGM D if it detects the SA-13 radar prior to the MWS detected launch of an SA-13 missile) What is troublesome about this is that all the relatively recent additions to DCS, such as the SA-2, HQ-7 and Rapier, seem to default to program D along with the SA-13, and these are all quite different types of threats (not that you need chaff to outmaneuver an SA-2 missile, even in an A-10). In fact, these threats aren't even listed in the "CMSC_param.lua" file under any CMSC program, whereas all the threats for programs A, B and L are. I tried adding or moving various threat lines to programs A or B or creating a new program in the "CMSC_param.lua" file. However, when I save, and close the file, then start DCS and test, the programs still respond as before. The reason I want to tailor these programs is to make the programs more efficient for each threat, and avoid wasting countermeasures unnecessarily. For example, I could set up PRGM D to expend both a chaff program that works for the HQ-7 and Rapier, and simultaneously expend flares for the SA-13, but now I'm expending more countermeasures than are necessary regardless of what threat I am engaged by. Any suggestions or insight would be appreciated. Thanks.
