Redfor Coalition AWACS gives an inaccurate BRA

[TeamSteelPawPaw]

Today I noticed that the Redfor AWACS’s BRA callouts are broken, while the Bluefor AI AWACS works fine. Redfor AWACS’s BRA callout range is off by over 100 miles and altitude off by 20k or more. The contacts bearing is called correctly thought.  
 

At I first thought this was a bug related to the new MiG-29 module because  loading into a Bluefor F-16 or F-18 had correct callouts from their corresponding Blue AWACS. But switching an F-16 to Redfor and the AWACS BRA would break again, or conversely, switch the MiG-29 to Bluefor and the callouts would be correct again.

This was tested on Syria, Germany, Kola, and Afghanistan with the F-18, F-16, and MiG-29 from cold start, hot start, and air start, but the behavior remained the same. Switch E-3, E-2, A-50, or GCI units made no difference either. Only changing coalitions fixed the AWACS. 

 

 

Edited 9 hours ago by TeamSteelPawPaw

[rob10]

4 hours ago, TeamSteelPawPaw said:

Today I noticed that the Redfor AWACS’s BRA callouts are broken, while the Bluefor AI AWACS works fine. Redfor AWACS’s BRA callout range is off by over 100 miles and altitude off by 20k or more. The contacts bearing is called correctly thought.  
 

At I first thought this was a bug related to the new MiG-29 module because  loading into a Bluefor F-16 or F-18 had correct callouts from their corresponding Blue AWACS. But switching an F-16 to Redfor and the AWACS BRA would break again, or conversely, switch the MiG-29 to Bluefor and the callouts would be correct again.

This was tested on Syria, Germany, Kola, and Afghanistan with the F-18, F-16, and MiG-29 from cold start, hot start, and air start, but the behavior remained the same. Switch E-3, E-2, A-50, or GCI units made no difference either. Only changing coalitions fixed the AWACS.

Attaching a track file from a session where this is occurring (short as possible, preferably on the Caucus map) or a copy of the mission will help the devs figuring out the problem.  There are way too many variables that may influence things and mess with trying to reproduce this from scratch.  You can save a track file from the debrief screen when you finish the mission.

[szcz13]

7 часов назад, TeamSteelPawPaw сказал:

Today I noticed that the Redfor AWACS’s BRA callouts are broken, while the Bluefor AI AWACS works fine. Redfor AWACS’s BRA callout range is off by over 100 miles and altitude off by 20k or more. The contacts bearing is called correctly thought.  
 

At I first thought this was a bug related to the new MiG-29 module because  loading into a Bluefor F-16 or F-18 had correct callouts from their corresponding Blue AWACS. But switching an F-16 to Redfor and the AWACS BRA would break again, or conversely, switch the MiG-29 to Bluefor and the callouts would be correct again.

This was tested on Syria, Germany, Kola, and Afghanistan with the F-18, F-16, and MiG-29 from cold start, hot start, and air start, but the behavior remained the same. Switch E-3, E-2, A-50, or GCI units made no difference either. Only changing coalitions fixed the AWACS. 

 

 

You sure your AWACS isn't just giving you distance and altitude in metric system? By your description sounds like it. Russians use metric system in aviation, unlike any bluefor nation

Edited 2 hours ago by szcz13

[TeamSteelPawPaw]

57 minutes ago, szcz13 said:

You sure your AWACS isn't just giving you distance and altitude in metric system? By your description sounds like it. Russians use metric system in aviation, unlike any bluefor nation

This never even crossed my mind. I did not know they did that based on coalition! I assumed it would stay with the selected 'general settings' measurement system. I do not fly much as red except for the Hind so I guess I've never noticed the change before! Thanks!

Please close!