15 minutes ago, bcip said:

The panels I'd like to be displayed all come with related script files for the associated airplanes with programmed buttons and knobs. From my observation, as long as the panel is displayed, its respective programmed functions also works w/o any problem!

That is not what I am talking about. The Gauge system in AAO has been designed to handle multiple different layouts of gauges, not just the one. The topic is displaying the gauge, not operating it. The XT Panel is just a very special case of gauge. You are expected to create a Layout for every (group of) gauges that you want to display for a certain aircraft. AAO will then associate the layout with the aircraft and load the gauge when you load the plane. 

If the config files of AAO have been changed in some way, the gauge will no longer display "just like that". The app expects a gauge Layout that it can load with the plane.

Edited November 7, 2025Nov 7 by Lorby_SI

"If the config files of AAO have been changed in some way, the gauge will no longer display "just like that". The app expects a gauge Layout that it can load with the plane."

I guess the config files of AAO should be the same for the two versions of the updates. It's a bit weird that the additional files of the latest update would make those gauges (which are not touch or altered at all) not able to be displayed. One observation is (under the faulty situation) that the WEBFIPs could display blank panels for the 4 sizes while the Desktop FIPs couldn't display any of the 4 panels.

9 hours ago, bcip said:

It's a bit weird that the additional files of the latest update would make those gauges (which are not touch or altered at all) not able to be displayed.

There are no "additional files" in an AAO update. And an update never touches your local config files in any way. Only you or your computer can destroy them, which can happen for example when the PC crashes while AAO is running.

We have both checked again, neither Funatic nor me can reproduce this issue. Besides, he is part of the AAO testers who always get every new iteration of the development version of AAO in advance. If there was an issue with the app, he would catch it early on. 

This problem seems to be specific to your computer somehow. Which makes it impossible to diagnose. My personal guess is that there is an error somewhere in your specific gauge configuration (= the functionality that you put on it) which the previous AAO version tolerated but the new version does not. But I can only guess at this point, not really advise.

- Check the AAO logfiles of those runs where the gauge wasn't displayed. 
- Make sure to download the latest version of the gauge.
- Reinstall both the AAO and the gauge, in that sequence.
- Make sure to create backups of your local files.

Edited November 8, 2025Nov 8 by Lorby_SI

6 hours ago, Lorby_SI said:

There are no "additional files" in an AAO update. And an update never touches your local config files in any way. Only you or your computer can destroy them, which can happen for example when the PC crashes while AAO is running.

We have both checked again, neither Funatic nor me can reproduce this issue. Besides, he is part of the AAO testers who always get every new iteration of the development version of AAO in advance. If there was an issue with the app, he would catch it early on. 

This problem seems to be specific to your computer somehow. Which makes it impossible to diagnose. My personal guess is that there is an error somewhere in your specific gauge configuration (= the functionality that you put on it) which the previous AAO version tolerated but the new version does not. But I can only guess at this point, not really advise.

- Check the AAO logfiles of those runs where the gauge wasn't displayed. 
- Make sure to download the latest version of the gauge.
- Reinstall both the AAO and the gauge, in that sequence.
- Make sure to create backups of your local files.

I've checked the log file and found to have the following errors when FIPs couldn't display:

"06/11/2025 11:37:34.864 : Exception received: 3 from send id 24 errloc 1
06/11/2025 11:37:34.864 : Exception received: 3 from send id 25 errloc 2
06/11/2025 11:37:34.864 : Exception received: 3 from send id 26 errloc 3
06/11/2025 11:37:35.304 : MW: Exception received: 32 from send id 162 errloc 162
06/11/2025 11:51:20.844 : SH: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. in SimConnect. Cessna 152 Asobo
06/11/2025 11:51:20.902 : SH: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. in SimConnect. Cessna 152 Asobo
06/11/2025 11:51:20.968 : SH: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. in SimConnect. Cessna 152 Asobo
06/11/2025 11:51:21.69 : SH: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. in SimConnect. Cessna 152 Asobo
06/11/2025 11:51:21.135 : SH: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. in SimConnect. Cessna 152 Asobo"

For using previous update (V44), the first 4 exception still received but not those "Attempted to read or write protected memory. This is often an indication that other memory is corrupt. in SimConnect. Cessna 152 Asobo"

Does it suggest my SimConnect got problem or corrupted?

 

3 hours ago, bcip said:

Does it suggest my SimConnect got problem or corrupted?

No, this is all pretty normal. The Exceptions "3" are created by AAO on purpose, the rest is just a momentary glitch that happens from time to time (too many new variables added to the interface at almost the same time). 

Edited November 8, 2025Nov 8 by Lorby_SI

Lorby, appreciate for your time and effort for the support. The cause of this fault was definitely done by myself during my PC lockup. I am glad that I still be able to use the XtouchMini panels using the AAO V4.54. Thank you!

8 minutes ago, bcip said:

Lorby, appreciate for your time and effort for the support. The cause of this fault was definitely done by myself during my PC lockup. I am glad that I still be able to use the XtouchMini panels using the AAO V4.54. Thank you!

I sometimes have the problem that I also think that a newly added gauge doesn't display. In reality it is just off screen - all I have to do is to press "Reset" on the gauge panel and it jumps back into view.