Tail number paint info in texture.config?

Questions & Community Discussions Art
1

Hey Asobo, any reason you can’t move the tail number paint info from panel.cfg
to texture.cfg? Seems like a more logical place for it, and seems to me it
would alleviate a lot of mod / livery incompatibilities. Pretty please???

2

Hello Rosco. The existing livery system actually already allows you to do
that. You just need to have your aircraft.cfg refence the base container and
then you can redefine the content of the panel directory just like what you do
for the texture directory. Just make sure to copy whatever wasm modules you
have in the original panel directory as inheriting those is not supported yet.
Hope this helps. Regards, Sylvain

3

@FlyingRaccoon So, what he’s implying is that he’d prefer NOT to have to
edit the panel.cfg file, because it causes problems later as panel.cfg files
change. So, if you include a panel.cfg file in your livery, you then have to
maintain the panel.cfg file as updates are made to the plane, and, if there’s
a relevant panel.xml file like there is in the C172 Classic, unless you know
the MUCH _less of a problem and we wouldn’t need to worry about the panel.cfg
file at all anymore. In particular, he’s talking about these sections

[VPainting01]
size_mm = 1024,256
texture = $RegistrationNumber
location = exterior
painting00=Registration/Registration.html?font_color=white, 0, 0, 1024, 256

[VPainting02]
size_mm = 256, 64
texture = $RegistrationNumber
location = interior
painting00=Registration/Registration.html?font_color=white, 0, 0, 256, 64

They don’t really have anything to do with the gauges in the cockpit, and
everything to do with how the plane is painted.

4

Thanks for explaining it somewhat clearer than I did!