not planned or correct for version Fire support via digital messages

[FalcoGer]

The apache has a comprehensive communications suite. MFD formats allow the selection of targets, both from points as well as from the FCR to be sent to artillery for a fire mission.

I would like this to be tied in with DCS in such a way that artillery fire missions are generated for the selected artillery unit on the selected fire support element (FSE). Artillery should be selectable as the FSE if it has that option set in the mission editor, perhaps as a route special option to be available for unit/group/coalition datalink tasking.

In practice this is hardly used, but in DCS it could tie in nicely.

Edited July 12, 2022 by Raptor9
Rule 1.16 - citing specific features from restricted documentation

[FalcoGer]

In the A10C, a mission from the JTAC is sent over the datalink system to be indicated with a red triangle on the TAD. A similar system is in place for the Apache. The Apache is able to be the recipient of an airfire mission for remote laser guided missile shots.

I would like this system be used for JTACs capable of tactical internet datalink or fire support net datalink.

[Raptor9]

There is a misunderstanding on the use of these systems and datalink types and how they apply/don't apply to the functions you are describing in the cockpit. This functionality doesn't work how you think it works.

[DmitriKozlowsky]

For Combined Arms and AH-64D , allow AH-64D crew to call for artillery fires.

If MLRS FDC friendly unit is available , allow Apache crew to call for indirect fire. Most useful for air defense threat suppression. Contact could be FDC itself, mission tactical commander, or JTAC as relay. Granted that Apache itself is flying artillery itself, it is vulnerable to air defense.

[FalcoGer]

10 hours ago, Raptor9 said:

There is a misunderstanding on the use of these systems and datalink types and how they apply/don't apply to the functions you are describing in the cockpit. This functionality doesn't work how you think it works.

How does it work then? The way I understood it is that some observer (perhaps an oh-58) is sending a air fire request message to the apache. the apache then can accept the mission, gets a target. Messages are sent back and forth regarding the different stages of engagement as outlined in [Rule 1.16]

Where did I go wrong?

Who can receive which messages with what DL protocol is outlined in [Rule 1.16]

In this case Tactical Internet and Fire Support networks are available on the FM radios, both of which may be used for the airfire mission messages. The apache may only receive requests and the assosiated messages from the observer and may only send messages meant for the observer, meaning it's confined to the shooter role.

Edited July 12, 2022 by Raptor9
Rule 1.16 - citing specific pages/procedures from restricted documentation

[FalcoGer]

i made the same request yesterday

 

[Kharrn]

Am 12.7.2022 um 01:43 schrieb FalcoGer:

The apache has a comprehensive communications suite. MFD formats allow the selection of targets, both from points as well as from the FCR to be sent to artillery for a fire mission.

I would like this to be tied in with DCS in such a way that artillery fire missions are generated for the selected artillery unit on the selected fire support element (FSE). Artillery should be selectable as the FSE if it has that option set in the mission editor, perhaps as a route special option to be available for unit/group/coalition datalink tasking.

In practice this is hardly used, but in DCS it could tie in nicely.

 

get some friends and play MP with CA. Some can control n shoot the arti or do JTAC or whatever, while you fly/gun.

Use radio mods or inbuild VOIP for voice transfer of "data".

hf

[FalcoGer]

CA is rather lacking. It would be nice to be able to call for fire without extra people.

If you have extra people you can still do it via voice. But the AI won't listen to you.

Edited July 13, 2022 by FalcoGer

[DmitriKozlowsky]

20 hours ago, FalcoGer said:

CA is rather lacking. It would be nice to be able to call for fire without extra people.

If you have extra people you can still do it via voice. But the AI won't listen to you.

 

In Mission Editor there is a FAC task function that, in effect , turns a unit into JTAC. ED could consider adding FO(forward observer) and/or FiST(Fire Suppourt Team) in same manner. In CA there is MLRS FDDM vehicle. SP howitzers, like M109A6 Paladin and towed artillery have Fire Direction Center that get fires calls from FO and FiST, prioritize them, and distribute fire missions to individual guns in batteries. A U.S. Army Stryker Brigade or armored cav brigade combat team would have one or two M109A6/7 batteries as organic assets. Lighter infantry teams would have towed M198 or M777 gun batteries. Higher level division or Corps level would have MLRS as organic fire support. Attack helicopters are a division or higher level assets. As are JTACs which are assigned as needed to advance units. MLRS and howitzer batteries main missions are counter battery fires, forward air defense SEAD suppression, followed by direct support of friendly units.  Enemy MLRS, howitzers, heavy mortars, and forward short range air defense are priority targets for friendly , then enemy maneuver elements such as armor, mech, and infantry.