Pete Dowson Posted May 20, 2007 Report Posted May 20, 2007 Thanks Pete - at least I now know (sort of :shock: ) how to get myself sorted out. Much appreciated. You are too quick for me! I edited the message after you read it. Please check this part and let me know, please: ============================= Actually, I also thought that this local had to be changed to global for a remote connection? Do you find your remote application works with that set to "local" still? If you had set it to "Global" then installing FSUIPC4 (using my installer) would have actually fixed your XML file for you, as it looks for a "local" section and if it isn't present it adds one for you. If keeping "local" in works for remote clients, then it seems I'll have to make even more checks in the InstallerPlease let me know! Regards Pete
grajay Posted May 20, 2007 Report Posted May 20, 2007 Actually, I also thought that this local had to be changed to global for a remote connection? Do you find your remote application works with that set to "local" still? If you had set it to "Global" then installing FSUIPC4 (using my installer) would have actually fixed your XML file for you, as it looks for a "local" section and if it isn't present it adds one for you. If keeping "local" in works for remote clients, then it seems I'll have to make even more checks in the InstallerPlease let me know! Regards Pete Top job there Pete - I reset the local to global then reinstalled FSUIPC and the following secion was added to my SimConnect.xml: False Auto local Starting up FSX and the Add ons menu is present and FSX is communicating with my Client OK. I should add that running the file as it was with local (apart from killing FSUIPC) I was able to connect over the network OK. As you say - the documentation needs to be a bit more explicit. Thank you again.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now