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.

Very Fustrated

Featured Replies

I "fixed" this particular problem by installing the simconnect.msi from the 1a version of the SDK in parallel with the already installed version 2 simconnect client.The client computer was recently wiped clean and reinstalled (XP). It never had simconnect clients earlier than version 2 installed. Seems that either the version 2 installer is broken, or ASA (and ASX) depends on something that the earlier installers do to the system. ASA is still using the version 2 client, but much happier now that 1a is also on the system. Go figure.Tom

  • Author
Same or similar problem here. FSX SP2, ASA running on a networked computer. Drives mapped as per the installation instructions and config files in all the right locations with correct content, I think. The AI SimConnect sample application works fine.Error message appears in a separate window when the green bar on the splash screen is almost all the way to the right. Message text is: "Simconnect Client SP2 Not Found. You must have FSX SP1 or SP2 SimConnect Client installed in order to use FSX mode with ASA. Please go to ...".After pressing "OK" to get rid of the error message ASA completes loading. Near the top of the output window is the text "SimConnect found and initialized", and a bit further down is "SimConnect SP2 instantiated!". ASA connects to FSX and (from the limited testing I've done) appears to work correctly.Tom
Yes this is the excact problem I having.Bill M

Bill McIntyre

Asus StrixB650E-F Gamer, AMD Ryzen 9 7900X3D, Corsair Titanium DDR5 64GB, Samsung 990 PRO-4TB M.2, (4) 2TB SSD's, Corsair H1150i liquid cooler, RTX 2080TI Founders Edition, (2) LG 34" HD Curved Monitor, Sound Blaster Audigy X, 1Kw PC Power & Cooling Power Supply, Corsair Obsidian Full tower Case. MSFS 2024, WIN11 Pro x64                                                                                                                                             

  • Author
I "fixed" this particular problem by installing the simconnect.msi from the 1a version of the SDK in parallel with the already installed version 2 simconnect client.The client computer was recently wiped clean and reinstalled (XP). It never had simconnect clients earlier than version 2 installed. Seems that either the version 2 installer is broken, or ASA (and ASX) depends on something that the earlier installers do to the system. ASA is still using the version 2 client, but much happier now that 1a is also on the system. Go figure.Tom
Well I tried your suggestion by installing SP1A simconnect, it seems it solved my problem. Something is definatly broke using SP2 and ASA.Bill M

Bill McIntyre

Asus StrixB650E-F Gamer, AMD Ryzen 9 7900X3D, Corsair Titanium DDR5 64GB, Samsung 990 PRO-4TB M.2, (4) 2TB SSD's, Corsair H1150i liquid cooler, RTX 2080TI Founders Edition, (2) LG 34" HD Curved Monitor, Sound Blaster Audigy X, 1Kw PC Power & Cooling Power Supply, Corsair Obsidian Full tower Case. MSFS 2024, WIN11 Pro x64                                                                                                                                             

Well I tried your suggestion by installing SP1A simconnect, it seems it solved my problem. Something is definatly broke using SP2 and ASA.Bill M
Hi,More likely, it's a minor snag with ASA checking for SP1A AND SP2 - Instead, it should first check for SP2 and only complain, if neither of the two is found.BRGDSSven Sorensen, EKCH

Create an account or sign in to comment

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.