Thanks @Chuck_Owl ,
This is like an early Christmas present. Some fun reading to get me through this cold snap.
Cheers!
Thank you @Chuck_Owl !
I was expecting a first draft, a smaller at first perhaps, but the doc is already a whopping 770 pages. Now it is time to really learn the Apache.
5 Likes
Edit Sorry,Posted Previously
Wow. That is truly amazing. Iāve honestly spent very little time with the Apache and despite intentions failed to do anything during my 2 weeks off that just ended, but now I see thisā¦Iāve got some READING to do!
2 Likes
Happy reading! 
7 Likes
9 Likes
6 Likes
I had forgotten the L was fire and forget with an internal radar. I always remembered it paired with the Longbow like it was SARH.
3 Likes
COMING SOON
In this DCS: AH-64D video, weāll discuss how to datalink with other AH-64Ds in a mission. This is done over the AH-64D radios and will allow you to send TSD points, tactical reports, or text messages. This is a very powerful tool to coordinate actions.
Letās first start in the Mission Editor where we can pre-configure our datalink networks. From the Helicopter Group window, the top portion remains unchanged. The bottom portion has new information from the Additional Aircraft Properties and Datalinks tabs.
Along the bottom portion of the Aircraft Additional Properties tab are two new entries for DATALINK. The first is the Datalink Originator ID that distinguishes data sent between networked members. Each AH-64D in mission should have a unique Originator ID. Below that is the Ownship Callsign, and like the Originator ID, this should be unique. Weāll see these later when setting up the network.
Before we discuss the Datalink tab, letās first look at the Radio Settings tab. This lists each radio in the AH-64D and the preset channel assignments for each. As you can see, each radio can have up to 10 presets.
On the Datalinks tab we have two sub-tabs: Settings and Network.
On the Settings sub-tab, we have 10 Presets, and each can have a unique Unit ID and Callsign. Weāll see these later in the cockpit. The primary frequency assigned to each Preset is defined in the drop down for each. Along the right side are check boxes to determine if the Preset takes part in the datalink network.
The Network sub-tab allows us to view, add, or remove AH-64Ds that will participate in a Presetās datalink network. As you can see, I currently only have myself, Chaos 11, and my wingman, Chaos 12 assigned to Preset 1, which is for āGunslingerā battalion. I can assign Presets 1 to 10 from the top row. If I wish to add other AH-64Ds to Preset 1, I can select Preset 1 and add them as a Group or as individual Units.
Note that this datalink is different from the ones used in aircraft like the F-16 and F/A-18, and they cannot exchange data.
Weāll first discuss setting up and editing the datalink through the COM page.
From the left MPD, Iāll select COM and we can see the Presets 1 to 10 listed along the right and left sides of the page with our ownship information in the center that includes the callsign CS11, for Chaos 11 and the datalink originator ID of 1 as we created in the Mission Editor. If I select ORIG ID, you can see that it displays the same information at the top left and top right. If wanted to edit this, I could select either one of these options and enter new designations for my own aircraft with the keyboard unit.
Back on the main COM page, if I select the first Preset, it then displays additional information regarding the Preset in the center, in this case the radio frequencies used by āGunslingerā battalion. If wanted to edit this though, I could select PRESET EDIT and select UNIT ID and CALLSIGN and enter new designations with the keyboard unit. I could also select V/UHF, FM, or HF along the top row to edit the frequency data that the Preset will use when tuned to the corresponding radios.
Selecting NET from the bottom row, I can display the aircraft assigned to this Presetās datalink network. As you can see, this matches what we set up in the Mission Editor, Chaos, and Bootleg flights. To add Saber flight, I simply select Member Directory, and select SR11 and press ADD and the same with SR12. We can now see that all six aircraft are assigned to Preset 1, Gunslingerās datalink network.
At the top youāll notice other options. If you select a network member and select Delete, it will remove that aircraft from the selected Preset. Selecting a network member and setting them as a Team member will allow you to send messages from that member through the COM page. If you set them as a Primary member, or PRI, you can send reports over the TSD and FCR page. Note that they are not mutually exclusive.
As mentioned, the Originator ID must be unique for each AH-64D. If you need to, you can edit you own by selecting Originator ID from the bottom of the main COM page as already demonstrated, or by selecting C/S, Callsign, or SUB at the top of the NET and entering a new designation for the network member that you have boxed in the network list.
NOTE 1. Due to complications stemming from our other businesses, we had to adjust datalink terms. In this case, Secure Modem Datalink (SMDL). This is all I will say on the matter.
NOTE 2. As always, these videos provide a preview of an upcoming feature to assist you in understanding a new feature. Later, it is quite possible that the feature will change, and the feature functionality has changed. As much as Iād like to, I lack the time re-record these videos.
NOTE 3. The next AH-64D datalink video will instruct how to transmit and receive datalink text messages, tactical reports, and points.
2 Likes
That one had me thinking, again. On no.
I left my request again for [what Iām calling] the āMark-1 Eyeball Data Linkā feature.
- Look at a Thing/Spot on the Ground (or [gasp] even an aircraft)
- Send an event with the object ID/coordinates
- Yadda, yadda, yaddaā¦cockpit visual recon mode does all this already - except tell me, mission editor/scripter, about the thing it actually found!
The āmathā is already in thereā¦or just give me the vector when I click something: My Eyeball ā Spot on the ground even. Iāll do the rest.
4 Likes
5 Likes
Iām all for realism and immersion, but at what point do we cross into the absurd? Who is going to send an in game text message through datalink when you can 1. use free text; or 2. just talk into the microphone that you probably have in front of you, because youāre talking to your team mates.
I donāt see the necessity here. Just my $0.02.
Free text obviously is just for chips & giggles. The auto messages, i see their use.
4 Likes
I obviously donāt understand war. This is to my good fortune of course. The Apache takes 18 steps written in triplicate to do anything. The Ka50 is the very definition of speed and simplicity. You can look at something and, with just a few presses, easily send that something to your 4-ship leader or to the rest of the team. It seems to my suburban New-Yorker-reading mind to be the perfect little ā80s bringer of death and mayhem. Yet the Ka50 was crap. Itās update, the Ka52, is still crap. And the Apache is a marvel.
5 Likes
Perhaps the real thing is not quite as snazzy as the one advertised in DCS 
5 Likes
Nooooo no. I refuse to believe that DCS is anything less than completely accurate.
7 Likes
Training, Tactics, and Procedures>Hardware
(Probably)
3 Likes