Version: 1.1.10.0
Frequency: Consistently
Severity: Blocker
Marketplace package name: N/A
Context: Liveries
Similar MSFS 2020 issue: N/A
Bug description:
Example:
Content of panel.cfg for livery
// Panel Configuration file
// ATS Antonov An-2
[VARIATION]
override_base_container = 0
[VPainting02]
size_mm = 1024, 256
texture = $RegistrationNumber
location = exterior
painting00=Registration/Registration.html?font_color=transparent, 0, 0, 1024, 256
Result in MSFS2020:
The dynamic registration is gone from the exterior, as intended.
Result in MSFS2024:
The registration still appears on the aircraft as set in the default panel.cfg:
Repro steps:
Have you looked at the livery.cfg files for this aircraft to see if this livery uses the [Panel_DynamicParameters] parameters? In MSFS 2024, a livery can alter the VPainting color parameters which is a preferred method to override the registration color than the panel.cfg.
https://docs.flightsimulator.com/msfs2024/html/5_Content_Configuration/CFG_Files/livery_cfg.htm?rhhlterm=panel_dynamicparameters&rhsearch=Panel_DynamicParameters
Yeah, I know about this, but the aircraft above is a 2020 version (Microsoft/ATS An-2) which is not in the new modular format.
Could this be the same as my bug here?
Version:
1.0.84.0
Frequency:
Consistently
Severity:
High
Marketplace package name:
Classic Aircraft Simulations Piper J3C-65 Cub
Context:
Using a configuration that has panel.cfg that tries to load WASM gauge from another panel folder.
Bug description:
Initially, I thought this was a WASM issue, repurposing and re-tagging post for with new info.
I use different ‘panel.X’ folders referenced in the aircraft.cfg to achieve different registration configurations. Within the panel.X config…
I’m not sure, but it looks quite similar indeed.
