bcip

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'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?

"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.

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! Let's wait and see what Funatic's response first. " buttons and rotaries light up on the gauge as I operate them, the slider is moving too." even those panels are not displayed, the buttons and rotaries light up in response to the respective physical XTouchMini, however, the programmed control functions were not working at all ( seems like the related script file are not loaded)!

Hi Lorby, You might be interested to know that the AAO latest update (LorbyAxisAndOhs_4_55_b26) might somehow affect the virtual XTouchMini virtual FIPs not displaying. This morning, I reloaded this update to my PC and found the old symptom occurred again. The XTouchMini FIPs simply disappeared for any plane loaded (even in offline mode). I double checked it by re-loading the earlier version LorbyAxisAndOhs_4_54_b08, the panels came back again. I just want to seek you view on this whether there are any files in update _4_55_b26 related to XTouchMini or scripts for third parties on their custom panels. I still suspect some files in my installed directories had corrupted which are required in the latest update for displaying the 3rd parties' FIPs. Thank you for your attention! I've also checked with Funatic to see how he look at this issue. Have a nice weekend!

Thanks

Hi Lorby, I am happy to report my Desktop FIPs could now be displayed. I reinstalled the LorbyAxisAndOhs_4_54_b08 update and all virtual panels (L;M;S & XS) are now operations as they should now. There must be some files in the version(LorbyAxisAndOhs_4_54_b08) I had corrupted in my last force restart! Just 1 more question, could I re-install version LorbyAxisAndOhs_4_55_b26 after this recovery?

No error message reported by AAO. The strange things are all the AAO default panels could be displayed normally. Those image (.png files) are under the same directory "1024". I suspect those xml files related to XTouchMini panels were unable to be retrieved (but no error message) and therefore both the related png / scripts were unable to be loaded/executed! Would you tell me where are those directories that the scripts files for the Desktop FTPs / WebFIPs will retrieved from in order to display/execute them. N.B. I saw there was a blank window from AAO ( as seen in Windows' task bar at the bottom of the screen) which couldn't be displayed when "click". This likely was the virtual panel of XTouchMini which suppose to be displayed to the desktop screen. Thanks for pointing me to the more area for investigation!

I'll go to have a look there. I only looked at those script files under the My Documents. Thanks for your advise!

Lorby, Thanks for your reply! I have contacted Funatics and done some tests already, the issue still under investigation!

As title, this happened after my last msfs2020 flight session which freeze my PC. I had to force restart my PC in order to continue to use it. I find all other panels in AAO (e.g. Lorby Airliner Flaps;... VSI HiRes) are okay except those L; M; S; & XS panels of XtouchMini. I've reinstalled the latest AAO's update (LorbyAxisAndOhs_4_55_b26) with no luck, any idea on this issue / any file likely corrupted ? I have also tried the WebFIPs, those sizes of panels are able to be display (but blank panels only) the labels and controls are not able to be loaded.

"This does not work for me, I always have to unplug and re-plug the device. Just doing a "Rescan" achieves nothing for me." The rescan only meant to replace the sequence suggested action on "close and reopen AAO" (as suggested by flyforever) for the connection of XTouch only. I do agree with you that an unplug/re-plug of XT is needed before the "Rescan". Cheers!

Lorby, the "online template" was wrongly used. Its the "Desk Gauge" that displays the XT on my PC screen. Sorry for this mistake After I followed the sequence suggested by flyforever, I looked further to check that I do not need to close and reopen the AAO, instead I went to do a "Rescan Devices" under AAO's "Hardware" menu, I works and the XT buttons/knots function normally. I wonder if there is any means for AAO to do a Rescan whenever it starts up? Is there any command in script to do a device rescan? There is another issue I encounter a couple of time, the "Desk Gauge" did not come up the screen, I simply use a workaround to toggle the "Simconnect" off/on to recall it back. Again, is there a way to do this in using a startup script to ensure AAO could connect my XT? Thanks for your help!

I've reset the XTouch mini and followed the sequency as advised by flyforever. The midi device is now recognized and usable for the control as the scripts. Because I haven't used the XTouch for over 6 months and left it unplug, I suspect it has gone to a state which somehow unable to talk to AAO again. Thank you very much LORBY-SI and flyforever ! Have a nice day!

My version of AAO is 4.54.8.0; Windows 11 version 23H2 (Quality Updates up to 2025-02 cumulative update KB5051989; Other Updates: Windows Configuration Update (KB5035942); Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.423.36.0) - Current Channel (Broad) )

I got the same problem using the XTouch mini. All my buttons/knobs/slider not working! however, my online templates works completely. The lights status also reflected in my XTouch mini. I'd tried the unplug/plug the USB and re-started a couple of times but no joy! I also re-started the MSFS2020 but no luck. Please advise what would be possible cause. (N.B. I haven't play the MSFS2020 for over 6 months, however I've updated to the latest version of AAO. Today, I've tried with different planes (Cessna172, FlyByWire Simulations A320neo), both are of same symptoms with online template functioned properly but not the actual XTouch mini)