Description of the Bug:
The ATC callsign numbers issue from previous versions was fixed in 3.0.4. So e.g. F90552 sounds like FRONTIERFLIGHT 0552 now and no longer sounds like FRONTIERFLIGHT 90552.
However, I noticed that ATC callsigns that have been manually edited to make them realistic have lost the real callsign now. TK8 (IAD-IST) is suddently Tango Kilo 8 instead of Turkish 8 and MH1 (LHR-KUL) is now Mike Hotel 1 instead of Malaysian 1. S
Steps to Reproduce:
Changed callsigns of British Airways flights at LHR from 4 to 3 digits. Result: call sign SPEEDBIRD
Changed callsigns of British Airways flights at LHR from 3 to 2 or 1 digit. Result: call sign Bravo Alpha
I’ve experienced this with only one callsign (up to now) at GRU, which was Turkish Airlines being called Tango Kilo after I changed it back in 3.0.2 with no issue
Edit: more callsigns being affected mainly E planes.
Can confirm this happens on Android as well. I like to renumber my real-life contracts and a lot of airlines have flagship routes to LHR so this is quite a prominent issue. For example, United Airlines UA19 is the route between LHR and EWR but indeed with only 2 digits, the callsign is replaced by the ICAO alphabet (Uniform Alpha 1-9er instead of United 1-9er)