February 29, 200818 yr This is not (yet) an ASX problem. I followed the ASX instructions to create a Simconnect.Server with XP professional, client Vista.Server and client communication O.K. (already a month now).Sharing the files as instructed (I can read them and changed them from the client).FSX and FSX SP1 installed (deluxe version)SDK , SPA1 and SP2 installed. (SPs from web site fsinsider).MS firewall set to accept port 500 and the two PC.Server: the address data is the server address on the network.Simconnect.xml<?xml version="1.0" encoding="Windows-1252"?>SimConnect Server ConfigurationSimConnect.xmlFalseTrueIPv4global64 192.168.1.45004096False---------------------------------------------------SimConnect.ini[simConnect]level=verboseconsole=0;RedirectStdOutToConsole=1;OutputDebugString=1;file=c:simconnect%03u.log;file_next_index=0;file_max_index=9---------------------------------------------------ClientSimConnect.cfg on client[simConnect]Protocol=IPv4Address=192.168.1.4Port=500MaxReceiveSize=4096DisableNagle=0-----------------------------------------------------------------Simconnect.msi installed and executed on client.But how can I see that this is O.K. ?Result:The test with AI traffic is negative, meaning that the job starts and end very very quickly with no message.So the ASX installation is now on hold. Well it finalization. Of course ASX from client gives an error message:Simconnect SP1 managed version was not found to be correctly installed on this system...But in fact the error appears before ASX was installed.So should I follow the procedure to uninstall and reinstall FSX SP1 update (the system specifies FSX, not SDK) Now I get this message on the client where no FSX is installed. I also receive this message if I severe the link between the 2 PC.Can anybody give me some advice. I already read lot of posts here and elswhere. I will continue my search but if somebody could help me I will appreciate. Roger See my specs in my profile
March 1, 200818 yr Hi Roger,See if both firewalls are allowing SimConnect itself access, not just the ports.Thanks,Jimhttp://www.hifisim.com/banners/hifi-community-sigbanner.jpghttp://www.hifisim.com/
March 1, 200818 yr Author Jim,I don't understand your advice. I read in the ASX doc:Firewall software must be configured to allow SimConnect communications on the port you set (we suggest port 500) Roger See my specs in my profile
March 1, 200818 yr Author Jim,I found in this Forum that I needed exactly this SimConnec.msl:<?xml version="1.0" encoding="Windows-1252"?>SimConnect Server ConfigurationSimConnect.xmlFalseFalseIPv4global64 192.168.1.45004096FalseFalseAutolocalAs you can see with my first post the difference is not that big. But it worked. Now AI traffic test is O.K.I now have problems with ASX and SDK SP1. I will follow the instructions from another thread in this forum to try to fix this. It seems that I need to install SDK on the client PC, at least the SimConnect.msi for each version of SDK. Roger See my specs in my profile
March 1, 200818 yr Hi,I think it is this line in your first .ini that is wrong: TrueThat means to disable the code below this line.Thanks,Jimhttp://www.hifisim.com/banners/hifi-community-sigbanner.jpghttp://www.hifisim.com/
March 1, 200818 yr Author Well that happens when one fiddles with unknown stuff.The ASX also works now. At the beginning I executed SP2 SimConnect.I found (as usual) the info in the forum. I need to have all 3 versions of SimConnect (at least SPa1 for ASX). But to find the info request lot of digging, searches, pulling the hair and ... lot of patience.Maybe this should be a little beter explained in the ASX documentation. It is quite complete but as one can see just one missing detail gives lot of problem.I am happy to use the ASX on the client because it was eating 4 or 5 fps (and my FSX is defined with 26fps). Now I need to migrate RC to the client but I need to check the FSUIPC and WideFs. I read that I needed to reinstall FSUIPC.Thank you Jim and all the others, mainly Al Jordan. Roger See my specs in my profile
Create an account or sign in to comment