I’m in the middle of converting over a large livery project from 2020 to 2024 for the DHC-2 Beaver. I’m pretty much done with it save for one thing, the dynamic registration. My project uses a submodel I created specifically for said registration (with a lot of help from others). I made sure not to use the $ prefix as warned by the 2024 SDK in the panel.cfg.
The main problem is this: I’m using a different font here instead of the sim default. I’ve tried to navigate my way around changing some of the settings both in the panel.cfg and livery.cfg (font color, stroke, etc.). The behavior worked as expected at first out of the panel.cfg file. I thought I was on the right track with the livery.cfg, but it stubbornly refused to assign my font color for some reason.
This morning, I decided to make a fresh livery folder as a test to see what would happen. I decided to use the sim default’s registration.html to see if anything broke. It worked as expected, including my font color. I then decided to look at the other liveries I converted (same plane, livery scheme) that has its own panel.cfg with my custom registration.html, font, settings, etc., and THAT used the test livery registration setting!
This is telling me that the sim appeared to be using my test livery’s panel.cfg as a default and overriding the other liveries’ panel.cfg files. Is this the case? What step am I missing to fix this? Or is this a bug I stumbled upon?
Many thanks,
Gabe (aka Waffler11)