I jus found out  that if i start fsx  from within fsxassist  asn won't find the appdata folder  if i just click  on the fsx icon  asn works ! weird.

Maybe because FSXAssist has taken control of that folder. Just guessing, E mail Jim and see if he can help

It's never a good idea to start FSX with another application as that other application takes over ownership of FSX and this can block other external programs from connecting as you found out in this case. I didn't use the launch FSX button in AS2012 and earlier exactly because of this problem.

 

 

It's never a good idea to start FSX with another application as that other application takes over ownership of FSX and this can block other external programs from connecting as you found out in this case. I didn't use the launch FSX button in AS2012 and earlier exactly because of this proble

 

Looks like it was not fsxassist's. fault.I mean now asn does not find the appdata folder even if I use the fsx icon.It doesn't happen all the time but very often

Yeah sorry,,,as with the rest of the post I left I did put simconnect sdk v2,,,,,,,,that line I messed sdk off,,,,that was the probs I had......to make sure it worked ok I did install the whole asn on the server with fsx and that worked fine here,,,,so led me to a conclusion that the simconnect sdk`s were out,,,and they were.

I was able to connect ASN and used the same AS2012 shares.  I have included 2 screenshots that will hopefully help out.  Note that on both my PC's I have added "Everyone" to the group or usernames on the Security tab via the share properties  I have found this technique to be the most easy way to connect 2 PC's whether they both run Win 7 or not.  Find the share, right click, select properties then add the name "Everyone" via the "Edit" button and allow full permission.  And note, both PC's run under the same workgroup name 

 

The client and server PC's must both be running as you are prompted to locate the FSX installation path and the AppData path otherwise ASN will hang. Have you checked to see if the IP address has changed via the CMD prompt?

Check your SimConnect.cfg located on your client PC. Mine is here: C:\Users\Robert\Documents and it should read as follows:

[simConnect]
Protocol=IPv4
Address=192.168.1.76
Port=500
MaxReceiveSize=4096
DisableNagle=0

Next thing to check is your SimConnect.XML located on the server (FSX) PC. Mine is located in C:\Users\Robert\AppData\Roaming\Microsoft\FSX (same location as your FSX.cfg) and it should read as follows:

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="SimConnect" version="1,0">
<Descr>SimConnect</Descr>
<Filename>SimConnect.xml</Filename>
<Disabled>False</Disabled>
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>IPv4</Protocol>
<Scope>global</Scope>
<Address>192.168.1.76</Address>
<MaxClients>64</MaxClients>
<Port>500</Port>
<MaxRecvSize>4096</MaxRecvSize>
<DisableNagle>False</DisableNagle>
</SimConnect.Comm>
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>Auto</Protocol>
<Scope>local</Scope>
</SimConnect.Comm>
</SimBase.Document>

 

Client PC

 

 

Server (FSX) PC

 

In regards to FSXAssist / P3DAssist make sure to install ASN into a non-program files (x86) folder as windows implements specific access rights to this folder.  We at SkyPilot have had good results by installing ASN into C:\HiFI.

 

Regards

 

Jim Allen 

SkyPilot Software