Jump to content
The simFlight Network Forums

ckovoor

Members
  • Posts

    121
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by ckovoor

  1. Dear Pete, I spent the last few hours consolidating all the Lua files for the PMDG B747v3: (1) all the files communicating with the XML Gauge files into a single Lua file (2250 lines of code). (2) all the files on both input and output sides of the hardware MCP-EFIS-DSP into a single Lua file (about 750 lines of code). I used different handles for distinct COM channels as you advised. (3) all the files on both input and output sides of the hardware radio-nav console into a single Lua file (again, different handles). And then I ran them, and it all worked perfectly, and the performance, is, if anything, better than before! I mean the displays, and the controls appear more rapidly responsive than before. So I shall be following your initial advice to consolidate/rationalize all the LUA files across my system, and return them (in their much smaller numbers ­čśë) to the Modules folder which is their ideal home. And in this way stay far away from the 127 file limit. I'll look into the other suggestions/points also, over the next few days. Thanks for your help and support! Regards, Chakko.
  2. Hi Roman, Many thanks for your suggestion. To test your idea quickly, I wrote a Lua entitled killLua.lua containing the instruction, in the first instance: ipc.writeSTR(0x0D70, "LuaKill LuaB747v3\\B747v3RearPedstl"), and ran it after assigning it to a button press, but to no effect. I also tried, in the second instance: ipc.macro("LuaKill LuaB747v3\\B747v3RearPedstl"), again, to no effect. So maybe this will not work for Lua files located outside the Modules folder. ......... Dear Pete, Most of the Lua files which make up the initial 127 are, in fact, files communicating with Arduinos on dedicated COM ports, and for that reason, as far as I know, they cannot be combined. In this set of 18 Lua files for the PMDG 747, 10 of these are files are communicating with 9 distinct Arduinos on 9 distinct COM ports. And that is pretty much the same for all the other aircraft I fly. With some aircraft using INS units, there are more COM channels involved. I agree that with the Lua 's dealing with Gauge files and Panels, I might be able to combine some of them, but that is going to result in some massively long files, and experience with this has taught me to keep things modular. In any case I'd still go over 127 because of the Arduino-related files. ........... Thanks and Regards, Chakko.
  3. I plead "Not Guilty" to the charge of profligacy in spawning Lua plugins. I operate a touchscreen-based system with 6 monitors on a Server PC, and 10 monitors and 7 additional PC's on a WidevieW/WideFS network. A video of its operation in the case of the PMDG 747-400 (QOTS II v3) can be seen here: https://www.youtube.com/watch?v=saFJ_xGBDTs and should give you an idea of it's complexity. In the case of the PMDG 747-400 v3 here is the [Auto] section of the 747v3.ini file located in Modules\Profiles with a justification for each Lua plugin: [Auto] 1=Lua LuaB747v3\\b747v3inputsL 2=Lua LuaB747v3\\b747v3inputsR 3=Lua LuaB747v3\\B747v3outputs1 4=Lua LuaB747v3\\B747v3outputs2 5=Lua LuaB747v3\\B747v3Overhead 6=Lua LuaB747v3\\B747v3Captain 7=Lua LuaB747v3\\B747v3Copilot 8=Lua LuaB747v3\\B747v3Centre 9=Lua LuaB747v3\\B747v3Quadrant 10=Lua LuaB747v3\\B747v3RearPedstl 11=Lua LuaB747v3\\B747v3_RN1 12=Lua LuaB747v3\\B747v3_RN2 13=Lua LuaB747v3\\B747v3_RNinputs 14=Lua LuaB747v3\\B747v3lights 15=Lua LuaB747v3\\B747v3Panels 16=Lua LuaB747v3\\B747v3MotorQuad1 17=Lua LuaB747v3\\B747v3MotorQuad2 18=Lua LuaB747v3\\B747v3ATstate (1) For the B744 MCP-EFIS-DSP hardware unit I used 4 distinct Arduino Mega 2560 units, each on a dedicated COM port, hence Lua's 1 through 4. (2) I created my own 2-D panel set for the PMDG 747-400 v3, because it did not come with native 2-d panels. I wrote individual .XML Gauge files for the Captain's Panel, Centre Panel, Co-Pilots Panel, Throttle Quadrant, Rear Pedestal, Forward Overhead and Rear Overhead. Each of these gauge files write to custom LVars which are then communicated to the sim via distinct Lua plugins. Hence Lua's 5 through 10. (3) I built a universal radio-navigation hardware console containing 3 Arduino Megas, each on a dedicated COM port. However, as the B747v3 interfaces with this console in a unique way, the 3 associated Lua plugins are unique to this aircraft. Hence Lua's 11 through 13. (4) B747v3lights.lua collects information about external lighting from my Server (cockpit) PC for transmission to the networked external view PC's (using WidevieW) to create coordinated ground illumination effects. (5) B747v3 Panels.lua is there to start the various panel windows of the B747 in specific locations and sizes to overcome certain graphics card issues I face on my system. (6) I recently built a Universal Motorized throttle quadrant (which you can see in development here: https://youtu.be/xM2Jp8nfjdA ) which requires a unique set of Lua's to interface with each particular aircraft that it is being used with. It contains 2 Arduino Mega's, hence Lua's 16 and 17. I also had to write another Lua to determine the Autothrottle state, in order to know when to power the stepper motors. This Lua communicates with an autoit script which extracts this information by pixel detection (method I described here: https://forum.simflight.com/topic/78417-lua-for-pixel-analysis/ and the basic issue is brought up here: https://forum.simflight.com/topic/92628-programmatically-discovering-whether-the-autothrottle-is-active-in-the-pmdg-747-400-v3/ ) Now, when I reveal that I also operate the PMDG B777-200, PMDG MD-11, PMDG 737-800, Level-D B767-300, FSLabs A320, SimCheck A300B4-203, Digital Aviation Fokker 100, Majestic Dash 8 Q400, Flight One ATR 72-500, and Aerosoft CRJ 700, and that I have built dedicated MCP's for each of them, and each of them interfaces with the other hardware/software (radio-nav console, throttle quadrant, gauge files, CIVA INS units, Wide View lighting effects) in unique ways, one might wonder how I didn't breach the maximum number of 127 earlier. I should add that apart from the aircraft-specific Lua's that I have mentioned, I also have some common Lua's that I use for all aircraft, and these remain in the Modules folder: like for manipulating scenery on my external-view monitors (refer to this post on network panning: https://forum.simflight.com/topic/81979-wideview-fsx-network-panning-using-fsuipc4-and-widefs/ ). As a matter of fact, I was led to this solution by your own comments in this thread: https://forum.simflight.com/topic/74784-lua-files-are-not-shown-in-fsuipc-gui/ in which you state that "a maximum of 127 Lua files can be assigned -- the first 127 in the list in the INI file. You can have other Lua files, preferably in other folders, which can be called by any of those, or directly in [Auto] sections." Fair enough, I'll try to work with that. To conclude, I have to say that "it is all your fault", Pete, for having brought this extremely powerful programming tool within the ambit of FSUIPC4, which was brilliant enough to start with. I believe I have built a uniquely versatile simulation system, and none of it was achievable without FSUIPC4 and LUA. Thanks and Regards, Chakko.
  4. Hello John and Pete, I'm (still) running FSX-SP2 and Win 7 x64 with registered FSUIPC4.974b. I have lots of hardware (MCP's, throttle quadrants, radio consoles) containing Arduino Mega's, and hence numerous LUA scripts to manage them. So a few days ago, I reached and breached the upper limit of 127 LUA files in the Modules folder. So I created sub-folders for each aircraft within the Modules folder, as for example Modules\LuaB747v3 containing all the Lua files pertaining to that particular aircraft. These LUAs are then started automatically from the Modules\Profiles\B747v3.ini file, thus: [Auto] 1=Lua LuaB747v3\\B747v3inputsL One negative fallout of the this arrangement is that if I need to start or kill a LUA on the fly using a button press (as I often need to do when testing hardware controlled by the Arduinos) I cannot do it as easily as when the LUAs were located in the Modules folder. For in that case I could assign a Lua (run) or LuaKIll to a particular button press and have it run or stop a chosen LUA on the fly. In the new arrangement, in order to run a LUA using a button press, I have to create a LUA file within the Modules folder, say called runLUA.lua containing the command, as for example: ipc.runlua(LuaB747v3\\B747v3inputsL), and then run the LUA by assigning it to a button press. It's cumbersome, but still worthwhile, especially while testing/debugging Arduino-related programs. I see no way of terminating such a LUA externally. So, my question: is there any way of terminating/kiling a Lua file located in a folder other than Modules? Something like an ipc.killLua() command? Thanks and Regards, Chakko.
  5. Hi, I am building a generic Boeing-style motorized throttle quadrant for use with my PMDG B744v3, B772 and B738 and maybe also the MD-11 (in FSX SP2, Win 7x64, with FSUIPC4). The 4 throttle levers and the single speedbrake lever are each geared to a potentiometer which senses the current lever position (0 to 16384) and a NEMA 17 stepper motor which drives the lever when the autothrottle is active. Each throttle lever also supports a reverser lever, connected to a potentiometer sensing its position (0 to -4096). An AT disconnect button is mounted on lever 1, and a TOGA button on lever 2. The flaps lever will be added soon. Here's a photo of the test rig: The hardware is controlled by a single Arduino Mega 2560 R3 in conjunction with five Big Easy Driver boards (to drive the steppers). When the autothrottle is "active", the coils of the stepper motors can be energised, and the throttle levers driven to their target positions. Essentially the system needs to know at all times whether the autothrottle is active (or not), because that determines whether power is to be applied to the stepper motors driving the levers. With the (PMDG) B777-200 this is easily done, because the B772 MCP has a green annunciator on the AT pushbutton switch, which lights up whenever the AT is active, with a corresponding FSUIPC offset (MCP_annunAT = 0x6572 BYTE) which one can read to determine this. So in the case of the PMDG B772 one simply applies power to the steppers whenever 0x6572 == 1, and removes it when it is zero. It seems to work reasonably well, though I am not absolutely certain about its behaviour during AT HOLD mode. With the (PMDG) B747-400, however, there is no equivalent push-button switch or annunciator. In the real world, as I understand it, the pilot would learn about the state of the autothrottle from the AT mode displayed in the first column of the FMA. If the AT mode is one of: THR REF, SPD, THR, or IDLE, then the AT is active and power is to be applied to the stepper coils/servo motors. But if the AT mode is HOLD or blank, then power is to be removed from the coils as the thrust levers should now be able to be moved freely without any resistance. Unfortunately, afaik, there is no way of discovering the AT mode on the FMA by programmatic means, i.e, this information appears not to be accessible by way of the PMDG SDK/FSUIPC offsets. So my question is this: is there any other way of discovering, absolutely, whether the AT is active? I am particularly interested in the response of RW 747 pilots who have a deeper understanding of the system logic, and of cockpit-builders who might already have encountered this problem and maybe have a solution. Here is the relevant information that is provided by the PMDG 744 SDK through readable FSUIPC offsets: 659D 1 BYTE MCP_IASBlank (=1 when IAS/M display blanked out) 65A7 1 BYTE MCP_ATArm_Sw_On 65C2 1 BYTE MCP_annunTHR 65C3 1 BYTE MCP_annunSPD 65C5 1 BYTE MCP_annunVNAV 65C6 1 BYTE MCP_annunFLCH 65C8 1 BYTE MCP_annunVS 65C9 1 BYTE MCP_annunALT_HOLD Thanks, Chakko. (also posted on the PMDG 747v3 forum)
  6. Dear Pete, I attach separate zip folders for each of PMDG B737v1.2, B747v3.0 and B777v1.1, with the simulator restarted each time, and running FSUIPC 4.975a. Please note that I did not connect the Arduino-based MCP/EFIS/DSP hardware each time, so the log files may contain the LUA error: bad COM handle, which can be ignored. Please let me know if I can provide any further information. Chakko. B737v1.2.zip B747v3.0.zip B777v1.1.zip
  7. Dear Pete, I started FSX and loaded the PMDG 737v1.2, waited for it to complete initializing systems, then after about a minute loaded the PMDG 747-400v3.0. A PMDG popup immediately warned that it is not a good idea to load a second PMDG aircraft in succession, but I went on nevertheless, and the 747v3 completed loading. Again, after a minute or so, I tried loading the PMDG 777v1.1, and again ignored the PMDG warning ..... but the 777 did not load completely, i.e. all panels were not displayed, and the menu options stopped working. So I had to shut down FSX. I tried a second time with similar results. It seems that the maximum number I can load in succession is 2 PMDG aircraft. So would it be okay if I sent you a separate log for each aircraft, with the sim restarted each time? Or would you want me to load them in pairs, like 737-747, 747-777 and 737-777? I await your instructions. Chakko.
  8. Dear Pete, First, thank you very much for looking into this. I shall be loading FSUIPC 4.975a and test-logging with the PMDG 737, 747 and 777, as I have all three, and will provide you with the zipped files, soon. I am not sure why you have provided the FSUIPC 4.974b (dll), as I already have that, and I have mentioned in this thread that the problem does not occur with that version. The problem is only with FSUIPC 4.975a, and simply replacing that DLL with FSUIPC 4.974b clears the issue. Also, as mentioned in the other thread concerning the B777 at : https://forum.simflight.com/topic/90304-pmdg-777-fsuipc-offsets-not-updating/?do=findComment&comment=546961 , the same problem occurs with the B777, but not the B737. That is, the B737 functions normally with FSUIPC 4.975a, but the B777 does not. Anyhow, I'll work on getting you the logs now. Thanks, Chakko.
  9. @AirPanther Hi, I can confirm that my PMDG 777-200LR v.1.10 suffers from the same lack of access to FSUIPC offsets as my PMDG 747-400 v.3.00 in FSX SP2 and FSUIPC 4.975a and Win7x64. The Event ID's for controls (on the input side) seem to work, but many of the "PMDG specific" FSUIPC offsets (for displays and annunciators on the output side) are clearly not being read/accessed. The problem disappears immediately when I replace FSUIPC 4.975a with FSUIPC 4.974b (which is the last one I had downloaded prior to 4.975a). I should mention that I also have the PMDG 737-800 NGX v.1.20 in FSX SP2 and Win7x64, but that airplane seems to work normally and the "PMDG specific" FSUIPC offsets are successfully read with FSUIPC 4.975a. Chakko.
  10. @AirPanther : I wonder whether your issue is related to a similar one I am facing with the PMDG 747v3 (offsets) in FSX SP2 and FSUIPC 4.975a that I reported at: https://forum.simflight.com/topic/89157-fsuipc-pmdg747v3-missing-offsets/?do=findComment&comment=544470 I shall try using FSUIPC 4.975a with my own PMDG 777 and get back to you. Chakko.
  11. I have created Voice-Interactive Checklists (using Windows Speech Recognition and Text-to-Speech facilities) for a variety of airplanes in FSX, though not by using this LUA script, but using a third party freeware: VoiceMacro. For details please visit: https://voicemacro.net/ and then proceed to my post in the VoiceMacro forums at: https://voicemacro.net/ForumVM/discussion/405/flight-simulator-co-pilot-for-cockpit-checklists-fsx-and-windows-7-x64#latest Checklists and Profiles I have already created for some common aircraft are referenced here: PMDG B747-400: https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/pmdg-747-queen-of-the-skies-ii-forum/71104-voice-interactive-checklists-for-the-b747-400-qots-ii PMDG B737-800 NGX: https://forum.pmdg.com/forum/main-forum/pmdg-737-ngx/75062-voice-interactive-checklists-for-pmdg-b737-800-ngx PMDG MD-11: https://forum.pmdg.com/forum/main-forum/pmdg-legacy-products/67885-voice-interactive-checklists-for-the-pmdg-md-11 SimCheck A300B4: https://forum.aerosoft.com/index.php?/topic/154190-voice-interactive-checklists-for-simcheck-a300b4/&tab=comments#comment-986217 Flight One ATR72-500: http://atr.flight1.net/forums/voiceinteractive-checklists-for-flight1-atr72500_topic6739.html?SID=10078-f5dc6bdea27f27a7bdf42075462963 Flight Sim Labs A320 X: https://forums.flightsimlabs.com/index.php?/topic/25728-voice-interactive-checklists-for-fslabs-a320x/ Majestic Dash 8 Q400: http://majesticsoftware.com/forums/discussion/793/voice-interactive-checklists-for-mjc8-q400 Level D B767-300: https://www.dropbox.com/sh/51bgejl2j83anjf/AACmtjJDcMbJBLvvcTL7oJMwa?dl=0 PMDG B777-200: https://forum.pmdg.com/forum/main-forum/pmdg-777-forum/71229-voice-interactive-checklists-for-pmdg-b777-200 Chakko Kovoor.
  12. Dear Pete, Apart from this problem with the PMDG B747-400 v3, FSUIPC 4.975a appeared to be functioning normally, but then that is only after a few days of testing, and not with all the aircraft that I fly. I need to do more extensive testing with all the other airplanes I fly before I can be certain. So, I shall stick with FSUIPC 4.974b for the time being, but will sometime soon re-test 4.975a and supply you with Install and Run-Time Logs for you to check. But I will open a separate thread for that. Thanks and Regards, Chakko.
  13. Dear Pete and John, I operate the PMDG B747-400 QOTS II v3 on FSX-SP2 and Win 7 x64 with registered FSUIPC4. The B744v3 from PMDG does not come with 2-D panels so I constructed my own working 2-D panel sets with my own XML gauge code and FSUIPC4-LUA scripts. I also built a hardware MCP+EFIS+DSP unit using Arduino Megas and FSUIPC4-LUA. Of course Pete's documentation for the FSUIPC offsets and the PMDG 747 SDK for Control Event ID's are the backbone of this implementation. You can see the system in operation here: https://www.youtube.com/watch?v=saFJ_xGBDTs Anyway, all was going well with FSUIPC 4.974b until a few days ago when I saw a newer version FSUIPC 4.975a and decided to install it. And immediately thereafter, the B747v3 stopped working properly. Specifically, the inputs and outputs to and from my Hardware and XML gauges were not being read or linked properly to the PMDG software. Replacing the FSUIPC4 DLL with the earlier version 4.974b immediately solved the problem and everything started working again. I switched the modules back and forth a few times, so I can confirm that something has broken, at least as far as the B747v3 in FSX is concerned, in the move from FSUIPC 4.974b to 4.975a. I have posted this report in this thread, because I suspect it may have something to do with the modifications that have been discussed here, which may or may not have been necessary for the FSX version of the B747v3, for which development ceased several months ago. For the time being I am reverting to FSUIPC 4.974b in order to be able to fly this wonderful airplane again. Would you please investigate? Thanks and Regards, Chakko.
  14. Interesting! But isn't Ram Air Pressure (or Total Pressure) = Static Pressure (or Ambient Pressure) + Dynamic Pressure ? So if you needed Ram Air Pressure to feed your hardware with, you would need to add the values as above. Also wouldn't Static Pressure (or Ambient Pressure) be a value which doesn't change very rapidly with time ........ unless, of course, you are travelling very fast indeed (vertically through altitude layers or horizontally across isobars) within the atmosphere? Just my two cents. Chakko.
  15. For a Client running FSX on Windows 10 x64 , keystrokes sent by WideClient were not being intercepted by the LUA. The problem and its solution are described in this thread: https://forum.simflight.com/topic/85961-wideclient-not-transmitting-keystrokes-to-local-fsx-on-networked-client-running-on-windows-10/
  16. I tried this out too...... Extract from WideClient.ini [7.148]: [User] PostKeys=Yes KeySend1=RunKey1 KeySend2=39,8,FS98MAIN KeySend3=37,8,FS98MAIN KeySend4=36,8,FS98MAIN KeySend5=38,8,FS98MAIN KeySend6=40,8,FS98MAI´╗┐N Extract from FSUIPC.ini at Client: [Auto] 1=Lua ´╗┐networkrotation [LuaFiles] 1=networkrotation [Keys] 12=39,8,x010066C0,x01 -{Right: Press=offset byte set, offset 66C0 }- 13=37,8,x010066C1,x01 -{Left: Press=offset byte set, offset 66C1 }- 14=36,8,x010066C4,x01 -{Home: Press=offset byte set, offset 66C4 }- 15=38,8,x010066C3,x01 -{Up: Press=offset byte set, offset 66C3 }- 16=40,8,x010066C2,x01 -{Down: Press=offset byte set, offset 66C2 }- [Programs] Run1=CLOSE,C:\FS Files\WideClient7148\WideClient.exe networkrotation.lua had to be modified to make use of the free FSUIPC user offsets at 0x66C0 - 4. -- initial values lX = 0.0 lY = 0.0 lZ = 0.0 lPitch = 0.0 lBank = 0.0 lHeading = 0.0 -- increments delHdg = 11.25 delPitch = 1 -- camera rotations function rotate_right (offset, value) if value == 1 then lHeading = lHeading + delHdg if lHeading >= 180 then lHeading = lHeading - 360 end set_eyepoint () ipc.writeUB (0x66C0, 0) end end function rotate_left (offset, value) if value == 1 then lHeading = lHeading - delHdg if lHeading <= -180 then lHeading = lHeading + 360 end set_eyepoint () ipc.writeUB (0x66C1, 0) end end function rotate_down (offset, value) if value == 1 then lPitch = lPitch - delPitch if lPitch < -90 then lPitch = -90 end set_eyepoint () ipc.writeUB (0x66C2, 0) end end function rotate_up (offset, value) if value == 1 then lPitch = lPitch + delPitch if lPitch > 90 then lPitch = 90 end set_eyepoint () ipc.writeUB (0x66C3, 0) end end function rotate_reset (offset, value) if value == 1 then lPitch = 0.0 lHeading = 0.0 set_eyepoint () ipc.writeUB (0x66C4, 0) end end -- set the eyepoint function set_eyepoint () ipc.writeStruct( 0x86A0 , "6FLT" , lX , lY , lZ , lPitch , lBank , lHeading ) -- X, Y, Z, P, B, H end event.offset ( 0x66C0, "UB", "rotate_right") event.offset ( 0x66C1, "UB", "rotate_left") event.offset ( 0x66C2, "UB", "rotate_down") event.offset ( 0x66C3, "UB", "rotate_up") event.offset ( 0x66C4, "UB", "rotate_reset") The result is marginally better than the earlier one, in that the lagginess appears to have decreased slightly, though it is still there. But of course, the lagginess might have other causes, stemming from the Windows 10 environment, rather than have anything to do with the FSUIPC-WideFS-Lua method. Whatever it is, I am happy to have got it working on Windows 10. Thank you, as always, Pete, for your outstanding program and the help and support you give us. Regards, Chakko.
  17. Hi Pete, I seem to have found a workaround or a temporary solution to the problem I am facing. Realizing that the essential problem in my setup is that Postkeys=Yes allows WideFS to communicate stably and consistently with FSX/FSUIPC through the medium of FSUIPC Controls, rather than KeyPresses, I surmised that the reason that my networkrotation.LUA was not working consistently in intercepting and acting on the KeyPresses must be that event.key() suffers from some inability to trap the WideClient-sent Keypresses consistently in a Win 10 environment. So I tried event.control() instead, thus: Extract from WideClient.ini [7.148]: [User] PostKeys=Yes KeySend1=RunKey1 KeySend2=39,8,FS98MAIN KeySend3=37,8,FS98MAIN KeySend4=36,8,FS98MAIN KeySend5=38,8,FS98MAIN KeySend6=40,8,FS98MAIN Extract from FSUIPC.ini at Client: [Auto] 1=Lua networkrotation [LuaFiles] 1=networkrotation [Keys] 12=39,8,65672,0 -{Right: Press=PAN_RIGHT }- 13=37,8,65671,0 -{Left: Press=PAN_LEFT }- 14=36,8,65875,0 -{Home: Press=PAN_RESET }- 15=38,8,65735,0 -{Up: Press=PAN_DOWN }- 16=40,8,65734,0 -{Down: Press=PAN_UP }- [Programs] Run1=CLOSE,C:\FS Files\WideClient7148\WideClient.exe Event section from networkrotation.lua (other parts unchanged): event.control ( 65672, "rotate_right") event.control ( 65671, "rotate_left") event.control ( 65734, "rotate_down") event.control ( 65735, "rotate_up") event.control ( 65875, "rotate_reset") The solution is clumsy in that the FSUIPC PANning control is being intercepted and 'reinterpreted' by the LUA, and there appears to be a slight lag at the Client as a result, but at least it is synchronised with the other 6 views generated by my other Clients (not running Windows 10). I look forward to your comments. Thanks and Regards, Chakko.
  18. Dear Pete, As a matter of fact, I am using neither the default FSX assignments nor the FSUIPC assignments for view-panning. As recounted in the original thread at: https://forum.simflight.com/topic/81979-wideview-fsx-network-panning-using-fsuipc4-and-widefs/ we did try those out initially, but found that as the Panning command is a time-based command, it resulted in view-mismatches across the 7 networked Clients I have on my system. So we switched to using the SimConnect_CameraSetRelative6DOF function instead, actioned by a LUA entitled networkrotation at the Client FSUIPC. This networkrotation.lua uses event.key() to intercept key-presses sent by the local WideClient. I now realize that in a later post in the thread I had described the modified process, and should have reproduced that here for your reference: Summary of Process: When a panning-command (via Hat-Switch button) is applied at the SERVER, FSUIPC-WideServer sends a KeySend number to all networked Clients. At each CLIENT, WideClient receives the KeySend number and sends a key-press to FSX-FSUIPC. An auto-started LUA script intercepts this key-press and rotates the view appropriately using the SimConnect_CameraSetRelative6DOF function. Certain options in the wideviewx.ini file at the CLIENTs and SERVER need to be set to ensure that it does not interfere. A new Camera Definition is also installed on the CLIENT(s) to keep this option separate. So, at each WideClient: [User] KeySend2=39,8,FS98MAIN KeySend3=37,8,FS98MAIN KeySend4=36,8,FS98MAIN KeySend5=38,8,FS98MAIN KeySend6=40,8,FS98MAIN and from there to this LUA auto-started by the local FSUIPC4: -- initial values lX = 0.0 lY = 0.0 lZ = 0.0 lPitch = 0.0 lBank = 0.0 lHeading = 0.0 -- increments delHdg = 11.25 delPitch = 5 -- camera rotations function rotate_right () lHeading = lHeading + delHdg if lHeading >= 180 then lHeading = lHeading - 360 end set_eyepoint () end function rotate_left () lHeading = lHeading - delHdg if lHeading <= -180 then lHeading = lHeading + 360 end set_eyepoint () end function rotate_up () lPitch = lPitch + delPitch if lPitch > 90 then lPitch = 90 end set_eyepoint () end function rotate_down () lPitch = lPitch - delPitch if lPitch < -90 then lPitch = -90 end set_eyepoint () end function rotate_reset () lPitch = 0.0 lHeading = 0.0 set_eyepoint () end -- set the eyepoint function set_eyepoint () ipc.writeStruct( 0x86A0 , "6FLT" , lX , lY , lZ , lPitch , lBank , lHeading ) -- X, Y, Z, P, B, H end event.key ( 39, 8, "rotate_right") event.key ( 37, 8, "rotate_left") event.key ( 40, 8, "rotate_down") event.key ( 38, 8, "rotate_up") event.key ( 36, 8, "rotate_reset") The LUA has worked very reliably, and apart from the uniform rotation across the network views it actions, it also allows me to set the angular increments to my liking. It is only now with the issues that Win 10 has with SetWindowsHookEx that I am having a problem. .......................... But, in order to test your suggestion, I went back to using the FSUIPC assignments thus: [Keys] 12=39,8,65672,0 -{Right: Press=PAN_RIGHT }- 13=37,8,65671,0 -{Left: Press=PAN_LEFT }- 14=36,8,65875,0 -{Home: Press=PAN_RESET }- 15=38,8,65735,0 -{Up: Press=PAN_DOWN }- 16=40,8,65734,0 -{Down: Press=PAN_UP }- along with PostKeys=Yes in WideClient, and YES, IT WORKED to produce reliable panning responses with both 7.15 and 7.148 versions! If you would like, I can forward you the corresponding logs in a subsequent post. However, unfortunately, I don't think this is the best solution for me, because the Pan commands are not synchronised with the LUA rotations that are occurring at my other Client views. I am wondering if there is a way of modifying the current LUA so that it will be reliably responsive to key-presses sent via the PostKeys=Yes method, as the FSUIPC assignments are.....do you think that would that solve my problem? Regards, Chakko.
  19. Dear Pete, I thank you very very much for going into the details of my situation and spending so much of your time to help me. Some personal commitments away from the sim will prevent me from spending much time with it over the next few days, so please forgive me for my slowness in testing the new version of WideClient that you have created solely to help me solve my problem.......but I will get back to you as soon as I possibly can. Thank you for all that you do for me/us. Chakko
  20. Hi Pete, With WideClient 7.15 (Postkeys=Yes and Log = KeySend) and FSUIPC4.974b (with button/key and event logging enabled), I applied around 10 key-presses via WideClient (only the first few elicited a response, and then FSX stopped responding, as before), then around 10 key-presses from the Keyboard (surprisingly, this time the response was sporadic, not all keypresses yielding a response) and then again around 10 via WideClient (only responsive on the first few, as before): ********* WideClient Log [version 7.15] Class=FS98MAIN01 ********* Date (dmy): 12/09/18, Time 17:37:52.176: Client name is INSPIRON3567 140 KeyHook added: 2=39,8,FS98MAIN, 140 KeyHook added: 3=37,8,FS98MAIN, 140 KeyHook added: 4=36,8,FS98MAIN, 140 KeyHook added: 5=38,8,FS98MAIN, 140 KeyHook added: 6=40,8,FS98MAIN, 156 KeyHook added: 259=0,0,, 156 KeyHook added: 260=0,0,, 172 Attempting to connect now 172 LUA: "C:\FS Files\WideClient7148\Initial.LUA": not found 172 Trying TCP/IP host "SERVER" port 8002 ... 172 ... Okay, IP Address = 169.254.152.178 187 Connection made okay! 32156 Post/Send input for KeyHook action 4 32156 WM_KEYDOWN posted to Window 000304f4 ok, VK code 36 32234 WM_KEYUP posted to Window 000304f4 ok, VK code 36 32297 Action request sent 2 events 32297 Checked KeySend[10]=4 35078 Post/Send input for KeyHook action 3 35078 WM_KEYDOWN posted to Window 000304f4 ok, VK code 37 35172 WM_KEYUP posted to Window 000304f4 ok, VK code 37 35234 Action request sent 2 events 35234 Checked KeySend[11]=3 36359 Post/Send input for KeyHook action 2 36359 WM_KEYDOWN posted to Window 000304f4 ok, VK code 39 36453 WM_KEYUP posted to Window 000304f4 ok, VK code 39 36515 Action request sent 2 events 36515 Checked KeySend[12]=2 37453 Post/Send input for KeyHook action 5 37453 WM_KEYDOWN posted to Window 000304f4 ok, VK code 38 37531 WM_KEYUP posted to Window 000304f4 ok, VK code 38 37594 Action request sent 2 events 37594 Checked KeySend[13]=5 38547 Post/Send input for KeyHook action 6 38547 WM_KEYDOWN posted to Window 000304f4 ok, VK code 40 38625 WM_KEYUP posted to Window 000304f4 ok, VK code 40 38687 Action request sent 2 events 38687 Checked KeySend[14]=6 39828 Post/Send input for KeyHook action 2 39828 WM_KEYDOWN posted to Window 000304f4 ok, VK code 39 39906 WM_KEYUP posted to Window 000304f4 ok, VK code 39 39969 Action request sent 2 events 39969 Checked KeySend[15]=2 40609 Post/Send input for KeyHook action 2 40609 WM_KEYDOWN posted to Window 000304f4 ok, VK code 39 40687 WM_KEYUP posted to Window 000304f4 ok, VK code 39 40750 Action request sent 2 events 40750 Checked KeySend[0]=2 41672 Post/Send input for KeyHook action 3 41672 WM_KEYDOWN posted to Window 000304f4 ok, VK code 37 41750 WM_KEYUP posted to Window 000304f4 ok, VK code 37 41812 Action request sent 2 events 41812 Checked KeySend[1]=3 42500 Post/Send input for KeyHook action 5 42500 WM_KEYDOWN posted to Window 000304f4 ok, VK code 38 42578 WM_KEYUP posted to Window 000304f4 ok, VK code 38 42640 Action request sent 2 events 42640 Checked KeySend[2]=5 60015 Post/Send input for KeyHook action 3 60015 WM_KEYDOWN posted to Window 000304f4 ok, VK code 37 60094 WM_KEYUP posted to Window 000304f4 ok, VK code 37 60156 Action request sent 2 events 60156 Checked KeySend[3]=3 60625 Post/Send input for KeyHook action 2 60625 WM_KEYDOWN posted to Window 000304f4 ok, VK code 39 60719 WM_KEYUP posted to Window 000304f4 ok, VK code 39 60781 Action request sent 2 events 60781 Checked KeySend[4]=2 61312 Post/Send input for KeyHook action 5 61312 WM_KEYDOWN posted to Window 000304f4 ok, VK code 38 61406 WM_KEYUP posted to Window 000304f4 ok, VK code 38 61469 Action request sent 2 events 61469 Checked KeySend[5]=5 61937 Post/Send input for KeyHook action 6 61937 WM_KEYDOWN posted to Window 000304f4 ok, VK code 40 62015 WM_KEYUP posted to Window 000304f4 ok, VK code 40 62078 Action request sent 2 events 62078 Checked KeySend[6]=6 62625 Post/Send input for KeyHook action 2 62625 WM_KEYDOWN posted to Window 000304f4 ok, VK code 39 62703 WM_KEYUP posted to Window 000304f4 ok, VK code 39 62765 Action request sent 2 events 62765 Checked KeySend[7]=2 63750 Post/Send input for KeyHook action 3 63750 WM_KEYDOWN posted to Window 000304f4 ok, VK code 37 63828 WM_KEYUP posted to Window 000304f4 ok, VK code 37 63890 Action request sent 2 events 63890 Checked KeySend[8]=3 74375 Post/Send input for KeyHook action 4 74375 WM_KEYDOWN posted to Window 000304f4 ok, VK code 36 74453 WM_KEYUP posted to Window 000304f4 ok, VK code 36 74515 Action request sent 2 events 74515 Checked KeySend[9]=4 80109 Post/Send input for KeyHook action 3 80109 WM_KEYDOWN posted to Window 000304f4 ok, VK code 37 80187 WM_KEYUP posted to Window 000304f4 ok, VK code 37 80250 Action request sent 2 events 80250 Checked KeySend[10]=3 80765 Post/Send input for KeyHook action 2 80765 WM_KEYDOWN posted to Window 000304f4 ok, VK code 39 80859 WM_KEYUP posted to Window 000304f4 ok, VK code 39 80922 Action request sent 2 events 80922 Checked KeySend[11]=2 81390 Post/Send input for KeyHook action 5 81390 WM_KEYDOWN posted to Window 000304f4 ok, VK code 38 81469 WM_KEYUP posted to Window 000304f4 ok, VK code 38 81531 Action request sent 2 events 81531 Checked KeySend[12]=5 82047 Post/Send input for KeyHook action 6 82047 WM_KEYDOWN posted to Window 000304f4 ok, VK code 40 82125 WM_KEYUP posted to Window 000304f4 ok, VK code 40 82187 Action request sent 2 events 82187 Checked KeySend[13]=6 82797 Post/Send input for KeyHook action 2 82797 WM_KEYDOWN posted to Window 000304f4 ok, VK code 39 82890 WM_KEYUP posted to Window 000304f4 ok, VK code 39 82953 Action request sent 2 events 82953 Checked KeySend[14]=2 83015 Post/Send input for KeyHook action 2 83015 WM_KEYDOWN posted to Window 000304f4 ok, VK code 39 83094 WM_KEYUP posted to Window 000304f4 ok, VK code 39 83156 Action request sent 2 events 83156 Checked KeySend[15]=2 83172 Post/Send input for KeyHook action 2 83172 WM_KEYDOWN posted to Window 000304f4 ok, VK code 39 83250 WM_KEYUP posted to Window 000304f4 ok, VK code 39 83312 Action request sent 2 events 83312 Checked KeySend[0]=2 83797 Post/Send input for KeyHook action 3 83797 WM_KEYDOWN posted to Window 000304f4 ok, VK code 37 83875 WM_KEYUP posted to Window 000304f4 ok, VK code 37 83937 Action request sent 2 events 83937 Checked KeySend[1]=3 84422 Post/Send input for KeyHook action 5 84422 WM_KEYDOWN posted to Window 000304f4 ok, VK code 38 84500 WM_KEYUP posted to Window 000304f4 ok, VK code 38 84562 Action request sent 2 events 84562 Checked KeySend[2]=5 84953 Post/Send input for KeyHook action 6 84953 WM_KEYDOWN posted to Window 000304f4 ok, VK code 40 85031 WM_KEYUP posted to Window 000304f4 ok, VK code 40 85094 Action request sent 2 events 85094 Checked KeySend[3]=6 91219 ****** End of session performance summary ****** 91219 Total time connected = 91 seconds 91219 Reception maximum: 32 frames/sec, 938 bytes/sec 91219 Reception average whilst connected: 31 frames/sec, 756 bytes/sec 91219 Transmission maximum: 0 frames/sec, 185 bytes/sec 91219 Transmission average whilst connected: 0 frames/sec, 23 bytes/sec 91219 Max receive buffer = 473, Max send depth = 1, Send frames lost = 0 91219 ********* Log file closed (Buffers: MaxUsed 2, Alloc 2950 Freed 2950 Refused 0) ********* and: ********* FSUIPC4, Version 4.974b (14th March 2018) by Pete Dowson ********* User Name="Chakko Kovoor" User Addr="ckovoor@alum,mit.edu" FSUIPC4 Key is provided WideFS7 Key is provided 344469 System time = 12/09/2018 17:38:18, Simulator time = 11:09:22 (06:09Z) 344484 FLT UNC path = "\\INSPIRON3567\Documents\Flight Simulator X Files\" [Continuation log requested by user] Running inside FSX on Windows 10 Module base=5FF60000 350656 KEYDOWN: VK=36, Waiting=0, Repeat=N, Shifts=0 350656 .. Key not programmed -- passed on to FS 350656 *** EVENT: Cntrl= 65607 (0x00010047), Param= 0 (0x00000000) ELEV_TRIM_DN 353609 KEYDOWN: VK=37, Waiting=0, Repeat=N, Shifts=0 353609 .. Key not programmed -- passed on to FS 353609 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 354875 KEYDOWN: VK=39, Waiting=0, Repeat=N, Shifts=0 354875 .. Key not programmed -- passed on to FS 354875 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 355984 KEYDOWN: VK=38, Waiting=0, Repeat=N, Shifts=0 355984 .. Key not programmed -- passed on to FS 355984 *** EVENT: Cntrl= 65608 (0x00010048), Param= 0 (0x00000000) ELEV_DOWN 357047 KEYDOWN: VK=40, Waiting=0, Repeat=N, Shifts=0 357047 .. Key not programmed -- passed on to FS 357047 *** EVENT: Cntrl= 65616 (0x00010050), Param= 0 (0x00000000) ELEV_UP 358344 KEYDOWN: VK=39, Waiting=0, Repeat=N, Shifts=0 358344 .. Key not programmed -- passed on to FS 358344 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 359125 KEYDOWN: VK=39, Waiting=0, Repeat=N, Shifts=0 359125 .. Key not programmed -- passed on to FS 359125 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 360187 KEYDOWN: VK=37, Waiting=0, Repeat=N, Shifts=0 360187 .. Key not programmed -- passed on to FS 360187 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 361000 KEYDOWN: VK=38, Waiting=0, Repeat=N, Shifts=0 361000 .. Key not programmed -- passed on to FS 361000 *** EVENT: Cntrl= 65608 (0x00010048), Param= 0 (0x00000000) ELEV_DOWN 370625 KEYDOWN: VK=37, Waiting=0, Repeat=N, Shifts=0 370625 .. Key not programmed -- passed on to FS 370625 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 370812 KEYUP: VK=37, Waiting=0 371390 KEYDOWN: VK=39, Waiting=0, Repeat=N, Shifts=0 371390 .. Key not programmed -- passed on to FS 371390 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 371594 KEYUP: VK=39, Waiting=0 372500 KEYDOWN: VK=38, Waiting=0, Repeat=N, Shifts=0 372500 .. Key not programmed -- passed on to FS 372500 *** EVENT: Cntrl= 65608 (0x00010048), Param= 0 (0x00000000) ELEV_DOWN 372656 KEYUP: VK=38, Waiting=0 373140 KEYDOWN: VK=40, Waiting=0, Repeat=N, Shifts=0 373140 .. Key not programmed -- passed on to FS 373140 *** EVENT: Cntrl= 65616 (0x00010050), Param= 0 (0x00000000) ELEV_UP 373281 KEYUP: VK=40, Waiting=0 374265 KEYDOWN: VK=39, Waiting=0, Repeat=N, Shifts=0 374265 .. Key not programmed -- passed on to FS 374265 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 374781 KEYUP: VK=39, Waiting=0 375687 KEYDOWN: VK=37, Waiting=0, Repeat=N, Shifts=0 375687 .. Key not programmed -- passed on to FS 375687 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 376219 KEYDOWN: VK=37, Waiting=0, Repeat=Y, Shifts=0 376219 .. Key not programmed -- passed on to FS 376219 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 376265 KEYDOWN: VK=37, Waiting=0, Repeat=Y, Shifts=0 376265 .. Key not programmed -- passed on to FS 376265 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 376312 KEYDOWN: VK=37, Waiting=0, Repeat=Y, Shifts=0 376312 .. Key not programmed -- passed on to FS 376312 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 376359 KEYDOWN: VK=37, Waiting=0, Repeat=Y, Shifts=0 376359 .. Key not programmed -- passed on to FS 376359 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 376406 KEYDOWN: VK=37, Waiting=0, Repeat=Y, Shifts=0 376406 .. Key not programmed -- passed on to FS 376406 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 376406 KEYUP: VK=37, Waiting=0 378515 KEYDOWN: VK=37, Waiting=0, Repeat=N, Shifts=0 378515 .. Key not programmed -- passed on to FS 378515 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 379140 KEYDOWN: VK=39, Waiting=0, Repeat=N, Shifts=0 379140 .. Key not programmed -- passed on to FS 379140 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 379859 KEYDOWN: VK=38, Waiting=0, Repeat=N, Shifts=0 379859 .. Key not programmed -- passed on to FS 379859 *** EVENT: Cntrl= 65608 (0x00010048), Param= 0 (0x00000000) ELEV_DOWN 380484 KEYDOWN: VK=40, Waiting=0, Repeat=N, Shifts=0 380484 .. Key not programmed -- passed on to FS 380484 *** EVENT: Cntrl= 65616 (0x00010050), Param= 0 (0x00000000) ELEV_UP 381156 KEYDOWN: VK=39, Waiting=0, Repeat=N, Shifts=0 381156 .. Key not programmed -- passed on to FS 381156 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 382297 KEYDOWN: VK=37, Waiting=0, Repeat=N, Shifts=0 382297 .. Key not programmed -- passed on to FS 382297 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 383922 KEYDOWN: VK=37, Waiting=0, Repeat=N, Shifts=0 383922 .. Key not programmed -- passed on to FS 383922 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 384437 KEYDOWN: VK=37, Waiting=0, Repeat=Y, Shifts=0 384437 .. Key not programmed -- passed on to FS 384437 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 384484 KEYDOWN: VK=37, Waiting=0, Repeat=Y, Shifts=0 384484 .. Key not programmed -- passed on to FS 384484 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 384531 KEYDOWN: VK=37, Waiting=0, Repeat=Y, Shifts=0 384531 .. Key not programmed -- passed on to FS 384531 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 384594 KEYDOWN: VK=37, Waiting=0, Repeat=Y, Shifts=0 384594 .. Key not programmed -- passed on to FS 384594 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 384640 KEYDOWN: VK=37, Waiting=0, Repeat=Y, Shifts=0 384640 .. Key not programmed -- passed on to FS 384640 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 384687 KEYDOWN: VK=37, Waiting=0, Repeat=Y, Shifts=0 384687 .. Key not programmed -- passed on to FS 384687 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 384687 KEYUP: VK=37, Waiting=0 386109 KEYDOWN: VK=39, Waiting=0, Repeat=N, Shifts=0 386109 .. Key not programmed -- passed on to FS 386109 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 386625 KEYDOWN: VK=39, Waiting=0, Repeat=Y, Shifts=0 386625 .. Key not programmed -- passed on to FS 386625 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 386672 KEYDOWN: VK=39, Waiting=0, Repeat=Y, Shifts=0 386672 .. Key not programmed -- passed on to FS 386672 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 386719 KEYDOWN: VK=39, Waiting=0, Repeat=Y, Shifts=0 386719 .. Key not programmed -- passed on to FS 386719 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 386765 KEYDOWN: VK=39, Waiting=0, Repeat=Y, Shifts=0 386765 .. Key not programmed -- passed on to FS 386765 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 386812 KEYDOWN: VK=39, Waiting=0, Repeat=Y, Shifts=0 386812 .. Key not programmed -- passed on to FS 386812 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 386859 KEYDOWN: VK=39, Waiting=0, Repeat=Y, Shifts=0 386859 .. Key not programmed -- passed on to FS 386859 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 386906 KEYDOWN: VK=39, Waiting=0, Repeat=Y, Shifts=0 386906 .. Key not programmed -- passed on to FS 386906 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 386969 KEYDOWN: VK=39, Waiting=0, Repeat=Y, Shifts=0 386969 .. Key not programmed -- passed on to FS 386969 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 387015 KEYUP: VK=39, Waiting=0 387719 KEYDOWN: VK=38, Waiting=0, Repeat=N, Shifts=0 387719 .. Key not programmed -- passed on to FS 387719 *** EVENT: Cntrl= 65608 (0x00010048), Param= 0 (0x00000000) ELEV_DOWN 388250 KEYDOWN: VK=38, Waiting=0, Repeat=Y, Shifts=0 388250 .. Key not programmed -- passed on to FS 388250 *** EVENT: Cntrl= 65608 (0x00010048), Param= 0 (0x00000000) ELEV_DOWN 388297 KEYUP: VK=38, Waiting=0 388578 KEYDOWN: VK=40, Waiting=0, Repeat=N, Shifts=0 388578 .. Key not programmed -- passed on to FS 388578 *** EVENT: Cntrl= 65616 (0x00010050), Param= 0 (0x00000000) ELEV_UP 388906 KEYUP: VK=40, Waiting=0 389297 KEYDOWN: VK=40, Waiting=0, Repeat=N, Shifts=0 389297 .. Key not programmed -- passed on to FS 389297 *** EVENT: Cntrl= 65616 (0x00010050), Param= 0 (0x00000000) ELEV_UP 389484 KEYUP: VK=40, Waiting=0 389812 KEYDOWN: VK=38, Waiting=0, Repeat=N, Shifts=0 389812 .. Key not programmed -- passed on to FS 389812 *** EVENT: Cntrl= 65608 (0x00010048), Param= 0 (0x00000000) ELEV_DOWN 390062 KEYUP: VK=38, Waiting=0 390594 KEYDOWN: VK=37, Waiting=0, Repeat=N, Shifts=0 390594 .. Key not programmed -- passed on to FS 390594 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 390734 KEYUP: VK=37, Waiting=0 391328 KEYDOWN: VK=39, Waiting=0, Repeat=N, Shifts=0 391328 .. Key not programmed -- passed on to FS 391328 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 391422 KEYUP: VK=39, Waiting=0 392890 KEYDOWN: VK=36, Waiting=0, Repeat=N, Shifts=0 392890 .. Key not programmed -- passed on to FS 392890 *** EVENT: Cntrl= 65607 (0x00010047), Param= 0 (0x00000000) ELEV_TRIM_DN 398640 KEYDOWN: VK=37, Waiting=0, Repeat=N, Shifts=0 398640 .. Key not programmed -- passed on to FS 398640 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 399265 KEYDOWN: VK=39, Waiting=0, Repeat=N, Shifts=0 399265 .. Key not programmed -- passed on to FS 399265 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 399937 KEYDOWN: VK=38, Waiting=0, Repeat=N, Shifts=0 399937 .. Key not programmed -- passed on to FS 399937 *** EVENT: Cntrl= 65608 (0x00010048), Param= 0 (0x00000000) ELEV_DOWN 400562 KEYDOWN: VK=40, Waiting=0, Repeat=N, Shifts=0 400562 .. Key not programmed -- passed on to FS 400562 *** EVENT: Cntrl= 65616 (0x00010050), Param= 0 (0x00000000) ELEV_UP 401328 KEYDOWN: VK=39, Waiting=0, Repeat=N, Shifts=0 401328 .. Key not programmed -- passed on to FS 401328 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 401562 KEYDOWN: VK=39, Waiting=0, Repeat=N, Shifts=0 401562 .. Key not programmed -- passed on to FS 401562 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 401719 KEYDOWN: VK=39, Waiting=0, Repeat=N, Shifts=0 401719 .. Key not programmed -- passed on to FS 401719 *** EVENT: Cntrl= 65613 (0x0001004d), Param= 0 (0x00000000) AILERONS_RIGHT 402328 KEYDOWN: VK=37, Waiting=0, Repeat=N, Shifts=0 402328 .. Key not programmed -- passed on to FS 402328 *** EVENT: Cntrl= 65611 (0x0001004b), Param= 0 (0x00000000) AILERONS_LEFT 402937 KEYDOWN: VK=38, Waiting=0, Repeat=N, Shifts=0 402937 .. Key not programmed -- passed on to FS 402937 *** EVENT: Cntrl= 65608 (0x00010048), Param= 0 (0x00000000) ELEV_DOWN 403469 KEYDOWN: VK=40, Waiting=0, Repeat=N, Shifts=0 403469 .. Key not programmed -- passed on to FS 403469 *** EVENT: Cntrl= 65616 (0x00010050), Param= 0 (0x00000000) ELEV_UP 406922 *** EVENT: Cntrl= 65732 (0x000100c4), Param= 0 (0x00000000) EXIT 406937 === Closing session: waiting for DLLStop to be called ... 407281 Sim stopped: average frame rate for last 62 secs = 20.9 fps 407281 Max AI traffic was 0 aircraft 410172 === DLLStop called ... 410172 === Closing external processes we started ... 411797 === About to kill any Lua plug-ins still running ... 411953 Lua threads being terminated: 411953 0 = "C:\FS Files\Microsoft Flight Simulator X\Modules\screenshot.lua" 412125 LUA: "C:\FS Files\Microsoft Flight Simulator X\Modules\screenshot.lua": killed 412125 1 = "C:\FS Files\Microsoft Flight Simulator X\Modules\networkrotation.lua" 412297 LUA: "C:\FS Files\Microsoft Flight Simulator X\Modules\networkrotation.lua": killed 412297 === Closing global Lua thread 413312 === About to kill my timers ... 413515 === Restoring window procs ... 413515 === Unloading libraries ... 413515 === stopping other threads ... 413515 === ... Memory checking ... 413515 === ... Button scanning ... 413625 === ... Axis scanning ... 413734 === Releasing joystick devices ... 413734 === Freeing macro memory 413734 === Removing any offset overrides 413734 === Clearing any displays left 413734 === NOTE: not calling SimConnect_Close ... 413734 === AI slots deleted! 413734 === Freeing button memory ... 413734 === Closing my Windows ... 413734 === Freeing FS libraries ... 414750 === Closing devices ... 414750 === Closing the Log ... Bye Bye! ... 414750 System time = 12/09/2018 17:39:28, Simulator time = 11:10:25 (06:10Z) 414750 *** FSUIPC log file being closed Minimum frame rate was 15.8 fps, Maximum was 21.4 fps Minimum available memory recorded was 2705Mb Average frame rate for running time of 217 secs = 19.0 fps G3D fix: Passes 7669, Null pointers 0, Bad pointers 0, Separate instances 0 Maximum AI traffic for session was 0 aircraft Memory managed: 106 Allocs, 106 Freed ********* FSUIPC Log file closed *********** I will shortly test without PostKeys and upload the logs. Regards, Chakko.
  21. Dear Pete, I have FSUIPC4 installed on all my Client PC's, so I enabled Key/Button logging, and here are the logs: ********* WideClient Log [version 7.148] Class=FS98MAIN01 ********* Date (dmy): 12/09/18, Time 05:50:02.515: Client name is INSPIRON3567 125 KeyHook added: 2=39,8,FS98MAIN, 125 KeyHook added: 3=37,8,FS98MAIN, 125 KeyHook added: 4=36,8,FS98MAIN, 125 KeyHook added: 5=38,8,FS98MAIN, 125 KeyHook added: 6=40,8,FS98MAIN, 140 KeyHook added: 259=0,0,, 140 KeyHook added: 260=0,0,, 156 LUA: "C:\FS Files\WideClient7148\Initial.LUA": not found 156 Attempting to connect now 156 Trying TCP/IP host "SERVER" port 8002 ... 156 ... Okay, IP Address = 169.254.152.178 156 Connection made okay! 469 Connection closed by server! 469 Attempting to connect now 469 Connection closed by server! 469 Attempting to connect now 469 Error on client WSAAsyncSelect() [Error=10038] Socket operation on nonsocket 469 Ready to try connection again 469 Error on client WSAAsyncSelect() [Error=10038] Socket operation on nonsocket 1484 Attempting to connect now 1484 Connection made okay! 1531 Connection closed by server! 1531 Attempting to connect now 1531 Connection made okay! 826906 Post/Send input for KeyHook action 3 826906 WM_KEYDOWN posted to Window 00040310 ok, VK code 37 826922 WM_KEYUP posted to Window 00040310 ok, VK code 37 826922 Action request sent 2 events 826922 Checked KeySend[0]=3 828625 Post/Send input for KeyHook action 2 828625 WM_KEYDOWN posted to Window 00040310 ok, VK code 39 828640 WM_KEYUP posted to Window 00040310 ok, VK code 39 828640 Action request sent 2 events 828640 Checked KeySend[1]=2 830000 Post/Send input for KeyHook action 6 830000 WM_KEYDOWN posted to Window 00040310 ok, VK code 40 830015 WM_KEYUP posted to Window 00040310 ok, VK code 40 830015 Action request sent 2 events 830015 Checked KeySend[2]=6 831187 Post/Send input for KeyHook action 5 831187 WM_KEYDOWN posted to Window 00040310 ok, VK code 38 831203 WM_KEYUP posted to Window 00040310 ok, VK code 38 831203 Action request sent 2 events 831203 Checked KeySend[3]=5 832890 Post/Send input for KeyHook action 3 832890 WM_KEYDOWN posted to Window 00040310 ok, VK code 37 832922 WM_KEYUP posted to Window 00040310 ok, VK code 37 832922 Action request sent 2 events 832922 Checked KeySend[4]=3 833797 Post/Send input for KeyHook action 2 833797 WM_KEYDOWN posted to Window 00040310 ok, VK code 39 833812 WM_KEYUP posted to Window 00040310 ok, VK code 39 833812 Action request sent 2 events 833812 Checked KeySend[5]=2 834797 Post/Send input for KeyHook action 5 834797 WM_KEYDOWN posted to Window 00040310 ok, VK code 38 834812 WM_KEYUP posted to Window 00040310 ok, VK code 38 834812 Action request sent 2 events 834812 Checked KeySend[6]=5 835703 Post/Send input for KeyHook action 6 835703 WM_KEYDOWN posted to Window 00040310 ok, VK code 40 835719 WM_KEYUP posted to Window 00040310 ok, VK code 40 835719 Action request sent 2 events 835719 Checked KeySend[7]=6 837125 Post/Send input for KeyHook action 4 837125 WM_KEYDOWN posted to Window 00040310 ok, VK code 36 837140 WM_KEYUP posted to Window 00040310 ok, VK code 36 837140 Action request sent 2 events 837140 Checked KeySend[8]=4 837640 Post/Send input for KeyHook action 3 837640 WM_KEYDOWN posted to Window 00040310 ok, VK code 37 837656 WM_KEYUP posted to Window 00040310 ok, VK code 37 837656 Action request sent 2 events 837656 Checked KeySend[9]=3 838328 Post/Send input for KeyHook action 2 838328 WM_KEYDOWN posted to Window 00040310 ok, VK code 39 838344 WM_KEYUP posted to Window 00040310 ok, VK code 39 838344 Action request sent 2 events 838344 Checked KeySend[10]=2 838953 Post/Send input for KeyHook action 5 838953 WM_KEYDOWN posted to Window 00040310 ok, VK code 38 838969 WM_KEYUP posted to Window 00040310 ok, VK code 38 838969 Action request sent 2 events 838969 Checked KeySend[11]=5 839609 Post/Send input for KeyHook action 6 839609 WM_KEYDOWN posted to Window 00040310 ok, VK code 40 839625 WM_KEYUP posted to Window 00040310 ok, VK code 40 839625 Action request sent 2 events 839625 Checked KeySend[12]=6 840515 Post/Send input for KeyHook action 4 840515 WM_KEYDOWN posted to Window 00040310 ok, VK code 36 840531 WM_KEYUP posted to Window 00040310 ok, VK code 36 840531 Action request sent 2 events 840531 Checked KeySend[13]=4 and: ********* FSUIPC4, Version 4.974b (14th March 2018) by Pete Dowson ********* Windows 10 Home Single Language 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0) fsx.exe version = 10.0.61472.0 Reading options from "C:\FS Files\Microsoft Flight Simulator X\Modules\FSUIPC4.ini" Running inside FSX on Windows 10 Module base=5E8F0000 User Name="Chakko Kovoor" User Addr="ckovoor@alum,mit.edu" FSUIPC4 Key is provided WideFS7 Key is provided 31 System time = 12/09/2018 05:50:00 47 FLT UNC path = "\\INSPIRON3567\Documents\Flight Simulator X Files\" 47 ------ Module Version Check ------ 47 acontain.dll: 10.0.61472.0 47 api.dll: 10.0.61472.0 47 controls.dll: 10.0.61472.0 47 fs-traffic.dll: 10.0.61472.0 47 G3D.dll: 10.0.61472.0 47 language.dll: 10.0.61472.0 47 sim1.dll: 10.0.61472.0 47 visualfx.dll: 10.0.61472.0 47 weather.dll: 10.0.61472.0 47 window.dll: 10.0.61472.0 47 ---------------------------------- 62 Trying to connect to SimConnect Acc/SP2 Oct07 ... 125 FS UNC path = "\\INSPIRON3567\FS Files\Microsoft Flight Simulator X\" 297 ---------------------- Joystick Device Scan ----------------------- 297 ------------------------------------------------------------------- 437 Run: C:\FS Files\PILOTS_FSGRW_NETWORKBRIDGE\FS Global Real Weather Network Bridge.exe 1609 Run: C:\FS Files\WideClient7148\WideClient.exe 2531 LogOptions=00000000 00000001 2531 ------------------------------------------------------------------- 2531 ------ Setting the hooks and direct calls into the simulator ------ 2531 --- CONTROLS timer memory location obtained ok 2531 --- SIM1 Frictions access gained 2531 --- FS Controls Table located ok 2531 --- Installed Mouse Macro hooks ok. 2531 --- Wind smoothing fix is fully installed 2531 --- G3D.DLL fix attempt installed ok 2531 --- SimConnect intercept for texts and menus option is off 2531 --- All links checked okay 2531 ------------------------------------------------------------------- 2531 SimConnect_Open succeeded: waiting to check version okay 2531 Trying to use SimConnect Acc/SP2 Oct07 2531 Opened separate AI Traffic client okay 7250 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 7250 Initialising SimConnect data requests now 7250 FSUIPC Menu entry added 7265 \\INSPIRON3567\Documents\Flight Simulator X Files\WVD A320.FLT 7265 \\INSPIRON3567\FS Files\Microsoft Flight Simulator X\SimObjects\Airplanes\WidevieW_Dummy - FSL A320X\pa320-cfm56-2.AIR 8062 User Aircraft ID 1 supplied, now being used 8062 Aircraft loaded: running normally now ... 21312 System time = 12/09/2018 05:50:21, Simulator time = 11:04:00 (06:04Z) 21328 Aircraft="WidevieW Dummy A320-X" 186703 Starting everything now ... 186781 AES Link established 188078 Advanced Weather Interface Enabled 791250 Sim stopped: average frame rate for last 606 secs = 25.4 fps 791250 Max AI traffic was 0 aircraft 820156 LogOptions changed, now 40000000 00000001 829312 KEYDOWN: VK=37, Waiting=0, Repeat=N, Shifts=0 829312 .. Key not programmed -- passed on to FS 831031 KEYDOWN: VK=39, Waiting=0, Repeat=N, Shifts=0 831031 .. Key not programmed -- passed on to FS 832406 KEYDOWN: VK=40, Waiting=0, Repeat=N, Shifts=0 832406 .. Key not programmed -- passed on to FS 833609 KEYDOWN: VK=38, Waiting=0, Repeat=N, Shifts=0 833609 .. Key not programmed -- passed on to FS 835312 KEYDOWN: VK=37, Waiting=0, Repeat=N, Shifts=0 835312 .. Key not programmed -- passed on to FS 836219 KEYDOWN: VK=39, Waiting=0, Repeat=N, Shifts=0 836219 .. Key not programmed -- passed on to FS 837219 KEYDOWN: VK=38, Waiting=0, Repeat=N, Shifts=0 837219 .. Key not programmed -- passed on to FS 838125 KEYDOWN: VK=40, Waiting=0, Repeat=N, Shifts=0 838125 .. Key not programmed -- passed on to FS 839500 KEYDOWN: VK=36, Waiting=0, Repeat=N, Shifts=0 839515 .. Key not programmed -- passed on to FS 840031 KEYDOWN: VK=37, Waiting=0, Repeat=N, Shifts=0 840031 .. Key not programmed -- passed on to FS 840734 KEYDOWN: VK=39, Waiting=0, Repeat=N, Shifts=0 840734 .. Key not programmed -- passed on to FS 841359 KEYDOWN: VK=38, Waiting=0, Repeat=N, Shifts=0 841359 .. Key not programmed -- passed on to FS 842015 KEYDOWN: VK=40, Waiting=0, Repeat=N, Shifts=0 842015 .. Key not programmed -- passed on to FS 842922 KEYDOWN: VK=36, Waiting=0, Repeat=N, Shifts=0 842922 .. Key not programmed -- passed on to FS As before, only the first 3 or 4 keypresses were actually received/responded to by FSX (I do note that the log shows that the keypresses continue to be passed on to FSX, though.) When FSX stopped responding, I began applying the keypresses directly from the keyboard, and FSX did respond normally to these. And when I thereafter reverted to sending the keypresses via WideClient, I once again got a response for the first 2 or 3 keypresses only. But I was able to renew its responsiveness to the WideClient-origin-keypresses (for a couple of keypresses at a time only) by reverting to using the keyboard directly. I was able to repeat this procedure several times. Thanks and Regards, Chakko.
  22. Dear Pete, Thank you again for your help with this. The panning/tilting-view feature across my networked scenery-Clients is something I would not like to forgo. (1) PostKeys=Yes (within the [User] section, right?) DID WORK, but, only for the first 3 or 4 button presses. Then it stopped working entirely, and only restarting the Sim got it working again (but as before, only for the first few button presses). The WideClient.log from that session (in case you find it useful) is here: ********* WideClient Log [version 7.148] Class=FS98MAIN01 ********* Date (dmy): 11/09/18, Time 18:36:24.542: Client name is INSPIRON3567 156 KeyHook added: 2=39,8,FS98MAIN, 156 KeyHook added: 3=37,8,FS98MAIN, 156 KeyHook added: 4=36,8,FS98MAIN, 156 KeyHook added: 5=38,8,FS98MAIN, 156 KeyHook added: 6=40,8,FS98MAIN, 172 KeyHook added: 259=0,0,, 172 KeyHook added: 260=0,0,, 172 Attempting to connect now 188 LUA: "C:\FS Files\WideClient7148\Initial.LUA": not found 188 Trying TCP/IP host "SERVER" port 8002 ... 188 ... Okay, IP Address = 169.254.152.178 203 Connection made okay! 51469 Post/Send input for KeyHook action 3 51469 WM_KEYDOWN posted to Window 000302e2 ok, VK code 37 51484 WM_KEYUP posted to Window 000302e2 ok, VK code 37 51484 Action request sent 2 events 51484 Checked KeySend[0]=3 52344 Post/Send input for KeyHook action 4 52344 WM_KEYDOWN posted to Window 000302e2 ok, VK code 36 52359 WM_KEYUP posted to Window 000302e2 ok, VK code 36 52359 Action request sent 2 events 52359 Checked KeySend[1]=4 215844 Post/Send input for KeyHook action 3 215844 WM_KEYDOWN posted to Window 000302e2 ok, VK code 37 215859 WM_KEYUP posted to Window 000302e2 ok, VK code 37 215859 Action request sent 2 events 215859 Checked KeySend[2]=3 216844 Post/Send input for KeyHook action 3 216844 WM_KEYDOWN posted to Window 000302e2 ok, VK code 37 216859 WM_KEYUP posted to Window 000302e2 ok, VK code 37 216859 Action request sent 2 events 216859 Checked KeySend[3]=3 217594 Post/Send input for KeyHook action 2 217594 WM_KEYDOWN posted to Window 000302e2 ok, VK code 39 217609 WM_KEYUP posted to Window 000302e2 ok, VK code 39 217609 Action request sent 2 events 217609 Checked KeySend[4]=2 218109 Post/Send input for KeyHook action 2 218109 WM_KEYDOWN posted to Window 000302e2 ok, VK code 39 218125 WM_KEYUP posted to Window 000302e2 ok, VK code 39 218125 Action request sent 2 events 218125 Checked KeySend[5]=2 219188 Post/Send input for KeyHook action 2 219188 WM_KEYDOWN posted to Window 000302e2 ok, VK code 39 219203 WM_KEYUP posted to Window 000302e2 ok, VK code 39 219203 Action request sent 2 events 219203 Checked KeySend[6]=2 221141 Post/Send input for KeyHook action 4 221141 WM_KEYDOWN posted to Window 000302e2 ok, VK code 36 221156 WM_KEYUP posted to Window 000302e2 ok, VK code 36 221156 Action request sent 2 events 221156 Checked KeySend[7]=4 221859 Post/Send input for KeyHook action 3 221859 WM_KEYDOWN posted to Window 000302e2 ok, VK code 37 221891 WM_KEYUP posted to Window 000302e2 ok, VK code 37 221891 Action request sent 2 events 221891 Checked KeySend[8]=3 222516 Post/Send input for KeyHook action 3 222516 WM_KEYDOWN posted to Window 000302e2 ok, VK code 37 222531 WM_KEYUP posted to Window 000302e2 ok, VK code 37 222531 Action request sent 2 events 222531 Checked KeySend[9]=3 223578 Post/Send input for KeyHook action 2 223578 WM_KEYDOWN posted to Window 000302e2 ok, VK code 39 223594 WM_KEYUP posted to Window 000302e2 ok, VK code 39 223594 Action request sent 2 events 223594 Checked KeySend[10]=2 224172 Post/Send input for KeyHook action 2 224172 WM_KEYDOWN posted to Window 000302e2 ok, VK code 39 224188 WM_KEYUP posted to Window 000302e2 ok, VK code 39 224188 Action request sent 2 events 224188 Checked KeySend[11]=2 224797 Post/Send input for KeyHook action 4 224797 WM_KEYDOWN posted to Window 000302e2 ok, VK code 36 224813 WM_KEYUP posted to Window 000302e2 ok, VK code 36 224813 Action request sent 2 events 224813 Checked KeySend[12]=4 225547 Post/Send input for KeyHook action 3 225547 WM_KEYDOWN posted to Window 000302e2 ok, VK code 37 225563 WM_KEYUP posted to Window 000302e2 ok, VK code 37 225563 Action request sent 2 events 225563 Checked KeySend[13]=3 226047 Post/Send input for KeyHook action 3 226047 WM_KEYDOWN posted to Window 000302e2 ok, VK code 37 226063 WM_KEYUP posted to Window 000302e2 ok, VK code 37 226063 Action request sent 2 events 226063 Checked KeySend[14]=3 226984 Post/Send input for KeyHook action 2 226984 WM_KEYDOWN posted to Window 000302e2 ok, VK code 39 227000 WM_KEYUP posted to Window 000302e2 ok, VK code 39 227000 Action request sent 2 events 227000 Checked KeySend[15]=2 227422 Post/Send input for KeyHook action 2 227422 WM_KEYDOWN posted to Window 000302e2 ok, VK code 39 227438 WM_KEYUP posted to Window 000302e2 ok, VK code 39 227438 Action request sent 2 events 227438 Checked KeySend[0]=2 228188 Post/Send input for KeyHook action 4 228188 WM_KEYDOWN posted to Window 000302e2 ok, VK code 36 228203 WM_KEYUP posted to Window 000302e2 ok, VK code 36 228203 Action request sent 2 events 228203 Checked KeySend[1]=4 230031 Post/Send input for KeyHook action 5 230031 WM_KEYDOWN posted to Window 000302e2 ok, VK code 38 230047 WM_KEYUP posted to Window 000302e2 ok, VK code 38 230047 Action request sent 2 events 230047 Checked KeySend[2]=5 230938 Post/Send input for KeyHook action 6 230938 WM_KEYDOWN posted to Window 000302e2 ok, VK code 40 230953 WM_KEYUP posted to Window 000302e2 ok, VK code 40 230953 Action request sent 2 events 230953 Checked KeySend[3]=6 231438 Post/Send input for KeyHook action 6 231438 WM_KEYDOWN posted to Window 000302e2 ok, VK code 40 231453 WM_KEYUP posted to Window 000302e2 ok, VK code 40 231453 Action request sent 2 events 231453 Checked KeySend[4]=6 233438 Post/Send input for KeyHook action 5 233438 WM_KEYDOWN posted to Window 000302e2 ok, VK code 38 233453 WM_KEYUP posted to Window 000302e2 ok, VK code 38 233453 Action request sent 2 events 233453 Checked KeySend[5]=5 234844 Post/Send input for KeyHook action 4 234844 WM_KEYDOWN posted to Window 000302e2 ok, VK code 36 234859 WM_KEYUP posted to Window 000302e2 ok, VK code 36 234859 Action request sent 2 events 234859 Checked KeySend[6]=4 237547 Post/Send input for KeyHook action 6 237547 WM_KEYDOWN posted to Window 000302e2 ok, VK code 40 237563 WM_KEYUP posted to Window 000302e2 ok, VK code 40 237563 Action request sent 2 events 237563 Checked KeySend[7]=6 238391 Post/Send input for KeyHook action 5 238391 WM_KEYDOWN posted to Window 000302e2 ok, VK code 38 238406 WM_KEYUP posted to Window 000302e2 ok, VK code 38 238406 Action request sent 2 events 238406 Checked KeySend[8]=5 239141 Post/Send input for KeyHook action 3 239141 WM_KEYDOWN posted to Window 000302e2 ok, VK code 37 239156 WM_KEYUP posted to Window 000302e2 ok, VK code 37 239156 Action request sent 2 events 239156 Checked KeySend[9]=3 239328 Post/Send input for KeyHook action 3 239328 WM_KEYDOWN posted to Window 000302e2 ok, VK code 37 239344 WM_KEYUP posted to Window 000302e2 ok, VK code 37 239344 Action request sent 2 events 239344 Checked KeySend[10]=3 239984 Post/Send input for KeyHook action 4 239984 WM_KEYDOWN posted to Window 000302e2 ok, VK code 36 240000 WM_KEYUP posted to Window 000302e2 ok, VK code 36 240000 Action request sent 2 events 240000 Checked KeySend[11]=4 240672 Post/Send input for KeyHook action 3 240672 WM_KEYDOWN posted to Window 000302e2 ok, VK code 37 240688 WM_KEYUP posted to Window 000302e2 ok, VK code 37 240688 Action request sent 2 events 240688 Checked KeySend[12]=3 241672 Post/Send input for KeyHook action 4 241672 WM_KEYDOWN posted to Window 000302e2 ok, VK code 36 241688 WM_KEYUP posted to Window 000302e2 ok, VK code 36 241688 Action request sent 2 events 241688 Checked KeySend[13]=4 243578 Post/Send input for KeyHook action 6 243578 WM_KEYDOWN posted to Window 000302e2 ok, VK code 40 243594 WM_KEYUP posted to Window 000302e2 ok, VK code 40 243594 Action request sent 2 events 243594 Checked KeySend[14]=6 244297 Post/Send input for KeyHook action 4 244297 WM_KEYDOWN posted to Window 000302e2 ok, VK code 36 244313 WM_KEYUP posted to Window 000302e2 ok, VK code 36 244313 Action request sent 2 events 244313 Checked KeySend[15]=4 245047 Post/Send input for KeyHook action 5 245047 WM_KEYDOWN posted to Window 000302e2 ok, VK code 38 245063 WM_KEYUP posted to Window 000302e2 ok, VK code 38 245063 Action request sent 2 events 245063 Checked KeySend[0]=5 246438 Post/Send input for KeyHook action 6 246438 WM_KEYDOWN posted to Window 000302e2 ok, VK code 40 246453 WM_KEYUP posted to Window 000302e2 ok, VK code 40 246453 Action request sent 2 events 246453 Checked KeySend[1]=6 247078 Post/Send input for KeyHook action 4 247078 WM_KEYDOWN posted to Window 000302e2 ok, VK code 36 247094 WM_KEYUP posted to Window 000302e2 ok, VK code 36 247094 Action request sent 2 events 247094 Checked KeySend[2]=4 247656 Post/Send input for KeyHook action 2 247656 WM_KEYDOWN posted to Window 000302e2 ok, VK code 39 247672 WM_KEYUP posted to Window 000302e2 ok, VK code 39 247672 Action request sent 2 events 247672 Checked KeySend[3]=2 248500 Post/Send input for KeyHook action 4 248500 WM_KEYDOWN posted to Window 000302e2 ok, VK code 36 248516 WM_KEYUP posted to Window 000302e2 ok, VK code 36 248516 Action request sent 2 events 248516 Checked KeySend[4]=4 249031 Post/Send input for KeyHook action 3 249031 WM_KEYDOWN posted to Window 000302e2 ok, VK code 37 249047 WM_KEYUP posted to Window 000302e2 ok, VK code 37 249047 Action request sent 2 events 249047 Checked KeySend[5]=3 249563 Post/Send input for KeyHook action 3 249563 WM_KEYDOWN posted to Window 000302e2 ok, VK code 37 249578 WM_KEYUP posted to Window 000302e2 ok, VK code 37 249578 Action request sent 2 events 249578 Checked KeySend[6]=3 250000 Post/Send input for KeyHook action 4 250000 WM_KEYDOWN posted to Window 000302e2 ok, VK code 36 250016 WM_KEYUP posted to Window 000302e2 ok, VK code 36 250016 Action request sent 2 events 250016 Checked KeySend[7]=4 257422 ****** End of session performance summary ****** 257422 Total time connected = 257 seconds 257422 Reception maximum: 32 frames/sec, 935 bytes/sec 257422 Reception average whilst connected: 31 frames/sec, 749 bytes/sec 257422 Transmission maximum: 0 frames/sec, 185 bytes/sec 257422 Transmission average whilst connected: 0 frames/sec, 20 bytes/sec 257422 Max receive buffer = 473, Max send depth = 1, Send frames lost = 0 257422 ********* Log file closed (Buffers: MaxUsed 2, Alloc 8242 Freed 8242 Refused 0) ********* (2) UseSendInput=Yes (within the [User] section) DID NOT WORK at all. The WideClient.log from that session (in case you find it useful) is here: ********* WideClient Log [version 7.148] Class=FS98MAIN01 ********* Date (dmy): 11/09/18, Time 18:42:43.047: Client name is INSPIRON3567 125 KeyHook added: 2=39,8,FS98MAIN, 125 KeyHook added: 3=37,8,FS98MAIN, 125 KeyHook added: 4=36,8,FS98MAIN, 125 KeyHook added: 5=38,8,FS98MAIN, 125 KeyHook added: 6=40,8,FS98MAIN, 157 KeyHook added: 259=0,0,, 157 KeyHook added: 260=0,0,, 157 Attempting to connect now 157 LUA: "C:\FS Files\WideClient7148\Initial.LUA": not found 172 Trying TCP/IP host "SERVER" port 8002 ... 172 ... Okay, IP Address = 169.254.152.178 172 Connection made okay! 10188 Setting hook for KeyHook action 4 10188 Can't SetWindowsHookEx! (Action request 4) 10188 Checked KeySend[8]=4 10766 Setting hook for KeyHook action 3 10766 Can't SetWindowsHookEx! (Action request 3) 10766 Checked KeySend[9]=3 11313 Setting hook for KeyHook action 3 11313 Can't SetWindowsHookEx! (Action request 3) 11313 Checked KeySend[10]=3 11750 Setting hook for KeyHook action 3 11750 Can't SetWindowsHookEx! (Action request 3) 11750 Checked KeySend[11]=3 12250 Setting hook for KeyHook action 2 12250 Can't SetWindowsHookEx! (Action request 2) 12250 Checked KeySend[12]=2 12563 Setting hook for KeyHook action 2 12563 Can't SetWindowsHookEx! (Action request 2) 12563 Checked KeySend[13]=2 12953 Setting hook for KeyHook action 2 12953 Can't SetWindowsHookEx! (Action request 2) 12953 Checked KeySend[14]=2 13250 Setting hook for KeyHook action 2 13250 Can't SetWindowsHookEx! (Action request 2) 13250 Checked KeySend[15]=2 13719 Setting hook for KeyHook action 4 13719 Can't SetWindowsHookEx! (Action request 4) 13719 Checked KeySend[0]=4 14344 Setting hook for KeyHook action 4 14344 Can't SetWindowsHookEx! (Action request 4) 14344 Checked KeySend[1]=4 15094 Setting hook for KeyHook action 2 15094 Can't SetWindowsHookEx! (Action request 2) 15094 Checked KeySend[2]=2 29985 Setting hook for KeyHook action 2 29985 Can't SetWindowsHookEx! (Action request 2) 29985 Checked KeySend[3]=2 30844 Setting hook for KeyHook action 4 30844 Can't SetWindowsHookEx! (Action request 4) 30844 Checked KeySend[4]=4 31297 Setting hook for KeyHook action 4 31297 Can't SetWindowsHookEx! (Action request 4) 31297 Checked KeySend[5]=4 31688 Setting hook for KeyHook action 4 31688 Can't SetWindowsHookEx! (Action request 4) 31688 Checked KeySend[6]=4 32125 Setting hook for KeyHook action 3 32125 Can't SetWindowsHookEx! (Action request 3) 32125 Checked KeySend[7]=3 32532 Setting hook for KeyHook action 3 32532 Can't SetWindowsHookEx! (Action request 3) 32532 Checked KeySend[8]=3 33032 Setting hook for KeyHook action 4 33032 Can't SetWindowsHookEx! (Action request 4) 33032 Checked KeySend[9]=4 33500 Setting hook for KeyHook action 4 33500 Can't SetWindowsHookEx! (Action request 4) 33500 Checked KeySend[10]=4 34094 Setting hook for KeyHook action 2 34094 Can't SetWindowsHookEx! (Action request 2) 34094 Checked KeySend[11]=2 34438 Setting hook for KeyHook action 2 34438 Can't SetWindowsHookEx! (Action request 2) 34438 Checked KeySend[12]=2 34907 Setting hook for KeyHook action 4 34907 Can't SetWindowsHookEx! (Action request 4) 34907 Checked KeySend[13]=4 36032 Setting hook for KeyHook action 6 36032 Can't SetWindowsHookEx! (Action request 6) 36032 Checked KeySend[14]=6 36360 Setting hook for KeyHook action 6 36360 Can't SetWindowsHookEx! (Action request 6) 36360 Checked KeySend[15]=6 36860 Setting hook for KeyHook action 4 36860 Can't SetWindowsHookEx! (Action request 4) 36860 Checked KeySend[0]=4 42235 ****** End of session performance summary ****** 42235 Total time connected = 42 seconds 42235 Reception maximum: 32 frames/sec, 938 bytes/sec 42235 Reception average whilst connected: 31 frames/sec, 770 bytes/sec 42235 Transmission maximum: 0 frames/sec, 185 bytes/sec 42235 Transmission average whilst connected: 0 frames/sec, 28 bytes/sec 42235 Max receive buffer = 473, Max send depth = 1, Send frames lost = 0 42235 ********* Log file closed (Buffers: MaxUsed 2, Alloc 1357 Freed 1357 Refused 0) ********* Thank you so much, as always, for the superlative support you provide. Regards, Chakko.
  23. Dear Pete, Thank you for having a look at this. (1) I ran WideClient as administrator, and (2) I included Log=KeySend in the [User] Section but the problem persists: ********* WideClient Log [version 7.148] Class=FS98MAIN01 ********* Date (dmy): 11/09/18, Time 16:39:17.475: Client name is INSPIRON3567 141 KeyHook added: 2=39,8,FS98MAIN, 141 KeyHook added: 3=37,8,FS98MAIN, 141 KeyHook added: 4=36,8,FS98MAIN, 141 KeyHook added: 5=38,8,FS98MAIN, 141 KeyHook added: 6=40,8,FS98MAIN, 156 KeyHook added: 259=0,0,FS98MAIN01, 156 KeyHook added: 260=0,0,FS98MAIN01, 172 LUA: "C:\FS Files\WideClient7148\Initial.LUA": not found 172 Attempting to connect now 172 Trying TCP/IP host "SERVER" port 8002 ... 172 ... Okay, IP Address = 169.254.152.178 172 Connection made okay! 31031 Setting hook for KeyHook action 4 31031 Can't SetWindowsHookEx! (Action request 4) 31031 Checked KeySend[0]=4 31906 Setting hook for KeyHook action 3 31906 Can't SetWindowsHookEx! (Action request 3) 31906 Checked KeySend[1]=3 32563 Setting hook for KeyHook action 3 32563 Can't SetWindowsHookEx! (Action request 3) 32563 Checked KeySend[2]=3 33203 Setting hook for KeyHook action 4 33203 Can't SetWindowsHookEx! (Action request 4) 33203 Checked KeySend[3]=4 212625 Setting hook for KeyHook action 4 212625 Can't SetWindowsHookEx! (Action request 4) 212625 Checked KeySend[4]=4 213438 Setting hook for KeyHook action 3 213438 Can't SetWindowsHookEx! (Action request 3) 213438 Checked KeySend[5]=3 214094 Setting hook for KeyHook action 3 214094 Can't SetWindowsHookEx! (Action request 3) 214094 Checked KeySend[6]=3 214688 Setting hook for KeyHook action 2 214688 Can't SetWindowsHookEx! (Action request 2) 214688 Checked KeySend[7]=2 215094 Setting hook for KeyHook action 2 215094 Can't SetWindowsHookEx! (Action request 2) 215094 Checked KeySend[8]=2 216219 Setting hook for KeyHook action 5 216219 Can't SetWindowsHookEx! (Action request 5) 216219 Checked KeySend[9]=5 216610 Setting hook for KeyHook action 5 216610 Can't SetWindowsHookEx! (Action request 5) 216610 Checked KeySend[10]=5 216985 Setting hook for KeyHook action 5 216985 Can't SetWindowsHookEx! (Action request 5) 216985 Checked KeySend[11]=5 217485 Setting hook for KeyHook action 5 217485 Can't SetWindowsHookEx! (Action request 5) 217485 Checked KeySend[12]=5 217922 Setting hook for KeyHook action 6 217922 Can't SetWindowsHookEx! (Action request 6) 217922 Checked KeySend[13]=6 218266 Setting hook for KeyHook action 6 218266 Can't SetWindowsHookEx! (Action request 6) 218266 Checked KeySend[14]=6 218578 Setting hook for KeyHook action 6 218578 Can't SetWindowsHookEx! (Action request 6) 218578 Checked KeySend[15]=6 219078 Setting hook for KeyHook action 6 219078 Can't SetWindowsHookEx! (Action request 6) 219078 Checked KeySend[0]=6 219953 Setting hook for KeyHook action 2 219953 Can't SetWindowsHookEx! (Action request 2) 219953 Checked KeySend[1]=2 220235 Setting hook for KeyHook action 2 220235 Can't SetWindowsHookEx! (Action request 2) 220235 Checked KeySend[2]=2 220703 Setting hook for KeyHook action 4 220703 Can't SetWindowsHookEx! (Action request 4) 220703 Checked KeySend[3]=4 225625 Setting hook for KeyHook action 6 225625 Can't SetWindowsHookEx! (Action request 6) 225625 Checked KeySend[4]=6 225860 Setting hook for KeyHook action 6 225860 Can't SetWindowsHookEx! (Action request 6) 225860 Checked KeySend[5]=6 226125 Setting hook for KeyHook action 6 226125 Can't SetWindowsHookEx! (Action request 6) 226125 Checked KeySend[6]=6 226563 Setting hook for KeyHook action 5 226563 Can't SetWindowsHookEx! (Action request 5) 226563 Checked KeySend[7]=5 226844 Setting hook for KeyHook action 5 226844 Can't SetWindowsHookEx! (Action request 5) 226844 Checked KeySend[8]=5 227438 Setting hook for KeyHook action 2 227438 Can't SetWindowsHookEx! (Action request 2) 227438 Checked KeySend[9]=2 227656 Setting hook for KeyHook action 2 227656 Can't SetWindowsHookEx! (Action request 2) 227656 Checked KeySend[10]=2 I had a look at my WIndows Defender settings: Firewalls are all off, and no Antivirus is active. And, yes, the WideClient.ini I attached to my earlier post was the complete file. Thanks and Regards, Chakko.
  24. Dear Pete, I refer you to the thread at: https://forum.simflight.com/topic/81979-wideview-fsx-network-panning-using-fsuipc4-and-widefs/ in which I have discussed using FSUIPC+WideFS/WIdeClient to transmit panning/tilting view-commands from a hat-switch on my WidevieW Server to my WidevieW Clients running FSX on Windows 7 and also Windows 8.1: Summary of Process: When a panning-command (via a Hat-Switch button) is applied at the SERVER, FSUIPC-WideServer sends a KeySend number to all networked Clients. At each CLIENT, WideClient-FSUIPC receives the KeySend number and acts on it to pan the view locally. Certain options in the wideviewx.ini file at the CLIENTs and SERVER need to be set to ensure that it does not interfere. A new Camera Definition is also installed on the CLIENT(s) to keep this option separate. The method has worked flawlessly with Clients running FSX on Windows 7 and even Windows 8.1. However, yesterday I installed a new Client running FSX on Windows 10, and found that the keystrokes were not being transmitted by WideClient to the local FSX window. More details with the corresponding WideClient.ini and .log files are appended to the same thread: https://forum.simflight.com/topic/81979-wideview-fsx-network-panning-using-fsuipc4-and-widefs/ where I thought it might be more convenient to continue the investigation. Thanks and Regards, Chakko.
  25. Dear Pete, I currently use FSUIPC 4.974b and WideFS/WideClient 7.148, and the setup and method described in this thread has worked flawlessly on my System, with Clients running FSX on both Win7 x64 and Win 8.1 x64. However, yesterday I added a new Client running FSX on Win 10 x64. This time I found the keystrokes were not being transmitted to the local FSX window, and the WideClient.log showed this: ********* WideClient Log [version 7.148] Class=FS98MAIN01 ********* Date (dmy): 10/09/18, Time 19:44:26.551: Client name is INSPIRON3567 172 Attempting to connect now 172 LUA: "C:\FS Files\WideClient7148\Initial.LUA": not found 172 Trying TCP/IP host "SERVER" port 8002 ... 172 ... Okay, IP Address = 169.254.152.178 172 Connection made okay! 276172 Can't SetWindowsHookEx! (Action request 3) 278312 Can't SetWindowsHookEx! (Action request 4) 391906 Can't SetWindowsHookEx! (Action request 3) 394984 Can't SetWindowsHookEx! (Action request 4) 397766 Can't SetWindowsHookEx! (Action request 2) 399297 Can't SetWindowsHookEx! (Action request 4) 1373719 Can't SetWindowsHookEx! (Action request 5) 1375594 Can't SetWindowsHookEx! (Action request 4) The corresponding WideClient.ini : [Config] ServerName=SERVER Protocol=TCP ButtonScanInterval=20 ClassInstance=1 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port=8002 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 Window=515,349,405,365 ReconnectMinutes=0 [Sounds] Path=C:\Program Files\WideClient6999b\Sound\ Device1=Primary Sound Driver Device2=Speakers and Dual Headphones (IDT High Definition Audio CODEC) Device3=SPDIF (Digital Out via HP Dock) (IDT High Definition Audio CODEC) [User] RunKey1="C:\Program Files\IrfanView\i_view64.exe /capture=0 /sharpen=20 /jpgq=100 /convert=\\SERVER\Flight Simulator X Files\ScreenShots\S4_$U(%d%b%y_%H%M%S).jpg" ;RunKey1="C:\Program Files\IrfanView\i_view64.exe /capture=0 /sharpen=20 /jpgq=100 /convert=C:\Users\Chakko Kovoor\Documents\Flight Simulator X Files\ScreenShots\S4_$U(%d%b%y_%H%M%S).jpg" KeySend1=RunKey1 KeySend2=39,8,FS98MAIN KeySend3=37,8,FS98MAIN KeySend4=36,8,FS98MAIN KeySend5=38,8,FS98MAIN KeySend6=40,8,FS98MAIN And here, for reference, is a WideClient.log from a Client running FSX-Win 7 x64 which successfully intercepted and responded to the keystrokes: ********* WideClient Log [version 7.148] Class=FS98MAIN01 ********* Date (dmy): 10/09/18, Time 19:43:50.431: Client name is SILVERZERO 140 LUA: "C:\FS Files\WideClient7148\Initial.LUA": not found 140 Attempting to connect now 140 Trying TCP/IP host "SERVER" port 8002 ... 140 ... Okay, IP Address = 169.254.152.178 140 Connection made okay! It seems that on a Client running Windows 10, WideClient cannot transmit the required keystroke to the local FSX window. I wonder if you could help me solve this problem. Thanks and Regards, Chakko.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.