Rick S.

Seems the problem had to do with my 2nd PCs firewall. WideFS was in there but set to specific ports (8002, 9002). Once I removed those specific port and just selected any it connected. Very strange. Thanx for the help -Rick

I have 4 different sims. FSX, P3Dv3, P3Dv5 and MSFS 2020 all on the same computer. Ports have already been opened. FSUIPC is on my main computer where they are supposed to be for each version. All utilities for the versions are run on another system and networked with the same workgroup. The only one that seems to have problems is P3Dv3. I'll try your suggestions and report back.

Network cards are both working just fine. Both can send and receive data just fine. No errors in the event viewer other than what is related to my VR headset. Logs attached. The missing number in the address in the message I sent was a typo and is not what is in my ini file. FSUIPC4.ini WideClient.log WideClient.ini FSUIPC4.log WideServer.log

Of course I've checked the log. That was the first thing I did. Also, I read the manual and tried your suggestion before even asking for help. FSUIPC didn't even create a log until I shut down the sim. Maybe that's normal. Here's what I got running it the way you suggested FSUIPC4.log WideServer.log WideClient.log

192.168.1.100 and 192.168.1.3 are the same computer just different network cards. Each network card has it's own dedicated IP address. FSXCOMPUTER should resolve to .3 which is the main card. Here are the 2 files: WideClient.ini WideClientLog.7z

Good morning. I've looked though the forums to see if I can locate anything like my particular problem and no luck. So I'm reaching out. I am using 2 different networked computers. I have 2 network cards in each computer and all IP addresses are dedicated addresses. One of the cards is connected directly to the other computer via a cross-over cable. When WideFS loads up it try to poll the cross-over maching at 192.168.1.100 and not 192.168.1.3. I've hardcoded the address inside the wideclient.ini file to specifiy 192.16.1.3. Now, this is where it gets really weird. It works FINE with MSFS (using the correct FSUIPC version, of course) and gives me no problems. Anyone have any ideas? Logs attached WideServer.log FSUIPC4.ini FSUIPC4.log WideClient.log

Figured it out. Seems you cannot run AIGTC directly from the command line and pass a parameter. You have to launch it via a shortcut with the -MSFS2020 parameter tacked to the end. FSUIPC is launching the AIGTC now by launching via the shortcut without any errors so now it's over to Alpha-India Group to suggest allowing the passing of parameters via the command line. Thanx for all your help! -Rick

You're on the board early. 🙂 Here's the actual cut and paste from file explorer: E:\MSFS2020Utils\AIGTC Here's the executable name: AIGTech - Traffic Controller.exe Decided to try to remove the -MSFS2020 option from the end to see if it would run then. THIS time it gave me a code 740 with means run with admin privileges. It already IS elevated, so I don't know what's going on. -Rick

Morning. I'm attempting to run AIG Traffic Manager automatically via the RunIfx command. Here's the command line I use: RunIf1="E:\MSFS2020Utils\AIGTC\AIGTech - Traffic Controller.exe" "-MSFS2020" This is the error I'm receiving from FSUIPC: FSUIPC couldn't run: "E:\MSFS2020Utils\AIGTC\AIGTech - Traffic Controller.exe" "-MSFS2020" in folder "E:\MSFS2020Utils\AIGTC" [Error=2] Don't know what the error code stand for since I couldn't find any error code listings in the docs. Any idea what would be causing this? I have another entry that works fine (no quote needed on it though) so I'm not sure what the deal is. Thanx in advance! -Rick

Yes, I seen that one John. Was hesitant since it appears the way it works is to inject DLL code into the program you're trying to force to a specific IP. I'd rather not do that but thanks for the info. -Rick

I looked through the advance documentation and could not locate what I was looking to find. I have 2 network cards in my computer. One is my normal hard-wired line to my internet. The second is a cross-over cable connecting my two rigs I have next to each other. On this last loadup of MSFS FSU7 hooked to my cross-over network rather than the normal network. Needless to say WideFS never connected. Is there a way to force it to use a specific network card so I can avoid this in the future? Thanx! -Rick

Yes, I think Windblows updated on me. I hate the fact that you are forced to take the update whether you want it or not. I'll check into the Joy Letters per your suggestion.... -Rick

Good morning. I'm running 2 Saitek flight yokes, a set of rudder pedals, and a dual set of throttles. All wires on the 2nd flight yoke are cut except for the yoke itself. I use it at as tiller (had an extra yoke). For some reason FSUIPC will occasionally scramble all the assignments and calibrations of my setup. I can find no underlying reason. The GUID of the devices should not have changed. Has anyone else experienced this issue? Thanx -Rick

Asking how I see it from 25ft away. Twisted patch cable is not an option so I'll just deal with it. Thanx.

lol Cute. The cable modem is in another room (about 10 ft on a direct line and 25ft by cable through the wall). The 2 computers I'm using are side-by-side in my flight sim room. -Rick

Not yet. I don't have a 25ft Cat6 cable right now. That will have to wait. -Rick

Follow-up. Tried a different port. Used several different ones and made sure both the client and the server side were using the same. Still the same issue. No connectivity. Can't figure it out so I'll just live with it. Have a good one. -Rick

Yup. 9002. I guess I'll just run my items that I need to access P3D (FSFlightkeeper and so on) on the same computer instead of my networked one and use Wideclient only for FSX. Thanx.

It's not XX, that's just what I put in the posting. Being I run a private Minecraft server I'd felt better not posting it. Besides, I don't think that particular item is germane to the issue as FSX connects fine. It's P3D that doesn't. As for the wireless, like I said, it runs with no problem with FSX. P3D is the default install with no changes made to it what-so-ever except for the installation of FSUIPC. As for the log I posted the wrong one by mistake. This is the correct one: ********* WideServer.DLL Log [version 7.959] ********* Blocksize guide = 8192 (double allowed) Date (dmy): 07/01/17, Time 11:54:04.014: Server name is FSXCOMPUTER 15140 Initialising TCP/IP server 15140 Initialising UDP/IP server 16046 Broadcasting service every 1000 mSecs 277843 Closing down now ... Memory managed: Offset records: 40 alloc, 38 free Read buffer usage: 0 alloc, 0 free, max in session: 0 Write buffer usage: 0 alloc, 0 free, max in session: 0 Throughput maximum achieved: 0 frames/sec, 0 bytes/sec Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec ********* Log file closed *********

Throwing this out to the group. I have registered Wideclient and FSUIPC. Both run flawlessly under FSX. When running under P3D v3 I cannot get Wideclient to connect to FSUIPC. Both computer are same workgroup and both ports on both firewalls are open for TCP, both send and receive. Wideclient log as follows: ********* WideClient Log [version 6.999z2] Class=FS98MAIN01 ********* Date (dmy): 07/01/17, Time 11:54:47.920: Client name is OLD_COMPUTER 312 LUA: "C:\FSX\WideFS\Initial.LUA": not found 343 Attempting to connect now 359 Trying TCP/IP host "FSXCOMPUTER" port 8002 ... 359 ... Okay, IP Address = 192.168.0.xx 21390 Error on client pre-Connection Select() [Error=10060] Connection timed out 21390 Ready to try connection again 22390 Attempting to connect now 66515 Trying TCP/IP host "FSXCOMPUTER" port 8002 ... 66515 ... Okay, IP Address = 192.168.0.xx 132703 Trying TCP/IP host "FSXCOMPUTER" port 8002 ... 132703 ... Okay, IP Address = 192.168.0.xx 198890 Trying TCP/IP host "FSXCOMPUTER" port 8002 ... 198890 ... Okay, IP Address = 192.168.0.xx 254453 ****** End of session performance summary ****** 254453 Total time connected = 0 seconds 254453 Reception maximum: 0 frames/sec, 0 bytes/sec 254453 Transmission maximum: 0 frames/sec, 0 bytes/sec 254453 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 254453 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* I run an ethernet cable with a static IP (that's what the xx is). The Wideclient computer is ALSO a static IP but on a wireless adapter. I do the static IPs to avoid some conflicts with other devices on my network. FSIUPC log as follows: ********* FSUIPC4, Version 4.959 (19th December 2016) by Pete Dowson ********* Windows version reported as 6.2.?.9200 Prepar3D.exe version = 3.0.14945.14945 Reading options from "F:\P3D\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 8.0 or later Module base=5E280000 User Name="Rick S" User Addr="xxxxxxxxx" FSUIPC4 Key is provided WideFS7 Key is provided 15 System time = 07/01/2017 11:52:56 15 FLT UNC path = "\\FSXCOMPUTER\Documents\Prepar3D v3 Files\" 15 ------ Module Version Check ------ 15 acontain.dll: 3.0.10.14945 15 api.dll: 3.0.10.14945 15 controls.dll: 3.0.10.14945 15 fs-traffic.dll: 3.0.10.14945 15 G3D.dll: 3.0.10.14945 15 language.dll: 3.0.10.14945 15 sim1.dll: 3.0.10.14945 15 visualfx.dll: 3.0.10.14945 15 weather.dll: 3.0.10.14945 15 window.dll: 3.0.10.14945 15 ---------------------------------- 15 Trying F:\P3D\Modules\SimConnectP3D3.dll 15 Found it: trying to connect 78 FS UNC path = "F:\P3D\" 94 ---------------------- Joystick Device Scan ----------------------- 94 Product= Saitek Pro Flight Rudder Pedals 94 Manufacturer= Saitek 94 Vendor=06A3, Product=0763 (Version 1.1) 94 Serial Number= Saitek 109 Product= Saitek Pro Flight Quadrant 109 Manufacturer= Saitek 109 Vendor=06A3, Product=0C2D (Version 2.0) 109 Serial Number= Saitek 109 Product= Saitek Pro Flight Yoke 109 Manufacturer= Saitek 109 Vendor=06A3, Product=0BAC (Version 3.4) 109 Serial Number= Saitek 109 ------------------------------------------------------------------- 140 LogOptions=00000000 00000001 140 ------------------------------------------------------------------- 140 ------ Setting the hooks and direct calls into the simulator ------ 140 --- CONTROLS timer memory location obtained ok 140 --- SIM1 Frictions access gained 140 --- FS Controls Table located ok 140 --- Installed Mouse Macro hooks ok. 140 --- Wind smoothing fix is installed 140 --- SimConnect intercept for texts and menus option is off 140 --- All links okay (except older global weather setting method) 140 ------------------------------------------------------------------- 140 SimConnect_Open succeeded: waiting to check version okay 140 Trying to use SimConnect Prepar3D 140 Opened separate AI Traffic client okay 39156 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.0.3.0 (SimConnect: 3.0.0.0) 39156 Initialising SimConnect data requests now 39156 FSUIPC Menu entry added 39187 \\FSXCOMPUTER\Users\Rick\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml 39187 F:\P3D\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 66594 User Aircraft ID 2 supplied, now being used 66844 System time = 07/01/2017 11:54:02, Simulator time = 08:00:02 (13:00Z) 66844 Aircraft="F-22 Raptor - 525th Fighter Squadron" 67844 Starting everything now ... 71015 Advanced Weather Interface Enabled 126359 Sim stopped: average frame rate for last 60 secs = 19.9 fps 126359 Max AI traffic was 37 aircraft (Deleted 0) 217469 Sim stopped: average frame rate for last 84 secs = 20.0 fps 217469 Max AI traffic was 37 aircraft (Deleted 0) 346969 === NOTE: not calling SimConnect_Close ... 347969 System time = 07/01/2017 11:58:44, Simulator time = 08:02:26 (13:02Z) 347969 *** FSUIPC log file being closed Minimum frame rate was 19.1 fps, Maximum was 20.0 fps Minimum available memory recorded was 2329Mb Average frame rate for running time of 144 secs = 19.9 fps Maximum AI traffic for session was 37 aircraft Memory managed: 40 Allocs, 39 Freed ********* FSUIPC Log file closed *********** Does anyone see anything that would signify where my connection issue is located? Thanx in advance!