My earlier submission on this topic was closed and merged with a bug report that tail letters were missing from default aircraft post SU12. My subject matter is entirely different. Default registration letters do appear on aircraft that I select but they are default registrations whereas prior to SU12 my “personal” registration G-DAVE appeared automatically on all GA aircraft that I selected. Post SU12, if I want to use G-DAVE I have to go into ‘Customise’ in the aircraft selection panel and enter that registration. I also want to know why, if I enter a call sign in that option, it does not get used by ATC.
"Since as long as I can remember I have had the same registration and call sign for all of my GA aircraft, I entered it, somewhere, once and it stuck - it was there for every aircraft without me doing anything. I never did manage to assign a call sign that was different to the ac registration but for GA that’s how it is. Since SU12 it seems that I have to ‘customise’ every aircraft that I select to fly each time I chose to fly it. Additionally, I have started to fly the Hawk T1 and I thought, being military I would enter the proper tail letters/numerals for the aircraft and assign myself a mil style call sign. Doesn’t work at all
Hi XR219and thanks for responding, but I don’t believe that it is related at all. Firstly, the bug report specifically references ‘stock’ aircraft and I don’t use stock aircraft. Secondly, the bug report is for aircraft spawning without any tail letters at all and aircraft that I use do not do that, unless I go into the customising option and insert my own registration letters/tail number, aircraft spawn with the developers letters/numbers. Thirdly, the bug report doesn’t raise the issue of call signs not being recognised or used.
Incidentally, XR220 was briefly in my charge whilst I was based at RAF Cosford and responsible for the maintenance of the RAF Cosford Aircraft Museum (at that time official The RAF Museum Reserve Collection) aircraft. In that time I was able to access a host of historic aircraft, some absolutely unique. A great experience and privilege that I will never forget.
Prior to SU12, there were always times where ATC did not (at first) use the callsign I had put in MSFS as my default, but then, later, ATC would magically switch to using that callsign.
The Callsign label on the Plane’s Panel was always correct – ie what I had put into MSFS as my default Callsign.
Now, since SU12, what ATC seems more often to Ignore my set MSFS callsign, and use the callsign in the plane’s config file, sometimes never changing to my MSFS personal set default.
A definite change & degradation in SU12
Hopefully, now these callsign issues have got worse, Asobo may take a look at this and make a permanent fix, including looking at Tailnumbers being passed over to planes in Multiplayer, and displayed on the plane.
