ASA Network Questions
Jim: I just purchased ASA and set it up for a network connection.
Not all is working yet so I have some questions:
I have ASA installed on one XP PC (FSX also happens to be there which I do not use) and my working FSX on a Vista PC. These 2 PCs are already networked together. I added all the appropriate shared folders and they work fine.
The "Test the Configuration" in Step 5 works fine. I can see the "Connected to FS" and I see some messages from the debug console. So that is OK.
1. Does the client PC need also to have FSX SDK installed on it; I have it on the server PC.
2. Where do I install simconnect.msi on the client (from Step 3)?
3. Since FSX is on the client (not using it and does not have SP1 or SP2 installed), will I need to edit all the registry locations on this PC?
There will probably be additional questions.
Thanks, AL
JIm: Thanks. Told you there
JIm: Thanks. Told you there would be a few more questions:
1. Not sure about your answer to #1. Does the SDK need to be installed on the client PC to make this all work? I mean is this a requirement? It is unclear to me from the instructions in the manual.
2. If I uninstall FSX on the client, do you know what registry entries also need to be removed that relate to FSX?
3. After I get ASA working properly with the server, can FSX be reinstalled on the client PC? I often use it as a reference to check FSX files on my other PC.
4. As far as that test configuration in step 5, should that AI traffic program be run on the client (with ASA) or server (with FSX) PC?
Thanks, Al
Hi, 1. No, just the
Hi,
1. No, just the simconnect.msi needs to go on the client and run there.
2. Pretty sure the FSX uninstaller takes care of those.
3. Maybe. We can try this later.
4. On the client with FSX running on the server.
Thanks,
Jim - HiFi Software Sales and Support
Jim: One other question to
Jim: One other question to add to my post above:
Regarding enabling the "port" in Windows Firewall (page 50 of manual) - when I do this it asks for a name. What should be the name given to this port? Should it be SimConnect? Thanks, Al
Hi Al, 1. Yes that is
Hi Al,
1. Yes that is fine.
2. That gets moved to the client and then you run it there. A .msi file is an installer type file.
3. Uninstall FSX on that client machine.
4. Doesn't really matter. That is good or "ASA". Just something that describes the port for yourself.
Thanks,
Jim - HiFi Software Sales and Support
Jim: Got everything working
Jim: Got everything working well after uninstalling FSX. Very nice. Two more questions:
1. Is it possible to reinstall FSX on my client PC at some point just as a reference for me to use? Will this cause any problem now that ASA has its FSX location pointing to the server?
2 Regarding the graphics applications - either X Graphics, REX or FEX, do these have to be installed on the server PC? How do these work in a network configuration? How do you do snapshots, etc?
Thanks again, Al
Hi Al, 1. I think that would
Hi Al,
1. I think that would be safe.
2. You can put X Graphics on the client machine and then use the ASA Integrated Graphics Icon to automatically generate Snapshots. With those other 2 programs, I am not sure where you have to install them, but no matter what you load the textures in FSX, take a snapshot, load other textures, take a snapshot and so on. It's a lot easier with XG and ASA automatically generating snapshots.
Thanks!
Jim - HiFi Software Sales and Support
Thank you Jim: So if I get
Thank you Jim: So if I get XG, I can install this program on the client with ASA, make snapshots, etc and when these are "loaded" into FSX, it is done over the network to the server - just wanted to be clear about this.
Also: 1. Where are these snapshots saved in FSX? 2. When they are loaded into FSX, where are they placed - what folders in FSX are they copied into? Thanks again, Al
Hi, Correct, but even simpler
Hi,
Correct, but even simpler than that. Only during the Snapshot creation process.
1. In a new folder called Snapshots in FSX.
2. FSX\Effects
FSX\World\Scenery
FSX\Scenery
Thanks,
Jim - HiFi Software Sales and Support