OK, so if I understand correctly you got a simconnect connection between main and client established alright.Yes, that is normal: client can't start a FSX on the main computer. But I don't see the real downside here - doubleclick FSX on the desktop?Starting directly is only possible when both on the same computer.Well done!

Thank you - it was a challenging few hours. I have learnt quite a bit :) I just did a test flight, and ASE does not seem to send weather to FSX. No doubt, there is a some minor thing I'm not doing correctly.Set the weather in ASE, then start FSX, then wait. Nothing happens weather wise. I then did it the other way - started FSX then ASE and the same - no weather. I set the clouds to overcast and rain to heavy, but these do not get pushed to the sim.Ideas? Cheers, Iain

Thank you - it was a challenging few hours. I have learnt quite a bit :)I just did a test flight, and ASE does not seem to send weather to FSX. No doubt, there is a some minor thing I'm not doing correctly.Set the weather in ASE, then start FSX, then wait. Nothing happens weather wise. I then did it the other way - started FSX then ASE and the same - no weather. I set the clouds to overcast and rain to heavy, but these do not get pushed to the sim.Ideas? Cheers, Iain

You did execute AI Traffic.exe on the same computer as ASE?

Hi:I did some checking - same things occurs when firewall is turned off on both computers, so firewall isn't the issue.You did execute AI Traffic.exe on the same computer as ASE? How can you do this on the client? The SDK is installed on the server (FSX) computer? After reading this I executed the AI Traffic file on the server and then on the client through the networking panel - is this incorrect? It opened on both occurances.The only thing I have not done is installed the X Gauge - which I don't want as I am running a full flight deck with real instruments, etc.Have I missed something - I don't beleive so.Ideas? Thank you, Iain

Hi,SDKs get installed on the client computer only.You run the AI Traffic utility on the client with FSX running on the server. If the utility stays open and shows your AI Traffic being injected and removed from FSX then things are set up correctly. If it runs and closes down on its own, that means that things are NOT set up correctly.

You did execute AI Traffic.exe on the same computer as ASE? How can you do this on the client? The SDK is installed on the server (FSX) computer? After reading this I executed the AI Traffic file on the server and then on the client through the networking panel - is this incorrect? It opened on both occurances.

Share the folder and access it, or copy the files!? LOL...Did you execute the AI Traffic.exe on the client, and did it write Connected to Flight Simulator: 2 in the window?

Have I missed something - I don't beleive so.

If the weather is not updating, then you missed something. Mine does update.

Hi,SDKs get installed on the client computer only.You run the AI Traffic utility on the client with FSX running on the server. If the utility stays open and shows your AI Traffic being injected and removed from FSX then things are set up correctly. If it runs and closes down on its own, that means that things are NOT set up correctly.

Jim, you mean on the server, not client? Why would you install SDK on the client? You can run AI Traffic.exe from the folder, it's a simple exe. I have the whole partitions shared, so I can access whatever I like or need.

You install the SDKs on the client in order to get Sim Connect installed on the client computer. That is how ASE communicates across the network: through 2 installs of SC, one on the server and one on the client.You test the connection by running the utility on the client with SX running on the server.You never need to install the SDKs on the server in this case.

You install the SDKs on the client in order to get Sim Connect installed on the client computer. That is how ASE communicates across the network: through 2 installs of SC, one on the server and one on the client.You test the connection by running the utility on the client with SX running on the server.You never need to install the SDKs on the server in this case.

Yeah, I did install Simconnect, but via exe file, not by installing SDK.Why not the other way around? Install SDK on the server, and use the exe to install on the client.What is the difference?Oh btw. I just noticed I have two clients installed, 60905 and 61242. Should I uninstall 60905?

So Jim, should I:1: remove SDK from server FSX computer, and:2: install SDK on Client machine - ORLeave the SDK that is already installed on the Server FSX machine and install the SDK (including update) on the client?This is now becoming confusing to what is right and what is wrong....Word Not Allowed - the folders are shared across the network (everyone). When I ran the AI Traffic .exe I did so from the client computer from the network panel. I probably should have done this directly from the folders that are shared.I'm at work now and revisit this is a few hours when back at home. Thanks, Iain

In the end, I think it doesn't matter. SDK is not a program. It's a set of tools. It doesn't do anything to the machine.What does is the tool you install: Simconnect. It should be installed on the client machine.The SP1a is important, because it gives you the correct Simconnect version for FSX - 61242.You can check in uninstall, if you have 61242 to uninstall, then you have correct Simconnect version installed.I don't know what's a "network panel". But if you, on the client, open a shared folder (which is on the server), then you are executing on the client, thus doing the right thing.In that case, if you see Connected to Flight Simulator, and as Jim said, you see traffic injecting (if you have any), then all is OK, on the Simconnect side.So in that case, ASE should be working flawlessly.

Roger that - makes sense re: SDK being tools, etcI did note that AI traffic was injected to FSX when it was open at my local airport (several AI aircraft were visible).But, ASE weather does not show when FSX is running. No matter what changes I make to ASE, the changes do not go accross to FSX.I'm sure everything is set as it should. Later today (at work now) I'll double check everything again.By "Network Panel" I mean - when you open a WIN 7 window, on the left had side of the open window is a selection of folders (your documents, programs, networked files, etc, etc). I activated AI Traffic from withion the networked files. Later tonight, I'll try activating from the ACTUAL folder on the cliet machine. (this sounds confusing, but I'll check everything again), Iain

I know you are at work now, but when you get home: run the AI Traffic utility on the client computer with FSX running on the server. Also, nothing will be different in FSX, traffic will still be there. You want to see if the utility "sees" the traffic from the client computer. All of this is to see if your two SimConnects are communicating properly, that is all.

I know you are at work now, but when you get home: run the AI Traffic utility on the client computer with FSX running on the server. Also, nothing will be different in FSX, traffic will still be there. You want to see if the utility "sees" the traffic from the client computer. All of this is to see if your two SimConnects are communicating properly, that is all.

"run the AI Traffic utility on the client computer with FSX running on the server"Hi Jim - first thank you for your help (it's appreciated).I have not run the AI Traffic with FSX actually running before, I ran the utility without FSX actually turned on - this maybe my issue. Iain (I hope) :)PS - On page 54 of the ASE manual it states in STEP 4: Configure Clients, the following: The simconnect.cfg file needs to be set for all client machines that will be running addons that need to connect to the FSX server.The manual them mentions a folder which is; C:UsersUsernamedocumentsDoes this mean you copy the simconnect.cfg file (altered from the SDK config folder) to the above path on the CLIENT machine?

Edited November 2, 201114 yr by Iain Williams

Hi again;I've done some more testing including checking everything twice. This includes disabling the firewall and ensuring the correct static IP address is listed in the simconnect.cfg and .xml files.First, when I run AI Traffic it does not say anything about connecting to flight simulator - just a curser.Second, I have been told that the folders I am placing the .xml and .ini files is the wrong folder. The ASE manual only has vista and XP file paths which I've been told are incorrect.Can you please tell me the correct file paths running two WIN 7 computers.I've been told the correct paths are:C:usersusernamedocumentsflight simulator x files for the simconnect .ini file; andC:users(username)appdataroamingmicrosoftfsx for the simconnect .xml file.I'm pulling my hair out on this one... After trying to install ASE other networked programs which were working are now not working (such as Aivlasoft Electronic Flight Bag).Also, can you please tell me the correct procedure for the PS in the post above this one I'm hoping there is a simple solution to my vexing problem. Thanks, Iain

Oh Lord...Iain, I see all the time you do not read the manual properly. As I said, like at least 5 times already, you have to go these 3 pages step by step. If you don't, can't help you really... you ask questions that are basically in the manual.But OK, I'll play along a bit more.Running AI Traffic.exe without FSX, I don't know how would you even get any result. So: run FSX, and run AI Traffic.exe. Report what happens, EXACTLY.Yes, that does mean that - how did you ever pass that if you went through all the steps? Without absolutely correct configuration, it's not gonna work.