Rick S. Posted January 7, 2017 Report Share Posted January 7, 2017 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! Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 7, 2017 Report Share Posted January 7, 2017 1 minute ago, Rick S. said: I run an ethernet cable with a static IP (that's what the xx is). Why "xx"? You know that all 192.168.x.x addresses are local to your Network, don't you. They can't be accessed externally without knowing the external IP address of your Router and you allowing it by router settings. 3 minutes ago, Rick S. said: The Wideclient computer is ALSO a static IP but on a wireless adapter. I've never had success with Wireless connections for the sort of continuous link WideFS needs. 4 minutes ago, Rick S. said: 21390 Error on client pre-Connection Select() [Error=10060] Connection timed out Timed out means it probably connected, sent a message, but never got a recognisable reply. Are you sure nothing else of your P3D installation is using the same ports (8002 and 9002) that WideFS uses by default? 5 minutes ago, Rick S. said: FSIUPC log as follows: The FSUIPC.LOG is irrelevant for WideFS. You need to show the WideServer.log file. That's the other end of the connection. In FSUIPC4 it is built into FSUIPC rather than seperate as it was with FSUIPC3, but it still has it's own log. Pete . Link to comment Share on other sites More sharing options...
Rick S. Posted January 7, 2017 Author Report Share Posted January 7, 2017 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 ********* Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 7, 2017 Report Share Posted January 7, 2017 3 hours ago, Rick S. said: As for the log I posted the wrong one by mistake. This is the correct one: Yes. That doesn't show anything useful, obviously. It never received anything. Did you try a different port? Pete Link to comment Share on other sites More sharing options...
Rick S. Posted January 8, 2017 Author Report Share Posted January 8, 2017 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. Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 8, 2017 Report Share Posted January 8, 2017 53 minutes ago, Rick S. said: Yup. 9002. Er, 9002 is not good. That's the port it already uses for Broadcasting its present. You need to use somethinmg other than 8002 and 9003. Didn't you see the 9002 setting already there, as Port2 in the [WideServer] section of the FSUIPC4.INI file and also in the WideClient.INI file? The data one is Port=8002, the broadcasting one is Port2=9002. Pete Link to comment Share on other sites More sharing options...
Rick S. Posted January 28, 2017 Author Report Share Posted January 28, 2017 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 Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 28, 2017 Report Share Posted January 28, 2017 6 hours ago, Rick S. said: No connectivity. As I said, I never had success over wireless either, though they did connect, with difficulty. The problem is that WideFS needs continuous connection and you often just don't get that with wireless. It's okay for most ordinary data access. It isn't the capacity which is the problem, just the continuity. Did you ever test it with a wired connection instead? Pete Link to comment Share on other sites More sharing options...
Rick S. Posted February 2, 2017 Author Report Share Posted February 2, 2017 Not yet. I don't have a 25ft Cat6 cable right now. That will have to wait. -Rick Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 3, 2017 Report Share Posted February 3, 2017 2 hours ago, Rick S. said: Not yet. I don't have a 25ft Cat6 cable right now. That will have to wait. How do you manage to read the screen from 25 feet away? Pete Link to comment Share on other sites More sharing options...
Rick S. Posted February 11, 2017 Author Report Share Posted February 11, 2017 On 2/2/2017 at 7:11 PM, Pete Dowson said: How do you manage to read the screen from 25 feet away? Pete 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 Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 11, 2017 Report Share Posted February 11, 2017 33 minutes ago, Rick S. said: 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. If the two PCs are so close to each other, you can connect them with a short cable. The modem connection would only be used for Internet connection -- WideFS doesn't use that. If you don't have two Ethernet ports on the connected PC, just use a cheap switch. BTW, what exactly is "cute" about my question? Pete Link to comment Share on other sites More sharing options...
Rick S. Posted March 5, 2017 Author Report Share Posted March 5, 2017 On 2/2/2017 at 7:11 PM, Pete Dowson said: How do you manage to read the screen from 25 feet away? Pete Asking how I see it from 25ft away. Twisted patch cable is not an option so I'll just deal with it. Thanx. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now