In the SU1 Beta, you can now select a custom registration and make it stick. 🙂

However, if you have a livery that has a painted on registration.. How do you prevent a registration from being superimposed on it?

In 2020, you could change settings in the panel.cfg file and/or select ATC_ID enabled=0

Is there something in 2024 that accomplishes the same thing?

Edited January 25, 20251 yr by Bert Pieke

Hmmm... no one? 🫢

Trying to figure this out too, but didn't get it yet. Best I could do was using ATC_ID enabled= "" and placing a dot in the the aircraft tail number inside the Sim (in Identification), but then I lose the ATC callsign which becomes just Cessna {trying with the WBSim C152).

4 hours ago, Alvega said:

Trying to figure this out too, but didn't get it yet. Best I could do was using ATC_ID enabled= "" and placing a dot in the the aircraft tail number inside the Sim (in Identification), but then I lose the ATC callsign which becomes just Cessna {trying with the WBSim C152).

Yes, I currently have an underscore as a placeholder... it does not look as silly as the dot on my RV14A.

Ryan B suggested I try his N120MB livery which actually worked a few times, and then went back to displaying the registration on the tail. 

17 minutes ago, Bert Pieke said:

Yes, I currently have an underscore as a placeholder... it does not look as silly as the dot on my RV14A.

Ryan B suggested I try his N120MB livery which actually worked a few times, and then went back to displaying the registration on the tail. 

On the 152 the dot is barely visible.

IDK what happened.  The first day I used SU1 beta it was working and now it only works on some planes but only sometimes.

Adding a null character between two quotation marks in the ATC ID line of the aircraft.cfg seems to work for the SWS RV14... but only for me and not two other people lol...

Someone else was able to clear out the dynamic reg on the FSR M500 but now for me the same "fix" doesn't work anymore.

Here's the aircraft.cfg opened in Notepad++ (I HIGHLY recommend this over the default notepad app) - click on the show characters button and then on the top menu: EDIT - Character Panel which brings up the column on the far right of my screenshot.  Put your mouse cursor in between the two quotation marks and double click the NULL insertion.  Save cfg.

 

You can see "FSR002" on top of TimHH's beautiful paint here... grrrr

 

38 minutes ago, Alvega said:

On the 152 the dot is barely visible.

Do you get a dot inside on the panel as well?  In my RV14 it is hard to ignore..

11 hours ago, Bert Pieke said:

Do you get a dot inside on the panel as well?  In my RV14 it is hard to ignore..

I do, but almost invisible because it's a white dot on a white background (near the bottom of the M letter).

Edit: Also tried the NULL method but it didn't work.

Edited January 27, 20251 yr by Alvega

23 hours ago, ryanbatc said:

DK what happened.  The first day I used SU1 beta it was working and now it only works on some planes but only sometimes.

Is there any chance the models are being stream updated rather than remaining locally installed?

On 1/27/2025 at 4:41 AM, Alvega said:

I do, but almost invisible because it's a white dot on a white background (near the bottom of the M letter).

Edit: Also tried the NULL method but it didn't work.

Guess what, we may have found a better way... If you choose the registration in the aircraft selection screens / configure,  you can enter Alt+255, enter and save.  This is an "invisible" reg..  Try it!

 

2 hours ago, Bert Pieke said:

Guess what, we may have found a better way... If you choose the registration in the aircraft selection screens / configure,  you can enter Alt+255, enter and save.  This is an "invisible" reg..  Try it!

Bert. ALT+255 is an ASCII space character.  Try it in a document instead of in an MSFS entry field. None of this has worked for me.  This deserves to be narrowed down. What is badly needed here is this:

Is this MSFS 2024 SU beta dependent?
If not:
Does this apply only to MSFS 2024 default aircraft, aircraft managed through content manager?
Does this apply to default liveries or just to addon liveries?
Does this then apply to liveries painted with reg numbers? to liveries painted with no reg numbers? Or to both?
Does this have any relevance to MSFS 2020 addon (purchased) aircraft?
If that relevance applies, does the source of purchase have any effect?  Marketplace vs third party purchase sites?

Feel like I have been chasing my tail.

Edited February 21, 20251 yr by fppilot

18 minutes ago, fppilot said:

Is this MSFS 2024 SU beta dependent?

Frank, as has been stated, this is my experience with SU1 Beta4.  It was working OK in the previous Beta3.

This is a 2020 payware aircraft that worked in 2020.

I am not claiming that this is anything more than a workaround.. but if you find yourself in my situation, you might just try it... Easy to do 🙂

44 minutes ago, Bert Pieke said:

Frank, as has been stated, this is my experience with SU1 Beta4.  It was working OK in the previous Beta3.

This is a 2020 payware aircraft that worked in 2020.

I am not claiming that this is anything more than a workaround.. but if you find yourself in my situation, you might just try it... Easy to do 🙂

Thanks Bert. The sum of that has not been so evident as topic has progressed and matured.  Have you been successful with more than one model? And what was the source and age of those your had success with?  Just wish to narrow this to what works for the masses. No contest here.  Just desire to sculpt expectations of all who read.  Fair enough?  Great respect here, as I hope you realize.

9 hours ago, Bert Pieke said:

Guess what, we may have found a better way... If you choose the registration in the aircraft selection screens / configure,  you can enter Alt+255, enter and save.  This is an "invisible" reg..  Try it!

Thanks Bert. Does the ATC call you by the correct registration when using this method? I will try when I have some time.

I was chasing my tail because I am not on the beta(S). Prior to yesterday the last previous mention of betas in this topic was back on January 27th, and I missed that as I came in much later.  My bad.

Edited February 21, 20251 yr by fppilot