TeamSteelPawPaw

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!

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.

Since the latest update, when spawning in or recentering the camera FOV in the A-10CII, it centers the camera off to the right of the cockpit. It worked without issue the day before the update as well. Additionally, I use TrackIR but I don’t think that is the issue. There are no stray IR sources distracting the IR camera, etc. TrackIR works flawlessly with all my other modules currently and including the regular A-10C since the last update. I have tested this on Syria, Marianas, Caucuses, PG, Kola, and Afghanistan. All the same issue. This issue is present in old missions and newly created ones. This picture shows what it believes to be the “centered” position. Any help is appreciated!