Context: FSR500 When editing or mounted from Community or in flight?
Bug description:
All G1000 units are failing to render at all, they remain dark not matter what. After hours of testing, this is due to the reversionary code inside panel.xml which contains this code:
Taking this code out allows the units to start working, however then the reversionary code stops working and when you click the Backup Display button the reversionary code to make the MFD display as PDF stops to work.
We cannot take this out either in MSFS 2020 to provide compatibility in MSFS 2024 since the reversionary code then stop operating in MSFS 2020 as well.
Repro steps:
Load the Cessna Caravan from MSFS 2020 inside MSFS 2024 via community folder and you guys will see it happening to.
are you using MSFS based systems? In panel.cfg, conficurations is pointing to MSFS folder sructures if you are using them. You may have to edit structures to match MSFS2024 folders. I did change those values and did get Kodiaks PDF and MDF working with previous Alpha .
Let’s allow Asobo to taclke the problem guys. We cannot submit 2020 versions with fixes to market place to show only in MSFS 2024… big problem… so wherever is causing this render is a bug that will need to be adresed in the CORE of MSFS 2024 so a MSFS 2020 aircraft copied inside the 2024 community folder just works as promised by Microsoft.
If now we all need to change our 2020 projects and submit changes, you will find over 1000 3rd party developers pushing changes for market place all simultaneously and trying to get those up before 19th of Novemeber… totally impractical.
One thing is converting our projects to 2024 standards and compiling inside MSFS 2024, and another is a Project from 2020 that supposedly needs to work in backwards compatible mode.
not matter what you do, even WT V2 will not render due to the bug on reversionary mode… see the report… if you take the panel.xml Systems_AS1000 tags they will render… but you will not have any reversionary code active.
It might be the model part or screen material name that is changed.
My LearFan that uses the Beech KingAir screens (new WT G3X) isnt working in 2024. They use the G1000 material name for the base for the instruments to run on. It might be changed.
Mine do appear dark. I have attached @SimbolFSReborn 's code to brighten them up, but they are still a little dark. I might see what I can do to see if they can be adjusted/brightened up some more.
I tested in the night and day. Also note that the AUX instruments on far left are bright (normal) while the G1000’s are dim.
On this one, note the AUX gauages, far left. Note, this is with the @SimbolFSReborn fix in the model XML coding.
I am going to look through the code and see if it has an adjustment written in the code. Doesnt make sense that the brightening code isnt doing the trick.
The issue with avionics not being displayed at all when the code snippet related to reversionary mode is present, as reported in the first post, has been fixed in 1.0.86.0.
All issues with instrument emissive being inconsistent need to be reported separately as they can have different causes.
Just recheck in 2020 and make sure its all running proper.
Also, I may have found a bug. In 2024, boot into a free flight, bring up the weather page in the sim and adjust your time slider and note the lighting on the instruments to see if they go really dark at certain parts of the day.