December 17, 201114 yr Ok, so I've got a bit of a bizarre problem with my networked simconnect. I'm running 2 computers, both on W7, both with firewalls that should be configured as necessary for simconnect to work, and they are both connected through a Linksys router. Today, I realized that ASE wasn't connecting to FSX. The simconnect log was showing that FSX wasn't there. The standard AI Traffic test failed. However, FSCopilot saw FSX, and FSinn had no issue injecting traffic over the network. Does anyone have any idea what might be broken here? Joe Sherrill
December 18, 201114 yr Author Ok, so I've looked at the simconnect log and found this at the beginning: 0.00000 SimConnect version 10.0.61259.00.01097 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=640.04893 Server: Scope=local, Protocol=IPv6, Address=::1, Port=50979, MaxClients=640.07666 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=50980, MaxClients=64 Despite the fact that this is set in the simconnect.xml: <?xml version="1.0" encoding="Windows-1252"?><SimBase.Document Type="SimConnect" version="1,0"> <Descr>SimConnect Server Configuration</Descr> <Filename>SimConnect.xml</Filename> <Disabled>False</Disabled> <SimConnect.Comm> <Disabled>True</Disabled> <Protocol>IPv4</Protocol> <Scope>global</Scope> <MaxClients>64</MaxClients> <Address>192.168.1.101</Address> <Port>500</Port> </SimConnect.Comm></SimBase.Document> Any idea what is causing this discrepancy? Joe Sherrill
December 18, 201114 yr Ok, so I've looked at the simconnect log and found this at the beginning:0.00000 SimConnect version 10.0.61259.00.01097 Server: Scope=local, Protocol=Pipe, Name=.pipeMicrosoft Flight SimulatorSimConnect, MaxClients=640.04893 Server: Scope=local, Protocol=IPv6, Address=::1, Port=50979, MaxClients=640.07666 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=50980, MaxClients=64 Despite the fact that this is set in the simconnect.xml: <?xml version="1.0" encoding="Windows-1252"?><SimBase.Document Type="SimConnect" version="1,0"> <Descr>SimConnect Server Configuration</Descr> <Filename>SimConnect.xml</Filename> <Disabled>False</Disabled> <SimConnect.Comm> <Disabled>True</Disabled> <Protocol>IPv4</Protocol> <Scope>global</Scope> <MaxClients>64</MaxClients> <Address>192.168.1.101</Address> <Port>500</Port> </SimConnect.Comm></SimBase.Document> Any idea what is causing this discrepancy? from the manual page 88 :Note: If you are using FSUIPC v4 with FSX, you may need to perform the following steps for proper networked operation:1. First set the SimConnect.xml as described above.2. Next set the <Scope> variable to global instead of local (<Scope>global</Scope>).3. Run FSUIPC install (again if already installed). Your SimConnect.xml will then be properly configured.example :<Disabled>False</Disabled>-<SimConnect.Comm><Disabled>False</Disabled><Protocol>IPv4</Protocol><Scope>global</Scope><Address>Your SERVER pc name are IP adress</Address><MaxClients>64</MaxClients><Port>500</Port><MaxRecvSize>4069</MaxRecvSize><DisableNagle>False</DisableNagle></SimConnect.Comm>-<SimConnect.Comm><Disabled>False</Disabled><Protocol>IPv4</Protocol><Scope>local</Scope><Address/><MaxClients>64</MaxClients><Port/><MaxRecvSize>4096</MaxRecvSize><DisableNagle>False</DisableNagle></SimConnect.Comm></SimBase.Document> Edited December 18, 201114 yr by pasterke Regards,patrickHiFi Technologies Apha TesterFDC/PFE 3 Beta TesterAivlaSoft EFB Alpha Tester
December 18, 201114 yr Commercial Member <SimConnect.Comm> <Disabled>True</Disabled> <Protocol>IPv4</Protocol> <Scope>global</Scope> <MaxClients>64</MaxClients> <Address>192.168.1.101</Address> <Port>500</Port> </SimConnect.Comm>Any idea what is causing this discrepancy?The fact that the very entry you want operating is disabled could be a reason for that, don't you think? ;-)RegardsPeteNote: If you are using FSUIPC v4 with FSX, you may need to perform the following steps for proper networked operation:If your FSX is at least SP1 level normal changes in the SimConnect.xml will affect FSUIPC4 operation, as SimConnect was changed in that update to always offer the local connection by default. It can only be stopped deliberately by an entry disabling the local connection methods.RegardsPete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
December 19, 201114 yr Author The fact that the very entry you want operating is disabled could be a reason for that, don't you think? ;-) I can honestly say I'm a moron. That's what I get for copy/pasting something out of the SDK examples. All good now. Joe Sherrill
Create an account or sign in to comment