I sometimes read about addons being run over a network and I always thought this was done so FSX would run better (since the addon doesn't need resources from the computer that's running FSX). So in my simple mind I thought you would run FSX on one computer and then simply connect another computer to it which would inject whatever the addon could inject (talking about OpusFSX, ProATC/X, FS2Crew and addons like that).

 

I have a (almost) spare laptop here at home and so this evening I started to investigate if I could put that laptop to good use in order to let FSX run better (then it does already) by maybe putting my weather and ATC software on that laptop. However, pretty soon I read about FSX having to be installed and running on the server too and lower performance on the client and the server needing to be a monster machine and before I knew it I was completely lost...

 

So here is my simple question: is it possible to use a (few years old) laptop to run addons on it so FSX will have more resources available on its own computer and hence perform better? Or was my view on this all totally wrong and way too simple from the start?

I've been running ATC, weather, moving maps etc on a network computer for yrs. I cant really give numbers on performance but it at least makes it easier to use the addon programs in flight. Not having separate windows opened on the sim computer, Im able to run in fullscreen all the time. That in itself makes for a more stable sim IMO.

Jeroen,

 

I have FSX running on a more powerful computer and several auxiliary software running on a lower powered computer. The use of simconnect built into FSX makes this possible.

 

Whether an application will work on the secondary computer depends on how the application developer "built" the app. There are a few "if's" and "maybe's"

 

If an application interfaces with FSUIPC, it will likely run on the second PC if the second PC is running WideFS.

 

If an application interfaces with simconnect and the app developer has provided the configuration, you can run it on the second PC.

 

For a very good example of how network or non-network works, check out fswidgets.com "EFB for FSX". They have a very good tutorial on how to configure their product for use on a second computer. I used their demo version to evaluate the product (didn't buy it for a variety of reasons) but they did a great job of explaining simconnect.

 

Also, Plan-G has a very good description of how to make their software run from a second PC.

 

Hope all this helps. It is a bit complex at first but after you learn the "buzzwords", it becomes a bit easier to decipher.

Thanks, I will have a look at those sites. In the meantime maybe someone who uses OpusFSX, FS2Crew and ProATC/X on a network (that would be luck ) might comment on the advantages of running those addons on a network. And if you really need FSX to be installed on the server (being the low end laptop) for any of those addons.

Hi Jeroen,

 

There is a lot of mystique surrounding networking, but it really is very simple in the end. Basically one PC puts its hand up and says "hello, I can be found here at this address" (i.e. the IP address/Port number). The second PC has to be told where that address is and once that is done it the app can go there to connect and get the data.

 

FSX definitely does not need to be installed on the remote PC/Laptop, not for SimConnect based applications.

 

The only thing required is that you run the SimConnect.MSI installer. That installs the SimConnect.DLL into the Windows Side-by-side system. You get that installer from the FSX SDK, its in one of the subfolders:

 

C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Core Utilities Kit\SimConnect SDK\lib\SimConnect.msi

 

Once you run that on your laptop any SimConnect clients should be able to find the main FSX machine on the same network (as long as they are told where to look in via the SimConnect.CFG file).

You will need to check the applications manual to see if the specific programs you have will run in a network configuration.

 

If the program will run on a network PC, then, yes it will reduce the stress on the main FSX PC.

 

Regards OpusFsx, I am using it. It has to be installed on the main FSX PC.

I think the best explanation that helped me make simconnect work is in the Activesky manuals near the end about networked configuration. Studying this for a short time was what got it working for me. I do also use WideFS for some programs like VASFMC and a traffic separation manager. The EFB Software has two methods of setting up, one where both programs run on the FSX pc and one where there is a "server" on the FSX computer and the main user interface on a separate computer. I definately like having the programs running on a separate pc and only fsx on the main computer.

Remember that running other programs remotely is not necessarily a simple way to get better FSX performance. Depending on the requirements of the addon interaction with FSX, it may make things worse. Programs work remotely without any problem since they don’t talk too much with FSX, or don’t need to scan the scenery or other object files too often. Other programs may not be able to interact with networked FSX without even more programs running on the FSX machine, making it one step forward and two back.

.

Remember that running other programs remotely is not necessarily a simple way to get better FSX performance. Depending on the requirements of the addon interaction with FSX, it may make things worse. Programs work remotely without any problem since they don’t talk too much with FSX, or don’t need to scan the scenery or other object files too often. Other programs may not be able to interact with networked FSX without even more programs running on the FSX machine, making it one step forward and two back.

 

Steve,

 

What are some examples of software best to run only on the FSX computer (even if they have a network config)?

I suppose it’s not as simple as that, combinations of addons, equipment, network adapter, and operating system make it difficult to say. To be honest anything you can get that is designed and has a mode for running remotely should be great. A moving map presents no problems but if files have to be traversed across the network, rather than having a local set, performance may not fare so well. If it can run remotely try it out, bearing in mind what is being sent over the network.

...Actually being an FSX addon more often than not means working on the network anyway. Consider that run locally they only need communicate with the host node, and that’s faster with less delay than a remote node. Most programs capable of remote operation use very little network bandwidth and don't rely on high speed feedback from the sim.

I run PRO ATC on a network as well as a bunch of other stuff like FS WIDGETS, Plang G and EFB. I also have a moving map on my tablet. The weather feature for OPUS is not yet ready for networking. It is advantageous because it is easier to use the programs on another computer while flying and it reduces the load a little bit on your main rig. ALso the answer is NO, you do not need FSX installed on the client.

 

Instead of giving you full instructions on how to run these programs on a network, I will point to you a cool little free program called FS Widgets GMAP. It is easy to install and run from your 2nd laptop. http://fswidgets.com/shop/download_files.php (I like the garmin edition). In the download it has a complete set of instructions for how to run this on your networked laptop. The process for this program is exactly the same as for PRO ATC. Other programs like EFB and Plan G are even easier as you just enter the settings inside the program itself.

Just make sure you have simconnect installed on both machines and the two computers are networked. Also make sure that on your main FSX rig you enable all of the files and folders necessary to be shared (in the Sharing tab) as well as in the Security tab for the same folders to give your client read/write access.

 

If you have any issues or questions feel free to PM me.