Maybe I am confused, but is it possible to change the visual registration on an aircraft by editing the panel.config file? Does altering anything in the file area below do it? Thanks a lot!
My first day with the 172 (Thank you Indigenous People’s Day) and I want to change the registry to match the old Cessna 150 I flew back in 1966…I have read the “how to convert a livery” section, but I wanted to double check before I mess with the panel.cfg file… Where should I place the new registration in the section(s) below? Thanks a lot!
[VPainting01]
size_mm = 256, 64
texture = $RegistrationNumber
location = interior
painting00=Registration/Registration.html?font_color=0xecebec, 0, 0, 256, 64
[VPainting02]
size_mm = 1024, 256
texture = $RegistrationNumber
location = exterior
painting00=Registration/Registration172X.html?font_color=0xecebec, 0, 0, 1024, 256
;painting00=Registration/Registration.html?font_color=0xecebec, 0, 0, 1024, 256
The Registration on those planes that use the Asobo Registration function are tied to “decal” geometry on the plane.
As long as the changes you are trying to make to the Registration are within the bounds of that decal, yes, you can make changes to the Registration with panel.cfg changes. Assuming you are using one of the default fonts, you can change the color and size (smaller) and position (within the decal).
Or, there are ways of using your own font by adding your own html_ui section (make sure to properly separate the Registration code from the default version as seen by the VFS), as long as what you’re doing still resides on the decal geometry (that white space you see on AI planes… Why, oh, why after 3 years hasn’t Asobo fixed this to make that geometry transparent… SMH so hard).
A while back, this functionality was broken by Carenado, who just copied the html_ui code, so their code overrode the default html_ui code, and then they didn’t update their code to match changes that Asobo made to allow some font manipulation (color I think it was), so they effectively broke the Registration functionality. They did eventually fix that, though, and made the html_ui code for their planes on its own path so it didn’t affect other planes. But you still might end up being befuddled by other developers who incorrectly copy code and don’t change it appropriately so it doesn’t overwrite the default code through the VFS.
To that point, if you are trying to do this, you should check that the plane you are trying to edit doesn’t have its own html_ui code, at which point you’ll have to check it to make sure it will handle the changes you want to make.
Seems like it should be easy, right, I mean the stuff is right there to edit… lol 
Unfortunately, you’re constrained by whatever css was actually implemented here.
Thanks for the extensive explanation! I think I will stick with the original registrations for now…I can just see myself screwing up the entire simulator! Thanks again…
My custom N number shows on any aircraft I use. This is where I set mine. But I might not understand fully what you’re asking.
I interpreted his request as asking if he could change its visual representation, i.e. colors, font, etc…
I could be wrong, then your answer definitely works if he’s just trying to change the value, though he could also have done that in the livery of his choice in the aircraft.cfg file by changing the atc_id= value to make it permanent and not affect other aircraft.
1 Like
