geoffkent

Ok John, thanks for your help, and the additional information. It’s working well. Geoff

Hello, I'm in the process of assigning keyboard keys to EFIS funtions. In PMDG_NG3_SDK.h, I found the third-party event EFIS_CPT_RANGE to set the position of the EFIS RANGE switch, but it has one parameter for each of the eight positions and it wouldn't make sense to assign eight keys. What I'm looking for are control events to increase/decrease the range switch position - two keys. If something like that exists, could someone please point me in the right direction? Many thanks, Geoff Kent Ok, got it. I need to use mouse click parameters.

Thanks Pete, So I just assign a PTT control to my joystick button, and Squawkbox on the client picks it up - that's great. And I've updated to the latest version - thanks for pointing that out. Cheers Geoff

Hello Peter, I seem to be having a WideFS problem after reinstalling everything after upgrading Win 7 from 32- to 64- bit. Perhaps you can throw some light on it please. I'm running FSX SP2 on a server PC with Squawkbox4 on a client PC. The problem is that Squawkbox won't let me assign a server-side joystick button (or keyboard key)as a PTT key. Here's what I do: In FSUIPC > Buttons + Switches, I assign a joystick button to the FS controls "PTT Transmit On" and "PTT Transmit Off" (you can check the assignment in the last few lines of the FSUIPC4 log below). In Squawkbox > Options > Voice tab, I open the "Set..." window for the Push-To-Talk Key. Then I operate the joystick button, expecting the window to close and the key to be assigned, but nothing happens - Squawkbox doesn't register the button action coming from the server. So then I press instead a server-side keyboard key and again nothing happens. I can, of course, assign a client-side keyboard key as a PTT key with no problem. Here are some details that might be relevant: FSUIPC (V4.60a) and WideFS are both registered. I'm running 64-bit Windows 7 on both machines. I run FSX, WideClient, and Squawkbox as Administrator. WideServer shows the status "1 connected". Both machines are in the same workgroup and both are assigned static IP addresses. The FSX installation folder is shared with read/write access for Everyone. FSX responds to the joystick button (it sounds the buzzer that indicates I'm using an inactive radio frequency). Squawkbox is able to communicate with FSX (eg the Squawkbox ".COM1" line command can change the FSX COM1 radio frequency). Firewalls on both machines are switched off. I hope you can help, Cheers Geoff ********* WideServer.DLL Log [version 7.60a] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 06/11/11, Time 20:35:05.360: Server name is FRITZ 15756 Initialising TCP/IP server 15756 Initialising IPX/SPX server 15756 IPX/SPX socket() failed [Error=10044] Socket type not supported 15756 Failed to start IPX/SPX Server 15756 Initialising UDP/IP server 16099 Broadcasting service every 1000 mSecs 87968 Incoming connection Accepted ok (skt=9144) TCP 88109 Connected to computer "MATAI" running WideClient version 6.860 (skt=9144) TCP 206124 Error 10053: client socket disconnected at Client: removing (skt=9144) TCP 217309 Close signalled to clients 218401 Closing down now ... Memory managed: Offset records: 111 alloc, 109 free Read buffer usage: 53 alloc, 53 free, max in session: 1 Write buffer usage: 3007 alloc, 3007 free, max in session: 1 Throughput maximum achieved: 30 frames/sec, 772 bytes/sec Throughput average achieved for complete session: 6 frames/sec, 168 bytes/sec Average receive rate from "MATAI": 0 frames/sec, 16 bytes/sec ********* Log file closed ********* ********* WideClient Log [version 6.86] Class=FS98MAIN ********* Date (dmy): 06/11/11, Time 20:36:35.456: Client name is MATAI 140 LUA: "D:\Software\WideClient\Initial.LUA": not found 172 Attempting to connect now 187 Server = FRITZ 218 Trying TCP/IP host "FRITZ" port 8002 ... 218 ... Okay, IP Address = 192.168.1.123 234 Connection made okay! 118311 ****** End of session performance summary ****** 118311 Total time connected = 118 seconds 118311 Reception maximum: 30 frames/sec, 880 bytes/sec 118311 Reception average whilst connected: 24 frames/sec, 612 bytes/sec 118311 Transmission maximum: 0 frames/sec, 167 bytes/sec 118311 Transmission average whilst connected: 0 frames/sec, 21 bytes/sec 118311 Max receive buffer = 443, Max send depth = 1, Send frames lost = 0 118311 ********* Log file closed (Buffers: MaxUsed 2, Alloc 2989 Freed 2989 Refused 0) ********* ********* FSUIPC4, Version 4.60a by Pete Dowson ********* Reading options from "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini" Trying to connect to SimConnect Acc/SP2 Oct07 ... User Name="Geoffrey Kent" User Addr="geoffpkent@gmail.com" FSUIPC4 Key is provided WideFS7 Key is provided Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed DebugStatus=255 63 System time = 06/11/2011 20:55:36 63 FLT UNC path = "\\FRITZ\Flight Simulator X Files\" 63 FS UNC path = "\\FRITZ\Microsoft Flight Simulator X\" 1092 LogOptions=40000000 00000001 1092 SimConnect_Open succeeded: waiting to check version okay 3323 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 3323 Initialising SimConnect data requests now 3323 FSUIPC Menu entry added 3604 \\FRITZ\Flight Simulator X Files\C152 Gloucestershire.FLT 3604 \\FRITZ\Microsoft Flight Simulator X\SimObjects\Airplanes\jf_C152_INSIDER\jfc152.AIR 142195 System time = 06/11/2011 20:57:58, Simulator time = 20:55:40 (20:55Z) 142195 Aircraft="jfC152_INSIDER" 142819 Advanced Weather Interface Enabled 299179 Button changed: bRef=0, Joy=0, Btn=4, Pressed 299179 [buttons] 1=P0,4,C1068,0 299179 FSUIPC Control Action: Ctrl=1068, Param=0 299460 Button changed: bRef=0, Joy=0, Btn=4, Released 299460 [buttons] 2=U0,4,C1069,0 299460 FSUIPC Control Action: Ctrl=1069, Param=0

It turns out that Windows 7 runs the older Vista workgroup functionality in parallel with the new Homegroup. I had assume the latter had replaced the former. Having stumbled on the fact that my Windows 7 PC actually had a workgroup name, the rest was easy. I just changed the default workgroup name to that of my Vista PC and I now have a connection. Thanks for pointing out that it was probably a workgroup problem. Cheers Pete, Geoff

Hello Pete, I hear your frustration - sorry about that. But I had read your installation instructions and understood them, apart from some of the networking detail. I've been using WideFS for a couple of years and was able to install it before without any special configuration. This is a reinstallation, however, where Windows 7 is my FS PC and Vista my client. As you say, the problem lies in that they are not in the same Workgroup. That's why I haven't yet experimented with some of the network setup suggestions in your documentation. As you probably know, Windows 7 lets you set up a 'Homegroup' rather than a Workgroup. A Homegroup will network only with another Windows 7 Homegroup. I already have file sharing set up between the two PCs, but maybe that's not enough for WideFS to communicate. So I'll play around with specifying a ServerName/Protocol in the client ini, and/or work out how to get Vista and Windows 7 thinking they are in the same Workgroup/Homegroup. And I'll let you know how I get on. Cheers Geoff

Hello Peter, a familiar story to you, I'm sure... WideServer: waiting for clients WideClient FS98 Eliminator - Waiting for a connection The server is a Windows 7 PC running FS9. The client is a Vista laptop. After a couple of hours trying to get this going, I don't know where I am any more. Maybe the following ini files and logs will shed some light. You'll find IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family in the WideServer.log Thanks for your help. Geoff * The WideServer.ini ; PLEASE SEE the documentation for parameter details ; ================================================== [Config] Port=8002 AdvertiseService=1 AutoRestart=0 AutoUpdateTime=13 MaximumBlock=4096 NoStoppedRestarts=Yes Port2=9002 RestartTime=10 SendTimeout=15 TCPcoalesce=No ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== * The WideServer log ********* WideServer.DLL Log [version 6.75] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 12/11/09, Time 20:32:58.740: Server name is FRITZ 36551 Initialising TCP/IP server 36566 Initialising IPX/SPX server 36566 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 36566 Failed to start IPX/SPX Server 36566 Initialising UDP/IP server 38282 Broadcasting service every 1000 mSecs 48048 Restarting service due to total lack of use 48048 Failed to start IPX/SPX Server * The WideClient .ini ; PLEASE SEE WideFS documentation for parameter details ; ===================================================== [Config] Port=8002 Window=43,44,886,589 Visible=Yes ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== * The WideClient.log ********* WideClient Log [version 6.75] Class=FS98MAIN ********* Date (dmy): 12/11/09, Time 18:51:17.834: Client name is MATAI 967 Attempting to connect now 1981 Trying to locate server: Need details from Server Broadcast 1981 Failed to connect: waiting to try again 4024 Attempting to connect now 69248 Trying to locate server: Need details from Server Broadcast