Marketplace package name: FSR500, TL3000, Sting S4 and anything in the simulator
Context: in flight
Bug description:
In MSFS 2020, when people installed liveries they configured to avoid having a registration number since most of them have a custom registration painted with the aircraft.
In MSFS 2024, this doesn’t work and people end up with the liveries looking like this:
Basically, they want the registration to not be there… and yet the users cannot do it, if they put the registration blank in the aircraft identification MSFS 2024 always sets one… and if they try to put a configuration in the livery panel.cfg to skip the dynamic registration, then it gets ignored:
They need some means to disable the dynamic registration like they did back in MSFS 2020… and this is not working anymore in MSFS 2024 since release, we tested with SU1 and the problem continues.
If I can expand on this further, I think I’ve tracked down the root cause for why dynamic registrations in 2020 aircraft aren’t being honored in 2024, and it has to do with the singular $ character. The $ is added as a prefix for registration material ID in 2020, but in 2024, per the SDK, it is not as it’s used to tell the engine it’s a collision material, seen here: panel.cfg
As a result, any 2020 aircraft addon that’s using the $ prefix apparently gets defaulted to the standard registration in 2024, which is Roboto in black. There are many livery painters, including myself, that has made extensive use of the panel.cfg to customize the look of dynamic registration, even using different fonts.
Could a tweak be made somewhere so that both 2020 and 2024 recognizes the registration files used? Anyone using a 2020 addon aircraft is stuck with the default and, while obviously just an aesthetic preference, it’s valued by many end users.
