Everything posted by koffee
-
Linda.exe Access violation on exit
I used to frequently get a similar error (possibly the same one, it has been a while) closing LINDA 2.5.7 I found that the file linda-cfg\system\linda-gui.ini would somehow get corrupted, and by replacing it with a saved good copy the error would go away. Kevin
-
ASN Simconnect will not function
koffee replied to Jetman67's topic in The AS16 and ASCA | Active Sky | Active Sky Next | XPAX Support ForumI was thinking you might have multiple SimConnect.CFG files on your client. That's strange that AI Traffic won't connect, maybe you mean connect to P3D. I don't have P3D, so not familiar with the setup, but the HiFi forum mentions a recent new build and a VC++ file. A couple people mentioned that using a different client computer worked, with all the same settings. If ASN FSX works then I wouldn't think it's a firewall issue, it might be worth trying to turn the firewalls (& AV) off for a test. Hope you make progress.
-
ASN Simconnect will not function
koffee replied to Jetman67's topic in The AS16 and ASCA | Active Sky | Active Sky Next | XPAX Support ForumDoes the AI Traffic.exe test work from your client computer, running in the same directory as ASNext.exe?
-
ASN Simconnect will not function
koffee replied to Jetman67's topic in The AS16 and ASCA | Active Sky | Active Sky Next | XPAX Support ForumOne clarification regarding the firewall, though not part of the AI Traffic test: on the client computer only, I was prompted to allow ASNext.exe to go through the firewall. If I display in Windows, "Allow a program or feature through Windows Firewall", ASNext is shown in a list, in my case only for Home network (not public).
-
ASN Simconnect will not function
koffee replied to Jetman67's topic in The AS16 and ASCA | Active Sky | Active Sky Next | XPAX Support ForumTaking it one step at a time, did you run the AI Traffic test from the client computer? When I tested this, I copied the AI Traffic executable from the main FSX server to the client, into the SimConnectFiles subdirectory of ASNext, making sure the SimConnect.cfg was correct, and used port 500 (note: the SimConnect.XML file in this directory is only a sample and is meaningless on the client computer). If this works, there should not be any firewall issue. If it does not work, you could temporarily disable the firewall and antivirus on both computers and try again. If that doesn't work, the SimConnect file parameters likely do not match. k