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
Which aircraft are you using that experiences this issue?
Tested with Bonanza G36, Cessna 172 G1000, and Savage Cub. Could be more, but after three aircraft, I stopped testing.
Brief description of the issue:
Would really like someone else to verify that this is happening with them. Please see the detailed steps.
When spawning in mid-air, ATC calls you by the generic callsign ASXG or ASXGS even if you have chosen to customize your callsign.
Provide Screenshot(s)/video(s) of the issue encountered:
This is a very boring video. Just look at the beginning frame and notice that I have a custom tail number and callsign in there. Then skip all the way to the end and notice that the pilot is calling themselves “Savage ASXGS” instead of the custom callsign I gave it in the first frame (note: I deliberately turned the engine sound down to 0 to make it easier to hear):
Detailed steps to reproduce the issue encountered:
- Go to the World Map. Choose one of the three aircraft I mentioned above (Bonanza G36, Cessna 172 G1000, and Savage Cub – again, might happen with all aircraft, but this is what I tried it on).
- Choose a custom tail number and callsign.
- Start a flight in mid-air. (This bug does not surface when spawning at an airport. I only observed it while spawning in mid-air.)
- Open the ATC window and request flight following or make some other request of ATC.
Expected result:
The pilot addresses themselves using the custom callsign.Observed result:
The pilot addresses themselves using the callsign “ASXG” (for the Cessna 172 G1000 and Baron G36) or “ASXGS” (for the Savage Cub). See video, above.
PC specs and peripheral set up:
N/A
Are you using DX11 or DX12?
DX12
Are you using DLSS?
No
For anyone who wants to contribute to 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:
Are you using DX11 or DX12?
Are you using DLSS?
If relevant, provide additional screenshots/video: