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.

Anyone having issue with ASN build 5360 ?

Featured Replies

Hello everyone,

Anyone encountered issue with the last beta SP build 5360 (and P3D v2.3) ?

 

My ASN keeps saying "Waiting for simulator" despite SimConnect connection checked, windows shares OK, DLL.XML checked and new "ASConnect_P3D_Install.exe" launched on the P3D PC. It worked like a charm with any previous build.

 

Opened thread on HifiTec forum : http://www.hifitechinc.com/forums/showthread.php?3640-ASN-Build-5360-(networked)-P3D-v2-3-quot-Waiting-for-simulator-quot&p=19173&viewfull=1#post19173

Vincent B.
Check my free MSFS sceneries : https://flightsim.to/profile/vbazillio/trending and my hardware configuration.

Everything is fine here. I hope you can solve it.

Spirit

 

PS: Did you deinstall ASN before installing this version?

Fine here too, and have to confess I did not even uninstall build #5354...

Here's my experience. I had issues with the new builds. I took 2 steps. One suggested by Kostas at HiFi and one to correct my error.

 

-first, I eliminated all traces of ASN on both machines. Program files, appdata, dll. xml entry...everything. I use a networked setting so that also included as_srv folder on the server machine. I searched after running the uninstall routine to find leftovers.

 

-at Word Not Allowed's suggestion, I disabled this file in the Prepar3D program folder, by adding .old to the end:

 

LockheedMartin.Prepar3D.SimConnect.dll

 

This forced ASN to use the fsx version of simconnect which as Kostas predicted, was more stable.

 

-oh yeah, you may have to manually add the dll.xml entry after installing the new build. There is a link to a browser page that describes the entry; in the ASN program folder.

 

Hope this helps,

 

Graham

Here's my experience. I had issues with the new builds. I took 2 steps. One suggested by Kostas at HiFi and one to correct my error.

 

-first, I eliminated all traces of ASN on both machines. Program files, appdata, dll. xml entry...everything. I use a networked setting so that also included as_srv folder on the server machine. I searched after running the uninstall routine to find leftovers.

 

-at Word Not Allowed's suggestion, I disabled this file in the Prepar3D program folder, by adding .old to the end:

 

LockheedMartin.Prepar3D.SimConnect.dll

 

This forced ASN to use the fsx version of simconnect which as Kostas predicted, was more stable.

 

-oh yeah, you may have to manually add the dll.xml entry after installing the new build. There is a link to a browser page that describes the entry; in the ASN program folder.

 

Hope this helps,

 

Graham

Don't know how post got duplicated.

 

Sry,

Graham

Regards,

Graham Derreck

CYMM

  • Author

Thanks Graham,

 

-at Word Not Allowed's suggestion, I disabled this file in the Prepar3D program folder, by adding .old to the end:

 

LockheedMartin.Prepar3D.SimConnect.dll

 

 

You mean you have a LockheedMartin.Prepar3D.SimConnect.dll file in your Prepar3D program folder ?

 

In my own Prepar3D program folder I only have a SimConnectP3D2.dll fle in the \Modules directory. You should wanted to write in the ASN directory,isn't it ?

 

Anyway deactivating it doesn't change anything and my "AI TRAFFIC.EXE" test still succeeded with or without this DLL.

Vincent B.
Check my free MSFS sceneries : https://flightsim.to/profile/vbazillio/trending and my hardware configuration.

  • Author
SOLVE !

 

15164605062_443d45a6e9_b_d.jpg

 

Solution : correct a wrong access right to shared directoy.

 

It should be my mistake concerning wrong access right to the Prepar3D directory. I always believe I haven't change anything between the two last ASN build. I was wrong. I recreate all share and mapping.  And finally it works.

 

I was duped by the ASN window which seems stucked on the "Waiting for Simulator" but the fact is that ASN was stucked somewhere else. Kostas asking me to export logs bring to my attention that all options were grayed. So ASN was stucked... somewhere else. As usual, if you can access log file it easy to diagnose issues (%appdata%\HiFi\ASNP3D).

 

Great support from Active Sky / Hifi on their forum.

Vincent B.
Check my free MSFS sceneries : https://flightsim.to/profile/vbazillio/trending and my hardware configuration.

Glad you got it sorted. My bad. I should have said Active Sky program folder. Duh! I didn't mention permissions as you indicated previous builds were good. Anyway, all's well that ends well.

 

Graham

Regards,

Graham Derreck

CYMM

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.