June 27, 20232 yr I'm using Guenseli's scripts for the Leo MD80: https://flightsim.to/file/31930/fly-the-maddog-streamdeck-xl-profile-alpha Lately, I'm seeing an issue where some assignments randomly stop working on my Bravo, e.g. the fuel cutoff levers and A/P mode buttons. I downloaded the latest version of AAO but that didn't do the trick. I'm not sure where to begin how to troubleshoot this... any suggestions?
June 27, 20232 yr Commercial Member 7 minutes ago, chapstick said: any suggestions? Ask the author of those scripts? LORBY-SI
June 27, 20232 yr Commercial Member 44 minutes ago, chapstick said: how to troubleshoot That would depend of what those scripts should be doing. There are so many options. You could try - run the script manually (Menu Scripting -> Run RPN Scripts) to make sure that it isn't on the input side - disconnect and reconnect AAO (click on the green LED of the main menu) - Analyze the script code, check if it uses variables and if those variables have the proper values at the moment the script is triggered) Edited June 27, 20232 yr by Lorby_SI LORBY-SI
June 29, 20232 yr Author On 6/27/2023 at 4:55 PM, Lorby_SI said: That would depend of what those scripts should be doing. There are so many options. You could try - run the script manually (Menu Scripting -> Run RPN Scripts) to make sure that it isn't on the input side - disconnect and reconnect AAO (click on the green LED of the main menu) - Analyze the script code, check if it uses variables and if those variables have the proper values at the moment the script is triggered) I figured out what I was doing wrong (entirely user error). However, I'm still running into another issue where AAO is freezing in the background and not responding to axis inputs I've assigned. In the MD80, I have both reversers, spoilers, and throttles assigned to my Bravo. At seemingly random times, I'll find the throttles unresponsive. I check AAO and it's behaving almost as if it's stopped responding. But then all of a sudden it comes back to life and starts acting on the axis inputs I was making before it froze. Any ideas? edit: just happened on approach, lost control of throttles. Flight scrapped. AAO worked perfectly just days ago. The only thing that's changed is that I reinstalled MSFS base to try and fix a CTD I've been seeing. edit2: After searching, this thread sounds like exactly the problem I'm having. I do have a USB audio amp that I've now blacklisted along with my keyboard, so I'll see if that solves it. Edited June 30, 20232 yr by chapstick
June 30, 20232 yr Commercial Member 8 hours ago, chapstick said: I do have a USB audio amp that I've now blacklisted along with my keyboard, Yes, this is the way to go. While you're at it, blacklist everything that isn't a game controller that you are actually using an axis or button from. LORBY-SI
July 1, 20232 yr Author On 6/30/2023 at 1:13 AM, Lorby_SI said: Yes, this is the way to go. While you're at it, blacklist everything that isn't a game controller that you are actually using an axis or button from. After a test flight blacklisting every device that isn't in use, it seems slightly better in that I'm not totally losing AAO, but it's still "blanking" out sometimes. When it comes back to life, the inputs I was making are queued and played all at once. This only seems to be happening with the Leo MD80--is there anything specific to that aircraft I should be checking?
July 1, 20232 yr Commercial Member 1 hour ago, chapstick said: -is there anything specific to that aircraft Everything is specific about this aircraft, it has it's own SDK and control logic. There is no way of being certain where your problem actually is. Might be the scripts, might be the aircraft itself. Or interference by another app/new addon? Edited July 1, 20232 yr by Lorby_SI LORBY-SI
July 8, 20232 yr Author Alright, now it just happened with the PMDG 737-800. AAO froze, there was no recovery, had to kill it. There was no "Not Responding" warning like Windows would normally show, all my controls just stopped working and I couldn't click anything in the AAO UI. I just tried adding the process to W10's a/v exclusions but at this point I'm not sure what else to do. It was working fine with the 737 up until now and I hadn't made any change to the profile.
July 15, 20232 yr Author Is there any logging or something that AAO has that I can provide? I don't know what else to try here. AAO is randomly freezing with Fenix, PMDG, Leo. Would a clean uninstall/reinstall help? Could the fact that my Bravo is plugged into a (powered) USB3 hub cause issues? I have multiple controllers on this hub. Again, it was working fine for a year+ on the hub, so I'm not sure what would've changed for that to be an issue. Does any of this from the log file mean anything? Quote 7/15/2023 6:33:08 AM.134 : Exception received: 3 from send id 50 errloc 50 7/15/2023 6:34:38 AM.702 : SH: AccessViolationException in SimConnect 7/15/2023 6:34:38 AM.769 : SH: AccessViolationException in SimConnect 7/15/2023 6:34:38 AM.868 : SH: AccessViolationException in SimConnect 7/15/2023 6:34:38 AM.997 : SH: AccessViolationException in SimConnect 7/15/2023 6:34:39 AM.52 : SH: AccessViolationException in SimConnect 7/15/2023 6:34:39 AM.165 : SH: AccessViolationException in SimConnect 7/15/2023 7:11:01 AM.886 : SH: AccessViolationException in SimConnect 7/15/2023 7:11:02 AM.580 : SH: AccessViolationException in SimConnect 7/15/2023 7:11:02 AM.635 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:01 AM.637 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:01 AM.776 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:01 AM.860 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:01 AM.943 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:02 AM.26 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:02 AM.165 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:02 AM.332 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:02 AM.416 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:02 AM.582 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:02 AM.665 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:02 AM.721 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:02 AM.888 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:03 AM.54 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:03 AM.193 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:03 AM.276 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:03 AM.359 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:03 AM.499 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:03 AM.582 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:03 AM.665 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:03 AM.749 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:03 AM.804 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:04 AM.54 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:04 AM.609 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:04 AM.776 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:04 AM.832 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:04 AM.998 : SH: AccessViolationException in SimConnect 7/15/2023 7:13:05 AM.82 : SH: AccessViolationException in SimConnect 7/15/2023 7:36:25 AM.332 : SH: AccessViolationException in SimConnect 7/15/2023 7:36:25 AM.387 : SH: AccessViolationException in SimConnect Edited July 15, 20232 yr by chapstick
July 15, 20232 yr Commercial Member This looks like SimConnect trouble, caused by a script or scripts that you are running. At least that is where it is happening, in the script handler (SH). I'm sorry, but I have no solution to offer. There are no previous reports or data points that I could go on. SimConnect doesn't report errors in such a way that the information is of any use. Maybe there are invalid scripts calling invalid events or invalid variables, and doing that on a grand scale, so Simconnect is being overloaded (what is called a "flood"). It could also be another MSFS addon intefering. To reset AAO to factory defaults, uninstall it, then delete this: \AppData\Local\LORBY_SI\LorbyAxisAndOhsMSFS \AppData\Local\LWR \Documents\LorbyAxisAndOhs Files plus everything in your community folder that has "lorbysi" in its name. Edited July 15, 20232 yr by Lorby_SI LORBY-SI
July 15, 20232 yr Author 25 minutes ago, Lorby_SI said: This looks like SimConnect trouble, caused by a script or scripts that you are running. At least that is where it is happening, in the script handler (SH). I'm sorry, but I have no solution to offer. There are no previous reports or data points that I could go on. SimConnect doesn't report errors in such a way that the information is of any use. Maybe there are invalid scripts calling invalid events or invalid variables, and doing that on a grand scale, so Simconnect is being overloaded (what is called a "flood"). It could also be another MSFS addon intefering. To reset AAO to factory defaults, uninstall it, then delete this: \AppData\Local\LORBY_SI\LorbyAxisAndOhsMSFS \AppData\Local\LWR \Documents\LorbyAxisAndOhs Files plus everything in your community folder that has "lorbysi" in its name. Ok, thanks. This probably isn't related, but in the startup log, AAO says it's Initialized my steelseries keyboard even though I black listed it. Is that normal? 7/15/2023 8:24:55 AM.355 : Sound folder set: C:\Users\alex7\Documents\LorbyAxisAndOhs Files\Sounds Quote 7/15/2023 8:24:56 AM.402 : Found Device SteelSeries Apex 7 828ebde0-3d7a-11ec-8002-444553540000 7/15/2023 8:24:56 AM.464 : Added Device SteelSeries Apex 7 828ebde0-3d7a-11ec-8002-444553540000 7/15/2023 8:24:56 AM.465 : Found Device AURA LED Controller 04f72ae0-3fe5-11eb-8001-444553540000 7/15/2023 8:24:56 AM.927 : Found FirstPerson Bravo Throttle Quadrant e1f4ed60-777b-11eb-8001-444553540000 7/15/2023 8:24:56 AM.928 : Added FirstPerson Bravo Throttle Quadrant e1f4ed60-777b-11eb-8001-444553540000 7/15/2023 8:24:56 AM.928 : Found FirstPerson VKB-Sim Gladiator NXT L 238c01d0-09c8-11ec-8001-444553540000 7/15/2023 8:24:56 AM.929 : Added FirstPerson VKB-Sim Gladiator NXT L 238c01d0-09c8-11ec-8001-444553540000 7/15/2023 8:24:57 AM.292 : Acquiring devices now 7/15/2023 8:24:57 AM.306 : Initialized SteelSeries Apex 7;828ebde0-3d7a-11ec-8002-444553540000 7/15/2023 8:24:57 AM.306 : Initialized Bravo Throttle Quadrant;e1f4ed60-777b-11eb-8001-444553540000 7/15/2023 8:24:57 AM.307 : Initialized VKB-Sim Gladiator NXT L ;238c01d0-09c8-11ec-8001-444553540000 7/15/2023 8:24:57 AM.307 : Device acquisition completed 7/15/2023 8:24:57 AM.328 : Running As Administrator, Web FIPs enabled 7/15/2023 8:24:57 AM.343 : SimConnect established 7/15/2023 8:24:58 AM.883 : Web API established 7/15/2023 8:24:59 AM.395 : Startup complete 7/15/2023 8:26:33 AM.111 : SH: Connected to Simulator KittyHawk Version 11.0.62651 7/15/2023 8:26:33 AM.112 : SH: Connected to SimConnect Version 11.0 Build 62651.3
July 15, 20232 yr Commercial Member 1 hour ago, chapstick said: AAO says it's Initialized my steelseries keyboard even though I black listed it. Is that normal? No, that is not normal. Are you certain that it is on the blacklist? Could it have changed its GUID? Edited July 15, 20232 yr by Lorby_SI LORBY-SI
July 15, 20232 yr Author 2 minutes ago, Lorby_SI said: No, that is not normal. Are you certain that it is on the blacklist? Could it have changed its GUID? It was definitely on the blacklist. What I tried next is taking my joystick and Bravo off the USB hub and plugging those directly into the motherboard ports. In doing so, I also moved the keyboard to different USB ports (it has two connections). After I changed its ports, it showed up again in AAO's recognized devices list--I guess the GUID changed? I then blacklisted it again. Restarting AAO, it didn't initialize the keyboard this time. the blacklist: Quote <?xml version="1.0" encoding="utf-8"?> <DeviceBlacklist xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <devices> <DisabledJoystick> <InstanceGuid>2e143130-23b8-11e8-8002-444553540000</InstanceGuid> <MidiDeviceId>0</MidiDeviceId> <InstanceName>DigiHug USB Audio</InstanceName> </DisabledJoystick> <DisabledJoystick> <InstanceGuid>8e7aa6f0-3d7a-11ec-8004-444553540000</InstanceGuid> <MidiDeviceId>0</MidiDeviceId> <InstanceName>SteelSeries Apex 7</InstanceName> </DisabledJoystick> <DisabledJoystick> <InstanceGuid>828ebde0-3d7a-11ec-8001-444553540000</InstanceGuid> <MidiDeviceId>0</MidiDeviceId> <InstanceName>SteelSeries Apex 7</InstanceName> </DisabledJoystick> <DisabledJoystick> <InstanceGuid>828ebde0-3d7a-11ec-8003-444553540000</InstanceGuid> <MidiDeviceId>0</MidiDeviceId> <InstanceName>SteelSeries Apex 7</InstanceName> </DisabledJoystick> <DisabledJoystick> <InstanceGuid>9196ae20-e186-11ea-8001-444553540000</InstanceGuid> <MidiDeviceId>0</MidiDeviceId> <InstanceName>CH PRO PEDALS USB</InstanceName> </DisabledJoystick> <DisabledJoystick> <InstanceGuid>828ebde0-3d7a-11ec-8002-444553540000</InstanceGuid> <MidiDeviceId>0</MidiDeviceId> <InstanceName>SteelSeries Apex 7</InstanceName> </DisabledJoystick> </devices> </DeviceBlacklist> So far on this 2nd flight after taking the USB hub out of the equation I haven't run into the freezing issue, but I've had other flights where nothing goes wrong so I'm not sure I've narrowed it down yet.
July 15, 20232 yr Commercial Member 6 minutes ago, chapstick said: I guess the GUID changed? Windows does that - there is no way to be sure when or how it wants to change that ID. The keyboard is actually the only known thing that could lock up AAO. Incompatible hardware that floods AAO with errors or just unnecessary data can do that. LORBY-SI
Archived
This topic is now archived and is closed to further replies.