This is the actual problem. Note when I hover over the Live Traffic - look at the info tag:
2 Likes
Thats HTML it should read “Tui Air [52]”
No idea why a plane code would use square brackets but FS2020 clearly cannot handle them
Well I flew this morning from LGW after installing the 26th August update and it’s still saying this nonsense.
Very disappointing.
Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons?
No
Brief description of the issue:
TUI flights ( reliably at EGTE ) have this format string as flight numbers - “Tui Air[52]” - presumably from Flightaware - which the ATC pronounces verbatim… “Tui Air and hashtag 91 52 and hashtag 93” - whch is quite broken. I don’t think filtering flight numbers would be terribly time consuming to implement.
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
Well, you’ll have to wait around at a UK airport for ATC to talk to a TUI flight, it might happen elsewhere. Perhaps just scan what live flights the live traffic system is injecting.
PC specs and/or peripheral set up if relevant:
Build Version # when you first started experiencing this issue:
Not sure, perhaps somewhere late 2021.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes
Provide extra information to complete the original description of the issue:
Still present in SU10
If relevant, provide additional screenshots/video:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Yesn’t as the situation somehow changed on SU11…
Provide extra information to complete the original description of the issue:
Instead of brackets and invisible characters like “hashtag” spoken the callsign for TUI flights are now somehow merged together. ATC now says the aircraft type followed by the flight number all together with “TUI” (see screenshot)
If relevant, provide additional screenshots/video:
Maybe the AI is messed up because the callsign is identical to the 3-character ICAO flight code.
Perhaps a resolution would be to re-define the callsign as "Twoey"
In EASA VFR flights typically use tail number only for example: G-ABCD which might latter be abbreviated to G-CD if no similar sounding tail numbers present.
IFR uses a callsign which often varies from the flight number.
Regarding IFR there is usually no mention of aircraft type other than in the initial clearance request from the pilot to ATC prior to pushback. Sometimes the arrival ATIS at busy airports advises pilots to mention aircraft type on first contact with radar/approach controller to assist ATC in handling separation distance.
This is still unresolved. Brackets are appearing in the callsign for TUI Airways, hence the “and hashtag ninety one” and “and hashtag ninety three”.
1 Like
Bug still there.
1 Like
Yeap. Just found it today.
Cheers
1 Like