+1 For saving callsigns for each aircraft/livery. This post is 4yrs old and still no way of the sim remembering that a Delta livery is not Lufthansa in ATC.
Should not have to edit .cfg files as a workaround. 4yrs later. Asobo: fix the little things, they are most annoying.
I can see the benefit for some users and would support it provided we get the option to have a common call sign for all A/c. I use ATC but don’t really focus on all the calls until my regular call sign catches my attention.
I know I could go in and enter it for each a/c but the current system works well for me so please give us the option if this change ever gets adopted.
Just picking this up as it hasn’t been implemented in 2024 either. Since the aircraft reads the default tail number from aircraft.cfg in 2020 if none is entered via GUI, I guess the system remains the same for 2024. So why should the sim not be able to either write to aircraft.cfg or - just as the Hobbs meter reading - save it somewhere else?
Plus: given that we now have per-aircraft control profiles, that would be a nice and welcomed addition.
Towing this topic in, if I configure e.g. the VL3 with my personal PH- tail number in the menu, start free flight and before I am on the parking spot, I open the efb and even put the tailnumber in there. When I load on the spot, there is a different PH- tailnumber on the plane.
Unfortunately this is by design. MSFS now displays a random tail number based on the format used by the country of the departure airport. Although it’s definitely a bug that entering the tail number when selecting an aircraft is ignored.
Another bug is that MSFS will now always display a dynamic tail number on any aircraft that has a dynamic tail number. Any livery that needs to match a specific tail number font/location needs to disable the dynamic tail number, to prevent 2 tail numbers appearing. Many airline liveries need a fixed tail number to accurately replicate the livery.
Unfortunately the poorly implemented new dynamic tail number process also stops methods used to hide or disable the dynamic tail number. So what works in 2020 doesn’t work in 2024. This effectively blocks a whole swag of custom liveries from ever being used in 2024.
And the new dynamic tail number has one last casualty. In the past livery creators could recolour the dynamic tail number to match the livery by editing the panel.cfg. This also no longer works in 2024, rendering another group of liveries unsuitable for use in 2024. Based on information in the SDK it looks like aircraft designers may be able to fix this problem though.
I think a quote from Jurassic Park is pertinent here in relation to the success of the new dynamic tail number. “They were so preoccupied with whether they could, they didn’t stop to think if they should”.
No, the format is not how it works. Only the nation code is displayed correctly, D-3NOV is not a valid tailnumber in Germany at all. On the C182 I should have D-Exxx, for example. So even in there, there’s either poor design or quite a bug.
I’m going to look into the VFSProjection and try to find out more later on (or whenever it becomes available.
Afterthought: When I managed to get into the sim on Wednesday, my 208 had the tailnumber I entered. Could that be a newly added bug, though?
Edit: I just noted that the wrong tailnumber posted above was saved to the field where you’d enter it. So something must be wrong on saving/reading the user entry.
I do not know if it happends because I just thought of it , maybe someone already noticed it: does the plane wears down in freeflight? Getting random tailnumbers should give a brand new plane every time. What I would expect is that using the same tail number with the same type of plane wears it down.
Aircraft registrations should at the very least be saved for your owned aircraft in career mode. At the moment I get a new registration every time I take a new mission…