Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Cutterwood

Members
  • Joined

  • Last visited

  1. This morning, I disabled AAO packages by renaming Manifest.json. No strong stuttering during a 3/4 hours. flight But it looks exactly like I didn't start AOA before my MSFS session. So i gives it back, its original name before this afternoon flight. And this time I had a CTD but fortunately with not a complete freeze of the PC. I could'nt close the windows with the mouse but i can do it using Task manager to close them. And I have a log file that is stamped at the moment of the crash 14:58. : ------------------------------------- 20/05/2026 14:10:59.906 : MW: Exception received: 3 from send id 164 errloc 164 20/05/2026 14:58:23.411 : MW: Exception de HRESULT : 0xC000014B in SimConnect. HJET HA420 Blue 20/05/2026 14:58:23.411 : SH: Exception de HRESULT : 0xC000014B in SimConnect. HJET HA420 Blue 20/05/2026 14:58:23.412 : MW: Exception de HRESULT : 0xC000014B in SimConnect. HJET HA420 Blue 20/05/2026 14:58:23.412 : MW: Exception de HRESULT : 0xC000014B in SimConnect. HJET HA420 Blue 20/05/2026 14:58:23.412 : MW: Exception de HRESULT : 0xC000014B in SimConnect. HJET HA420 Blue 20/05/2026 14:58:23.412 : MW: Exception de HRESULT : 0xC000014B in SimConnect. HJET HA420 Blue 20/05/2026 14:58:23.412 : MW: Exception de HRESULT : 0xC000014B in SimConnect. HJET HA420 Blue 20/05/2026 14:58:23.412 : MW: Exception de HRESULT : 0xC000014B in SimConnect. HJET HA420 Blue 20/05/2026 14:58:23.412 : MW: Exception de HRESULT : 0xC000014B in SimConnect. HJET HA420 Blue 20/05/2026 14:58:23.412 : MW: Exception de HRESULT : 0xC000014B in SimConnect. HJET HA420 Blue 20/05/2026 14:58:23.412 : MW: Exception de HRESULT : 0xC000014B in SimConnect. HJET HA420 Blue 20/05/2026 14:58:23.412 : MW: Exception de HRESULT : 0xC000014B in SimConnect. HJET HA420 Blue 20/05/2026 14:58:23.412 : MW: Exception de HRESULT : 0xC000014B in SimConnect. HJET HA420 Blue 20/05/2026 14:58:23.412 : MW: Exception de HRESULT : 0xC000014B in SimConnect. HJET HA420 BIue ----------------------------------------------------------------- T hope this will be able to give us some useful information.
  2. It means that i have exactly the good settings in AAO.
  3. HI, All 3 settings in AAO were on line with those in your answer. I looked at log files (*.txt.). There are 2 or 3 files per MSFS session : same number as strong stutterings. Each of these files have the same single line : "MW: Exception received: 3 from send id 164 errloc 164". Is this a known SimConnect error code?
  4. HI, All 3 settings in AAO were on line with those in your answer. I looked at log files (*.txt.). There are 2 or 3 files per MSFS session : same number as strong stutterings. Each of these files have the same single line : "MW: Exception received: 3 from send id 164 errloc 164". Is this a known SimConnect error code?
  5. New question to Lorby_SI. : Still no CTD but experiencing 1-second GPU drops (5-8% GPU usage only) with frozen image, 4-5 times per flight, no CPU spikes at the same time.. Two occurrences 15 seconds apart during ILS approach at 1500ft, AP+AT active, no physical input. Could the RPN script polling rate cause periodic SimConnect interruptions?
  6. Thank you for this honnest answer. I must be lucky as with TBM 930 and Hondajet (without AOA and therefore without Fadec), I can fly everywhere in MSFS 2020.
  7. I imported your HJET template (axes only, cancelled the button assignments as I don't have a Honeycomb Bravo). Same crash in under 2 minutes. The assignments look identical to what I had before, except for the curve shape 1.2. At this point I believe the issue is not in the configuration itself, but in AAO running alongside MSFS on an RTX 5080 (Blackwell architecture). Can you give me your opinion.
  8. AAO minimized: still crashes. Switched to THROTTLE1/2_AXIS_SET but throttle levers are now inactive in cockpit - probably a value range issue (0-100 vs -16383/+16383)? How should AXIS_SET be configured in AAO? My settings are now : L:THROTTLE1_AXIS_SET, percent. Axis min 0 axis max 100. could you give me the good settongs ? Thanks in advance.
  9. Hello Oliver, Thank you for your quick and detailed response. First, I will test with AAO minimized during flight. I was not doing this before, so the throttle cursors were updating continuously in the WPF window during the entire flight - which could well explain the issue. Regarding axis assignments: I am currently using THROTTLE1_SET and THROTTLE2_SET (Percent, no AXIS variant). I realize this might be a second cause: sending discrete events continuously (at every micro-movement of the physical throttle lever, including vibrations) could saturate the MSFS main thread, which is already handling physics, avionics, SimConnect and 3D rendering simultaneously. Multiplied by 2 throttles, this could cause a SimConnect overflow leading to a GPU timeout and the nvlddmkm 153 crash. I will test in this order: 1. AAO minimized, same assignments (THROTTLE1/2_SET) 2. AAO minimized, switching to THROTTLE1/2_AXIS_SET 3. Single throttle only if needed I will report back with results. Thank you again for your involvement.
  10. Hello, I am using Axis and Ohs v4.56 build 19 with MSFS 2020, on a system with an RTX 5080 GPU (driver 591.86). I have identified a fully reproducible crash pattern: - With AAO active (only 2 throttle axes assigned, for HondaJet HA-420 FADEC): MSFS crashes within a few minutes with Windows Event ID 153 nvlddmkm. - With AAO completely closed, same flight, same aircraft, same route: zero crashes over multiple complete flights. Additional observation: AAO adds approximately +1.5ms to CPU render time when active. This disappears when AAO is closed. This strongly suggests AAO triggers a GPU driver timeout (TDR) through its SimConnect interaction, possibly specific to the RTX 5000 series. Could this be investigated for a future build? Thank you.
  11. Sorry if I made a mistake. Which forum should I use ?
  12. Hello, I am using Axis and Ohs v4.56 build 19 with MSFS 2020 on a system equipped with an RTX 5080 GPU (driver 591.86). I have identified a reproducible crash pattern: With AOA active (only 2 throttle axes assigned for HondaJet HA-420 FADEC): MSFS crashes within minutes with a Windows Event ID 153 nvlddmkm error. With AOA completely closed, same flight, same aircraft, same route: zero crashes over multiple full flights. AOA also adds approximately +1.5ms to CPU render time when active, which disappears when closed. This strongly suggests AOA is triggering a GPU driver timeout (TDR) through its SimConnect interaction, possibly related to RTX 5000 series specifics. Could this be investigated for a future build? Thank you.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.