I’ve been trying to track down the source of some MSFS CTDs and other odd sim behaviors, and have had some results that involve AAO, but I’m at a loss to understand why. Complicating the matter is that the problems do not always occur, but when they do, AAO seems to be involved in some way.

I have had a number of CTDs lately when loading into a flight. Progress bar gets to 80-90% then dumps to desktop with the usual unhelpful 0005 code. Restart, try again, CTD. When I disable lorbysi-content-hooks in the add-on linker and then restart the sim, the flight loads normally. Doesn’t always happen, but when it does disabling the hooks usually fixes it. 

On exiting a flight to return to the main menu, the sim sometimes seems to hang and the main screen will not display unless I toggle AAO’s SimConnect connection off using the button on the AAO app toolbar. In a similar vein, toolbar popup menus (weight & balance, weather, checklists) sometimes won’t initially appear when clicked, unless AAO’s SimConnect connection is toggled off and on. Once toggled, toolbar menus display as expected. It acts as if there is something blocking their visibility until the connection between SimConnect and AAO is severed.

I hear SU14 may have a fix for the CTDs, so I’m inclined to put up with these workarounds for the next couple of weeks, but I’m curious if anyone’s seen anything remotely similar.

8 hours ago, HisBoyElroy said:

I have had a number of CTDs lately

So it worked normally "before"? What changed and when?

In general this sounds like an incompatibility, possibly with another addon. Or something that you make AAO do that floods the sim (autoscript or something). Sorry, no idea. Maybe only connect the app to the sim when you are already sitting in the cockpit?
 I would need so much information to even begin to have an opinion that this can't be handled in a forum. I suggest that you send an email with your proof of purchase to the support address (last page of the manual). Then again, I am not qualified to comment on MSFS instabilities. My MSFS crashes after 20 minutes of flight, AAO on or off. This has been the case on three consecutive new PC builds, so it is probably one of my USB devices (of which I have a lot). Or MSFS has trouble running on some PC configurations.

Edited November 28, 20232 yr by Lorby_SI

I had a similar problem with CTD.

I don't know what could happened but maybe a problem with GPU memory (I've a RTX 3080ti with 12GB of ram)

I reduce all my grapichs settings from ULTRA to HIGH and Terrain LOD from 200 to 100 and now MSFS is much better.

 

On 11/28/2023 at 1:45 AM, Lorby_SI said:

So it worked normally "before"? 

I should have said I have had *more than the usual* number of CTDs lately. 

On 11/28/2023 at 1:45 AM, Lorby_SI said:

What changed and when?

Easier perhaps to ask what hasn't changed. A Sim Update, a World Update, assorted mod and add-on updates, Windows OS updates, and an updated version of AAO.

So, back to the drawing board. Emptied the Community folder and cleared all caches. Restarted in Safe Mode, did a quick flight, exited. Started adding mods back in and testing, first the essential stuff (incl AAO), then utilities (Pushback, Shift Z, Flow), then scenery enhancement mods, and finally planes & sceneries. And just like that, without a clue why, every test worked. No CTDs (so far, save for one that I'm pretty sure was my fault), and no weird, inhibited html popups. 

I'd like to say, "I fixed it", but I've no idea what did the trick, nor do I believe for a moment that it's permanent. But for now, it's ok.

it happens to me too, my SIM CTD with my PMDG 737-800 when AAO is running (did not check with other aircrafts as I don't use AAO with other aircrafts). when I press "fly Now", the plane loads on the tarmac but frozen, about 3 seconds later CTD. I noticed that it happens only if I press "fly now" when AAO is on/loaded. if I make sure AAO is closed (not running) and I press Fly Now, the plane will load fine. once the plane is loaded I load AAO and every thing works fine.

so my current workaround is: 

1. make sure AAO is not running
2. load the plane (fly now)
3. once fully loaded, run/load AAO.

Edited January 5, 20242 yr by Akila

Sounds weird. I just ran a test with the PMDG 737 right now with zero issues. Maybe another app or addon is interfering on your end?

I am suspecting it is because of FSUIPC combination. need to test it further to see is those two are conflicting each other during aircraft load.

I use FSUIPC only for my yoke axis as I have an option to manually (edit the ini file) the axis range.
the default axis range detected by AAO or FSUIPC is ~16,000 to -~16,000 and I need to increase it to around 36,000 to -36,000 on Elevator Axis and around 24,000 to 24,000 for Aileron axis. I need those numbers in order to reduce sensitivity of my controls equally throughout the entire Axis range. it's just very sensitives using 16,000. 

Edited January 5, 20242 yr by Akila

@HisBoyElroy @JPLS you might want to check this and see if you fall under the same conditions.

 

Edited January 6, 20242 yr by Akila

Hi all,

something similar happens very often to me, I loaded AAOO and the VRI Combo Bridge during MSFS loading for my PMDG B737NG, than, started to have CTD at the moment to enter the cockpit or a little later.
Mainly are CTD, but sometimes the simulator simply freezes...
Tried to load AAOO once in the cockpit, it seemed work, but after some times again CTD.
I tried many times to setup a flight without starting AAOO and never crashed.
I'll be very glad if you can find the culprit, because this is a very good piece of software, and I find it very useful!
If needed more info, just let me know.

Thank you
 

54 minutes ago, zetato said:

I'll be very glad if you can find the culprit

Sorry, but I don't think that this is possible. IMO this must be a combination of things, it is no a single cause alone. I have AAO testers who are flying the PMDG 737 almost exclusively, with a lot of AAO (=virutal cabin attendant, virtual first officer, voice recognition, sound output), and never suffered a CTD. On the other hand, my own MSFS has always been unstable, on several computers consecutively. Running with AAO or not, MSFS + PMDG will inevitably crash after 20-30 minutes of flight. It generally happens with all aircraft, but the PMDG is the most reliable in that regard. I am starting to think that the sim just hates me.

In my experience there are only two things that can cause a CTD in the sim: a SimConnect flood or an actual error/exception happening in the simulator (=error in code, hardware defect/overheating etc.).

• Floods can be theoretically caused by every SimConnect client, like AAO, FSUIPC, SPAD, GSX, vPilot, etc. etc. when what you do with them is sending too much input to the simulator too fast. But there is no practical way to find out what that could be.
  In case of AAO, you would have to disable all plugins (like the VRI bridge) and delete the aircraft configuration plus all scripts, then start over, adding one item after the other until the sim becomes unstable again.
• There are infinite possibilities for errors in the sim itself. If you take a look into the various error logs, for example in the Coherent debugger, so will see quite a lot of exceptions happening all the time. And at some point one of them will be just too much. 
  Despite the promises made by Asobo as far as the "Sandbox" character of the sim goes, I personally find it to be very unstable and at the same time too forgiving regarding errors in the JS/Behavior/etc. code that is run in the sim by the addons (=an addon that causes an error should not be allowed to run at all).  
  Again, in case of AAO, that would mean to disable all lorby packages in the Community folder, to see if that impoves matters. This will result in loss of features, for example, BVars will stop working. But by and large you can replace them with InputEvents, so it is not that big a loss
• And as always there is the golden rule of sims (or computing in general): the more addons you stuff into something, the more code written by different people using different strategies you cram into a framework like the sim, the more unstable it will become.
  IMHO (after spending 40 years writing software) the worst is to run multiple items at the same time that do essentially the same thing (like AAO, FSUIPC, SPAD and Mobiflight). That can only go wrong at some point.
   

Edited February 4, 20242 yr by Lorby_SI

Thanks for the answer,

don't know, looking in the event viewer I only found this error, always the same (sorry, is the italian version).

Nome dell'applicazione che ha generato l'errore: FlightSimulator.exe, versione: 1.36.2.0, timestamp: 0x00000000
Nome del modulo che ha generato l'errore: FlightSimulator.exe, versione: 1.36.2.0, timestamp: 0x00000000
Codice eccezione: 0xc0000005
Offset errore 0x00000000014d5f59
ID processo che ha generato l'errore: 0x35c0
Ora di avvio dell'applicazione che ha generato l'errore: 0x01da5774c8d73b5d
Percorso dell'applicazione che ha generato l'errore: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.36.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Percorso del modulo che ha generato l'errore: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.36.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
ID segnalazione: a4774539-df09-4516-aa50-7702bc4d76c4
Nome completo pacchetto che ha generato l'errore: Microsoft.FlightSimulator_1.36.2.0_x64__8wekyb3d8bbwe
ID applicazione relativo al pacchetto che ha generato l'errore: App

Nothing more.

I only noticed that if I do not run AAO, but use the mouse for all the operations, it seems (can't be sure at 100%), the sim has no CTD.
Anyway I'll continue to test and fly, and if I find something will let you know.

Thanks!

40 minutes ago, zetato said:

0xc0000005

To quote Microsoft:

Quote

Application Error 0xc0000005 (Access Violation) error is usually caused by your computer not being able to correctly process the files and settings required to run a particular program or installation. Despite the error showing when you try and use particular pieces of software, it has many different causes including faulty RAM problems, errors with the files of your PC and issues with the settings of your PC.
(...) etc. - you get the usual advice of using sfc /scannow to make sure all OS files are intact

So this is just "an error", nobody really knows what is causing it and it can happen to any program at any time.

No doubt "something" in the combination of your addons will be the cause.  I don't think that it is about the AAO app just "being there", it is what you are doing with it that is causing the problem (unless something is wrong with .Net). As I wrote earlier, try to disable absolutely everything in AAO, every Bridge and Autoscript, possibly the community packages. Only run the "bare bones" app. Normally the sim does not just crash at any odd time, there must be something that you were doing at that point?

Edited February 4, 20242 yr by Lorby_SI

Again, thank you,

I'm trying to use AAO mapped buttons slowly... Usually I was starting battery, Bus transfer, Stby power, pumps, lights, APU etc. in rapid succession, and, maybe too many imput at the same time coud cause some crash. In fact, another thing I noticed, is that normally, if the CTD does not happens at the beginning, the rest of the flight has no problem, it's not a rule, but that's what I saw...
I will also follow your suggestions at the next crash!

Thank you.

There is one additional thing. With the PMDG, if you are using the ROTOR_BRAKE codes to operate switches, there is a "catch". All those codes have two parts, a (mouse button) "down" code and an additional "up" code. Many AAO scripts that I have seen only use the "down" code - and don't bother with sending the "up". That is essentially the same as pressing the mouse button and never releasing it. I don't know if that can cause a problem, but it is something to keep in mind.

Edited February 4, 20242 yr by Lorby_SI

Thanks,

I don't use it, but since I started with slower action sequences, seems to go better, from yesterday this is the third online flight completed without any issue!

Will update in case.