I have 6 LAN networked PCs (A,B,C,D,E and F) and have built 2 cockpits, a Boeing 747 and Cessna 172. Because of the number of USB ports each needs I have had to used computer A as server for the 172 and B as server for the 747. Each PC has 2 User Accounts, one for when I fly the 172 and the other for the 747. My problem is with the IP address. As the servers have different addresses it appears that I would have to change the addresses (and server name) on all 6 PCs when switching cockpits. Is there a way around this or to make switching easier.

 

Phil.

Hi Phil,

 

Interesting set up. I think you can solve your problem by taking copies of the configuration data files, then using a simple batch procedure to copy the appropriate config files into the current files before running the FSXSERVER or FSXCLIENT programs. I believe (on holiday now) that the config data is stored in FSXSERVERCFG.DAT and FSXCLIENTCFG.DAT files respectively for the server and client programs. You could configure one system then copy and rename these files on your systems, for example FSXSERVERCFG_C172.DAT and FSXCLIENTCFG_C172.DAT. Then create a batch file to first copy the relevant _C172 or _B747 config file into its current file before running the FSXSERVER or FSXCLIENT program, all within the same BAT file.

 

For example,

 

@ECHO OFF

CD C:\OpusFSX

COPY FSXSERVERCFG_C172.DAT FSXSERVERCFG.DAT

CALL FSXSERVER.EXE

 

Something along those lines anyway. If you have setup your permissions and security across the network you may even be able to create a batch procedure to start the entire system up.

 

@ECHO OFF

CD \\SystemA\C\OpusFSX

COPY FSXSERVERCFG_C172.DAT FSXSERVERCFG.DAT

CALL FSXSERVER.EXE

CD \\SystemB\C\OpusFSX

COPY FSXCLIENTCFG_C172.DAT FSXCLIENT.DAT

CALL FSXCLIENT.EXE

 

You may have to experiment, not at the computer right now and haven't done any of this for donkey's years.

 

Good luck with your system.

 

Stephen :-)

 

I should add, the CAM files can be treated in a similar fashion just in case you wanted different sets of cameras defined for each set up, but you may just be able to define all C172 and B747 cameras together which would most likely be the simplest method.

 

Let us know how you get on, sorry I can't test or check anything here so the above is really guess work.

 

Regards

Stephen :-)

Hello Stephen,

  Thanks for your reply. I will try what you suggested. I have a couple more questions to ask.

1) I apologise in advance as I am probably being stupid here. The network manual gives an example of entering IPv4 IP addresses of 192.168.1.11 on the server and 192.168.1.21 on the 1st client. Am I right in entering the IP address of my own server into the server PC and how do I determine the addresses to enter on the clients?

2) As I said in my original post, due to the number of USB ports required for the 2 cockpits I have to use 1 PC as server for the 172 and a second PC as server for the 747. What is the situation regarding buying OpusFSX for use on the 2 PCs? I don't want to have to buy OpusFSX twice. 

 

Phil

You had always best use the computer names in the Configuration of the clients. The IP addresses in the manual were for example purposes, but the 192.168 part is commonly used for local private networks, and the following 1 is just a common group number so the 192.168.1 part is usually quite common.

 

We trust you so you can just install the license on the two computers you are going to use as servers.

 

Stephen :-)

Thanks Stephen. So the IP address of the individual computers does not matter? One PC I intend to use as server has an IP address of 169.254.130.162 but I could just as easily enter 192.168.1.11 on the server and 192.168.1.12 on one client and 192.168.1.13 on the next etc. As long as the address starts 192.168.1. I can enter anything in the last section. It does not matter. Is this correct?

 

Phil

It does matter a great deal. You should aim to use the same network ID and group numbers for all PCs. So use all 192.168.1 or all 192.168.2 etc.. The IDs and group numbers must be identical so that all computers assume to operate on the same network, in this case 192.168, and use the same network group number, in this case 1 or 2. Hence our examples use 192.168.1.n where 'n' is the unique number assigned to the computer, but they all use 192.168.1.

 

Stephen