Registration set to a 0,0 value in Panel.cfg is broken - Was fixed in Beta 3, broken again in Beta 4 & 5

2 tags are required - add them in the tag section next to the title above:

  • One for platform (ms-store, steam, xbox, or xcloud)
  • One for aircraft (start typing in your aircraft name in the tag section and pick correct option)

Feel free to delete this quote section after adding your appropriate tags.


ISSUE DESCRIPTION

Description of the issue: The custom registrations were fixed for me in Beta 3, and are now broken again.

Could it be that the beta4 updates to the registration logic (mentioned in the release notes) regressed to the pre beta3 code base?

Did you experience this issue before you joined the Beta? Yes, ever since 2024 launch.

If applicable, which aircraft is experiencing this issue: RV14A

MEDIA

[END OF FIRST USER REPORT]


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

1 Like

Now Beta5… 1.13.22.0

Changed, yes. Better, not really…

The interior reg seems to be stuck on either black or white for each sim session. It is not consistent which color is active. For 2020 aircraft, like the A36 or TBM850, this works for one but not the other, since the panel placard is black for the A36, and white for the TBM.
The sim ignores the color that is selected in the panel.cfg file.

I believe this is related Aircraft Identification Configuration Always Resets

Do you have the same issue if you follow the OP’s steps to reproduce it?
• no

Provide extra information to complete the original description of the issue:
• tested with the C172
@MapleBayaviator : the RV14A is a 3rd party aircraft right ?, can you reproduce the issue of as shown on your screenshot but with a 1st party aircraft ?
Title updated to better reflect what the issue is.

If relevant, provide additional screenshots/video:

As you can tell from the screenshot, this RV14 has a custom livery with a painted on registration. The default aircraft do not, so the problem does not occur.
This aircraft calls a panel.noregistration folder where the panel.cfg file has the registration set to a 0,0 value. This worked cleanly in 2020. With the SU1 Beta3 release, it started working in 2024 as well. That was great!
However, in beta 4 and 5, it stopped working again… Somehow, the code regressed to a pre Beta3 version…

With respect: the new title misstates the issue. It should say: “was fixed in Beta 3, and broken again in Beta4 and 5.”

1 Like

Thanks for the explanation, title updated based on that, hope it is clear now.
Maybe should be reported to the dev support forum https://devsupport.flightsimulator.com (if no report already exists)