January 21, 200818 yr Hicant find the proper syntaxSeemes 'pipes' are faster?pipe name = Port name = ?my current SimConnect.cfg:[simConnect]Protocol=IPv4Address=192.168.1.8Port=18002becomes?:[simConnect]Protocol=PipeAddress=Port=pipeport(and use same in simconnect.xml)is it even possible to change my IPv4 connection to "pipe" whatever that isusing ASX on a notebookTHXmtP5K 4x1GB-DaneElec Q6600 8800GTS640MB XPproSP2 FSXSP2 Intel 2500K | AMD 7970 | Win7x64 | 16GB | TV 40" | Touchscreen 22" | HOTAS | Rudder | MCP | FFB Joystick | FSX-SE | Prepar3D | DSC A10
January 21, 200818 yr Commercial Member >Seemes 'pipes' are faster?Only for local connections, i.e. on the same PC. They are faster than TCP/IP because they use shared memory, like the FSUIPC IPC interface, and DDE.When used over a Network I think they are just another wrapper for TCP/IP, so they won't be any faster.>is it even possible to change my IPv4 connection to "pipe">whatever that isPossibly, but I don't think there's any point.>using ASX on a notebookI'm pretty sure that the current release of ASX uses the SP1 version of SimConnect in any case, so it can't take advantage of Named Pipes even if run locally. For programs released to make use of SP2 (like FSUIPC4 since version 4.20) the Named Pipe facility gets used automatically with local connections. It needs no configuring.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
January 21, 200818 yr Author thanks Petenothing anywhere I could make sense ofthis safes me a lot of trials that would have gone nowhereYour info also explanes why FSUIPC keeps working while my IP4 connect was down for a whilethxmtP5K 4GB-DaneElec Q6600 8800GTS640MB XPproSP2 FSXSP2 Intel 2500K | AMD 7970 | Win7x64 | 16GB | TV 40" | Touchscreen 22" | HOTAS | Rudder | MCP | FFB Joystick | FSX-SE | Prepar3D | DSC A10
Create an account or sign in to comment