Jump to content

When did Crew-->KY28 Encryption get implemented?


Recommended Posts

Posted

I've been using VoiceAttack for "Request Launch" (/+F8+F7) on the Supercarrier ever since its release, and to my surprise yesterday in the Tomcat it took me to a KY-28 Encryption option instead of telling the deck crew to get back to work. When was this added?

Posted

I'm pretty sure the F8 -> F7 being the option to change KY-28 encryption has been there since its inception, along with the option in the mission editor.

 

I'm not sure what the functionality of the system is in DCS, my guess is that it probably works in SRS, but in base DCS World it doesn't (and won't until ED's native voice chat becomes integrated with aircraft radios).

 

The test tone when keying PTT for 2 seconds does at least work (on current OB).

Modules I own: F-14A/B, F-4E, Mi-24P, AJS 37, AV-8B N/A, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk.

Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas.

System:

GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, NVIDIA GeForce RTX 4070S FE, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV.

Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.

Posted

When I flew the F-14B before the A's release, that option either did not exist, or it was not in the F7 slot of the Ground Crew comms menu. F7 was always "request launch" until the KY-28 encryption came about with the A and the NVG/HMD option came with the Hornet, getting slotted into F7 and FUBAR'ing my Voice Attack profiles. 

Posted

Hmm, not sure then, my guess is that it might not have been in the F7 slot. But I know the option was there from the get go IIRC.

Modules I own: F-14A/B, F-4E, Mi-24P, AJS 37, AV-8B N/A, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk.

Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas.

System:

GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, NVIDIA GeForce RTX 4070S FE, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV.

Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.

Posted (edited)

Is it possible ED shuffled the comms then, perhaps with the Supercarrier module? Because before the patch that included the F-14A, I flew the F-14B on the Supercarrier and my VoiceAttack command (F8-->F7) worked perfectly fine. After the patch that released the F-14A, the same VoiceAttack command (F8-->F7) went to KY-28 encryption. So someone changed something.....if you guys didn't change that then I guess that leaves ED as the culprit. 

23 minutes ago, IronMike said:

That existed since before release (and we havent changed anything on it ever since). 🙂

 

Edited by Nealius
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...