sbclark

Pete, I discovered that my Server and Client were setup on "Private" networks, so no issue there.......but still had a problem. However, I just happen to stumble on this video that solved my mystery. It is approximately 11 minutes long and the critical part that fixed my issue is when I enabled "Choose media Streaming options" at the 3:39 mark. https://www.youtube.com/watch?v=uNeo7O6ImAo In the video it also showed how to change from Private to Public or vice versa. Bill Clark

Pete, Looks like I'm off to Google Land! Thanks, Bill Clark

Pete, Thanks so far. After exploring the firewalls on both the Server side and Client side, I discovered that by ONLY turning OFF the “Public” Firewall in the Server PC, I can connect the WideFS to P3D 100% of the time, no matter what the other settings are. This simple matrix, I hope, explains it pretty well: Server Firewall Private ON or OFF ON or OFF Public OFF ON Client Firewall Private ON or OFF ON or OFF Public ON or OFF ON or OFF WideFS Connect? YES NO I’m not quite sure how I can fix this other than turning OFF the Server Public Firewall. I would rather not have to do that, any ideas? The Server IP address is correct 192.168.1.57 Bill Clark Below is the wide server log file you requested. WideServer.log ********* WideServer.DLL Log [version 7.075] ********* Blocksize guide = 8192 (double allowed) Date (dmy): 04/06/18, Time 09:13:52.267: Server name is KILLER-PC 15266 Initialising TCP/IP server 15266 Initialising UDP/IP server 16031 Broadcasting service every 1000 mSecs 427094 Closing down now ... Memory managed: Offset records: 190 alloc, 188 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 *********

Hi Pete, I’ve been using FSUIPC and WideFS for years, but after installing a new router on my network, and a Win10 Spring update on my client PC running Pilot2ATC and Wide FS, Wide FS no longer connects. Some basic system configuration information: -Win10 on both the server and client PC -Running P3D v4.1 -Running ActiveSky on client (it works correctly) - Running Pilot2ATC on client (can’t connect without WideFS) -Can look at files on both PC ‘s from either PC – network works, or seems to! I worked well prior to these two changes. If you have any suggestions to offer, I would love to hear them? Bill Clark Below are three log files: WideClient.log: ********* WideClient Log [version 7.146] Class=FS98MAIN ********* Date (dmy): 04/06/18, Time 09:14:03.704: Client name is MOOSE-PC 171 LUA: "C:\WideFS\WideFS\Initial.LUA": not found 187 Attempting to connect now 187 Trying to locate server: Need details from Server Broadcast 187 Failed to connect: waiting to try again 1218 Attempting to connect now 6296 Server = KILLER-PC 6296 Trying TCP/IP host "KILLER-PC" port 8002 ... 6296 ... Okay, IP Address = 192.168.1.57 27312 Error on client pre-Connection Select() [Error=10060] Connection timed out 27312 Ready to try connection again 28328 Attempting to connect now 28328 Giving up server, looking for another! 28328 Server = KILLER-PC 28328 Trying TCP/IP host "KILLER-PC" port 8002 ... 28328 ... Okay, IP Address = 192.168.1.57 50406 Server = KILLER-PC 50406 Trying TCP/IP host "KILLER-PC" port 8002 ... 50406 ... Okay, IP Address = 192.168.1.57 72468 Giving up server, looking for another! 72468 Server = KILLER-PC 72468 Trying TCP/IP host "KILLER-PC" port 8002 ... 72468 ... Okay, IP Address = 192.168.1.57 94546 Server = KILLER-PC 94546 Trying TCP/IP host "KILLER-PC" port 8002 ... 94546 ... Okay, IP Address = 192.168.1.57 116593 Giving up server, looking for another! 116593 Server = KILLER-PC 116593 Trying TCP/IP host "KILLER-PC" port 8002 ... 116593 ... Okay, IP Address = 192.168.1.57 138609 Server = KILLER-PC 138609 Trying TCP/IP host "KILLER-PC" port 8002 ... 138609 ... Okay, IP Address = 192.168.1.57 160625 Giving up server, looking for another! 160625 Server = KILLER-PC 160625 Trying TCP/IP host "KILLER-PC" port 8002 ... 160625 ... Okay, IP Address = 192.168.1.57 182671 Server = KILLER-PC 182671 Trying TCP/IP host "KILLER-PC" port 8002 ... 182671 ... Okay, IP Address = 192.168.1.57 204718 Giving up server, looking for another! 204718 Server = KILLER-PC 204718 Trying TCP/IP host "KILLER-PC" port 8002 ... 204718 ... Okay, IP Address = 192.168.1.57 226796 Server = KILLER-PC 226796 Trying TCP/IP host "KILLER-PC" port 8002 ... 226796 ... Okay, IP Address = 192.168.1.57 248843 Giving up server, looking for another! 248843 Server = KILLER-PC 248843 Trying TCP/IP host "KILLER-PC" port 8002 ... 248843 ... Okay, IP Address = 192.168.1.57 270890 Server = KILLER-PC 270890 Trying TCP/IP host "KILLER-PC" port 8002 ... 270890 ... Okay, IP Address = 192.168.1.57 292921 Giving up server, looking for another! 292921 Server = KILLER-PC 292921 Trying TCP/IP host "KILLER-PC" port 8002 ... 292921 ... Okay, IP Address = 192.168.1.57 314984 Server = KILLER-PC 314984 Trying TCP/IP host "KILLER-PC" port 8002 ... 314984 ... Okay, IP Address = 192.168.1.57 337000 Giving up server, looking for another! 337000 Server = KILLER-PC 337000 Trying TCP/IP host "KILLER-PC" port 8002 ... 337000 ... Okay, IP Address = 192.168.1.57 359062 Server = KILLER-PC 359062 Trying TCP/IP host "KILLER-PC" port 8002 ... 359062 ... Okay, IP Address = 192.168.1.57 381109 Giving up server, looking for another! 381109 Server = KILLER-PC 381109 Trying TCP/IP host "KILLER-PC" port 8002 ... 381109 ... Okay, IP Address = 192.168.1.57 389187 ****** End of session performance summary ****** 389187 Total time connected = 0 seconds 389187 Reception maximum: 0 frames/sec, 0 bytes/sec 389187 Transmission maximum: 0 frames/sec, 0 bytes/sec 389187 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 389187 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* WideClient0.log: ********* WideClient Log [version 7.146] Class=FS98MAIN ********* Date (dmy): 04/06/18, Time 09:09:06.683: Client name is MOOSE-PC 156 LUA: "C:\WideFS\WideFS\Initial.LUA": not found 234 Attempting to connect now 234 Trying to locate server: Need details from Server Broadcast 234 Failed to connect: waiting to try again 1234 Attempting to connect now 2281 Server = KILLER-PC 2281 Trying TCP/IP host "KILLER-PC" port 8002 ... 2281 ... Okay, IP Address = 192.168.1.57 23312 Error on client pre-Connection Select() [Error=10060] Connection timed out 23312 Ready to try connection again 24375 Attempting to connect now 24375 Giving up server, looking for another! 24375 Server = KILLER-PC 24375 Trying TCP/IP host "KILLER-PC" port 8002 ... 24375 ... Okay, IP Address = 192.168.1.57 39437 ****** End of session performance summary ****** 39437 Total time connected = 0 seconds 39437 Reception maximum: 0 frames/sec, 0 bytes/sec 39437 Transmission maximum: 0 frames/sec, 0 bytes/sec 39437 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 39437 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* FSUIPC5.log: ********* FSUIPC5, Version 5.131 (17th May 2018) by Pete Dowson ********* Running inside Prepar3D v4 Module base=7FFA39990000 Windows 10 Pro 64 Bit reported as Build 16299, Release ID: 1709 (OS 10.0) Prepar3D.exe version = 4.1.7.22841 Reading options from "C:\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.ini" Checking the Registrations now ... User Name="Bill Clark" User Addr="sbclark-ext@cox.net" FSUIPC5 Key is provided WideFS7 Key is provided 0 System time = 04/06/2018 09:12:55 16 FLT UNC path = "\\KILLER-PC\Prepar3D v4 Files\" 16 Using PDK events 16 Using DialogMode 32 FS UNC path = "\\KILLER-PC\Prepar3D v42\" 94 ---------------------- Joystick Device Scan ----------------------- 94 Product= HOTAS Cougar Joystick 94 Manufacturer= Thrustmaster 94 Vendor=044F, Product=0400 (Version 1.16) 110 GUIDs returned for product: VID_044F&PID_0400: 110 GUID= {5FA1F0D0-E1B8-11E7-8001-444553540000} 110 Details: Btns=28, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X65535,Y65535,Z255 110 ------------------------------------------------------------------- 125 Device acquired for use: 125 Joystick ID = 0 (Registry okay) 125 0=Thrustmaster HOTAS Cougar 125 0.GUID={5FA1F0D0-E1B8-11E7-8001-444553540000} 125 ------------------------------------------------------------------- 141 LogOptions=00000000 00000001 141 ------------------------------------------------------------------- 141 SimConnect_Open succeeded: waiting to check version okay 141 Opened separate AI Traffic client okay 13688 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.1.7.22841 (SimConnect: 4.1.0.0) 13688 Initialising SimConnect data requests now 13688 FSUIPC Menu entry added 13688 ... Using Prepar3D with Academic License 13703 \\KILLER-PC\Prepar3D v4 Files\KSAN F-16.fxml 13719 \\KILLER-PC\Prepar3D v42\SimObjects\Airplanes\F-16AM\F-16 F100 CAT-I.air 55235 Loading Complete ... 55875 User Aircraft ID 2 supplied, now being used 55875 Aircraft loaded: running normally now ... 56141 System time = 04/06/2018 09:13:51, Simulator time = 09:13:09 (16:13Z) 56141 Aircraft="Lockheed Martin F-16AM - Orange Demo" 57141 -------------------- Starting everything now ---------------------- 57141 ASN active function link set 57141 Ready for ActiveSky WX radar with additional data 58282 Advanced Weather Interface Enabled 461828 Sim stopped: average frame rate for last 406 secs = 30.0 fps 461828 Max AI traffic was 8 aircraft (Deleted 0) 464172 === Closing session: waiting for DLLStop to be called ... 480578 === DLLStop called ... 480578 === Closing external processes we started ... 481578 === About to kill any Lua plug-ins still running ... 481719 === Closing global Lua thread 482735 === About to kill my timers ... 482938 === Restoring window procs ... 482938 === Unloading libraries ... 482938 === stopping other threads ... 482938 === ... Button scanning ... 483032 === ... Axis scanning ... 483141 === Releasing joystick devices ... 483141 === Freeing macro memory 483141 === Removing any offset overrides 483141 === Closing all WideFS threads 484485 === Clearing any displays left 484485 === NOTE: not calling SimConnect_Close ... 484485 === AI slots deleted! 484485 === Freeing button memory ... 484485 === Closing my Windows ... 484485 === Freeing FS libraries ... 485485 === Closing devices ... 485485 === Closing the Log ... Bye Bye! ... 485485 System time = 04/06/2018 09:21:00, Simulator time = 09:19:54 (16:19Z) 485485 *** FSUIPC log file being closed Minimum frame rate was 30.0 fps, Maximum was 36.6 fps Average frame rate for running time of 406 secs = 30.0 fps Maximum AI traffic for session was 8 aircraft Memory managed: 190 Allocs, 189 Freed ********* FSUIPC Log file closed ***********

Yes it works.................thanks for your help! Bil

Pete, One last question question. I notice that the log file in WideFS is always looking for the server IP address. Which section do I place the following entry ServeriPaddr=xx.xx.xx.xx in the WideFS.ini file? I have setup all my devices to use static IP addresses. Bill Clark

Hi Pete, Got this "KeySend" feature working...........created a profile for PMDG and setup all of my 737's, 777's and 747-400 to work with one standard setup The only question I have, is using the comma character (,) going to create an issue for me that you can foresee? It is one of my unused characters I assigned to this Press-to-talk feature. Bill Clak

Hi Pete, I’m the original poster. I have looked at thread below with the same/similar question posted in your forum which gives me a pretty good idea of what I need to do to get started. http://forum.simflight.com/topic/77225-keysend-over-widefs-not-working/ However, I have a problem as the ThrustMaster Cougar HOTAS is fully programmable. I normally run it in “Button and Axis” Emulation mode which basically sends out characters generated by the HOTAS microprocessor. The beauty is that I can create a downloadable profile for each aircraft generated by the Foxy compiler into the HOTAS memory for execution. M y problem is, the example in the link above is a normal joystick. I can convert my HOTAS into behaving like a standard joystick by taking it out of Emulation mode, but I prefer to run it in Emulation mode. So my question is, is there a way I can assign a key press character and still to use the Key Send feature of FSUIPC4/WideFS? Bill Clark

Thanks Pete, I will check this out. But first I need to fix a P3D issue and defrag my HD. Bill Clark

Pete, I have the latest versions of FSUIPC4 and WideFS installed on my P3D system. I’m running an ATC package called Pilot2ATC (P2A) on a networked PC, and I have a Cougar Joystick on my P3D sim PC What I would like to do is create a “press to talk” capability from my Flight Sim PC (using the Cougar and assigning a button press thru FSUIPC4), and send a held down keypress over the network to be intercepted by WideFS on the network PC and pass on to Pilot2ATC to communicate a request/response? Is this possible? Bill Clark

Are you guys aware that there is a fix for the MCP Pro freezing and lagging digits. I talked to the support Tech and apparently F/W version A25 fixes this issue. Unfortunately, you have to send your unit back to Goflight to update your unit: Here is the post I made on the GoFlight forum. http://www.goflightinc.com/forums/index.php/topic,1156.0.html I to am interested in finding a driver for the PMDG 737 as I have both the EFIS and the MCP Pro.....I have yet to have my firmware updated. I'm going to wait until after Christmas as the mail system will be overloaded. Bill Clark

Andy, If you are having trouble with lockups, check out this GoFlight Link below. I haven't done it yet, but you will need to update your MCP Pro Firmware: http://www.goflightinc.com/forums/index.php/topic,1156.0.html Bill Clark

Steve and Peter, Here is an FYI about the freeze-ups on the GoFlight MCP Pro: I posted this on the GoFlight Forum after talking to their support tech: http://www.goflightinc.com/forums/index.php/topic,1156.0.html Ohsirus, Thanks for your quick response. I just checked with John, the GoFlight Tech, and he confirmed that A25 fixes the freeze problem at the expense of eliminating the serial number. Currently, I'm at version A22 and occasionally have freeze ups, which have been minimized by adding a USB 1.1 card. Unfortunately, if I update to the latest version now, my MCP Pro will probably no longer work with the Flightsims Lab driver I have for my PMDG 747-400 as there is no serial number with the update. Currently, I've migrated to the PMDG 737NGX which doesn't have software support yet from GoFlight either, although there is someone working on some sort of script file for it. I saw your response about Flightsim Labs position on this, which is unfortunate. My take on this is that new users who now purchase the MCP Pro (I assume new units are shipping with A25), won't be able to buy the driver from Flighsims lab because it won't work. This would mean no future business opportunities for either the FSX PMDG 747 or the FS9 PMDG 737. Only those prospective customers with older units would be compatible with the driver. So Flightsims lab is shutting out new business opportunities and also prohibiting existing customers who have their MCPPro units upgraded to A25 to fix te freezing issue from using their units with these two PMDG planes. Bill

Pete, I did what you said; I made both these segments the same as you see below. Unfortunately, many of my key presses now no longer work. If I change it back to the original as per my message at the top of this thread, then they work. The name of the aircraft is correct. Bill Clark [Keys.F1_Cessna_Mustang1] 2=48,10,66777,0 3=73,10,66756,0 5=74,9,66757,0 6=78,9,66758,0 7=112,9,66759,0 8=113,9,66760,0 10=53,26,66750,0 11=54,26,66751,0 12=55,26,66752,0 13=56,26,66753,0 14=57,26,66754,0 15=48,26,66755,0 16=49,24,66749,0 17=50,24,66748,0 [Keys.F1_Cessna_Mustang1] 1=48,8,66776,0 2=117,10,66784,0 3=117,9,66785,0 4=118,10,66786,0 5=118,9,66787,0 6=119,10,66788,0 7=119,11,66778,0 8=120,11,66780,0 9=119,9,66779,0 10=120,10,66781,0 11=120,9,66782,0 12=121,11,66783,0 13=65,26,66789,0 14=66,26,66790,0 15=67,26,66791,0 16=68,26,66792,0 17=69,26,66793,0 18=70,26,66794,0 19=71,26,66795,0

Thank you Sir! Bill