Bug Report – F4U Corsair Radio Navigation (ARR-2 / C38 / C26) Not Working as Intended

[Ala13_Kokakolo]

Module: F4U Corsair
Issue: Radio navigation frequencies are only tunable via the C26 dial instead of using preselected channels in the ARR-2/C38 radio system.

Description:
In the current implementation of the Corsair in DCS, the navigation system does not behave as expected. I have set up two aircraft carriers:

• Carrier SE transmitting on 127 MHz AM

• Carrier SS transmitting on 121 MHz AM

I configured the ARR-2 as follows:

• Channel 1 = 127

• Channel 2 = 121

However, once inside the aircraft, it doesn’t matter which channel is selected via the ARR-2 — I can only receive navigation signals by manually tuning the C26 dial. The C38 control appears to have no effect at all.

This behavior is incorrect. According to documentation and intended system logic, the ARR-2/C38 system should allow the pilot to select a preset channel to tune to the appropriate frequency for navigation. Manual tuning via the C26 should not be necessary for receiving carrier signals when a preset channel is active.

Steps to reproduce:

1. Place two carriers emitting on different AM frequencies (e.g., 127 MHz and 121 MHz).

2. Set ARR-2 channel 1 to 127, channel 2 to 121.

3. Enter the Corsair cockpit.

4. Attempt to receive carrier beacons using C38 to select channel 1 or 2.

5. Note that no signal is received unless the C26 dial is manually tuned.

Expected behavior:
The ARR-2 system should allow tuning to preset channels (via the C38 selector), without requiring the use of the manual dial (C26) to receive navigation signals.

Actual behavior:
Navigation signals are only accessible through manual tuning with C26. The ARR-2/C38 preset channel system appears non-functional.

Example signals picked up via C26 (not ARR-2/C38):

• 190: AGA C → Agana airport

• 290: SS K → Carrier SS

• 560: SE N → Carrier SE (embarked)

[buur]

can confirm the bug.

[GTFreeFlyer]

SP or MP?

I have another post reporting this as a MP bug.  I did fly again last night on a MP dedicated server and again confirmed I could not get the Essex tones.  However, try the same mission in SP mode and it works.
 

I’m sure we’ll see a fix soon for this early-access module.  The radio is a work in progress because we did see the behavior change, unannounced, in the last DCS update that came about.  Small steps in the correct direction for this awesome module

[buur]

up to now only tested for SP

[Gretsch_Man]

Works for me in SP, but you have to make sure the C-26 is set to VOICE (default on mission start is CW). If the C-26 is left in the CW position, only the manual frequency is active.

[GTFreeFlyer]

2 minutes ago, Gretsch_Man said:

Works for me in SP, but you have to make sure the C-26 is set to VOICE (default on mission start is CW). If the C-26 is left in the CW position, only the manual frequency is active.

Ah yes, this is what I did as well, in SP.  Thanks for reminding me.  However, still couldn’t get it working last night in a dedicated server.  
 

Also, last time I tried in a locally hosted MP session, it worked only for normal spawn, not for dynamic spawn.  

Edited Tuesday at 09:57 PM by GTFreeFlyer

[Ala13_Kokakolo]

17 hours ago, Gretsch_Man said:

Works for me in SP, but you have to make sure the C-26 is set to VOICE (default on mission start is CW). If the C-26 is left in the CW position, only the manual frequency is active.

Yes. tested today. Iw works if the C-26 is set to VOICE (and the C-38 has to be in CW)