Severity:High
(Low - quality of life, workflow optimization, rare enough to not impact production, etc…
High - critical but workarounds are available, important feature not working as expected, frequent enough to impact production
Blocker - prevents from working on the project, prevents from releasing the product)
Marketplace package name: FSReborn FSR500
Context: Selecting FSR500 aircraft, any livery.
Similar MSFS 2020 issue: None, works fine in 2020.
Bug description: First livery (Urban Gold when only using default liveries) dynamic registration colors appears to override all other dynamic registration color assignments for liveries below.
Repro steps: Aircraft selection, choose FSR500, select any livery and observe same dynamic registration colors as first livery.
This is a odd one, so as soon as an user installs custom liveries, the livery configuration set inside panel.cfg for the registration colors gets ignored resulting in all of them having the urban gold configuration.
@FlyingRaccoon we cannot replicate this with a local copy install via community folder, looks like this happens only with the streamed versions of the product…
We fixed something “similar” yesterday in our developing branch: textures referenced in .fx files where loaded with direct disk access function instead of going through the VFS. Trouble is, the VFS also handles the streaming part of packages which means those files were never found when streaming the package, while they were if the package was installed locally.
I’ll check if something similar may happen that would explain the issue reported here.
This topic has been automatically closed after 60 days of inactivity since it was marked as fixed.
If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.
