Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. Nothing is "sent" to an FSUIPC application, it is the application reading data from a memory location in FSUIPC (copied to WideClient in this case). The data should be identical. If you can find out what that error means, it would certainly help. I also still need to know exactly what your ATC panel is sending, and to what program. Is it writing to offsets or sending keystrokes or controls? Pete
  2. Sorry, I've no idea what RCV4 is saying with that error. But then I've no idea what you've programmed in your "send RCV4 keys". Perhaps you should elaborate. Anyway, test in the first place by actually pressing the correct keys on the Server's keyboard. Then you'll know. The method of answering the menu on the FS PC has always worked for all of the RC users I've known. I think for further help you might need to ask other user's advice -- I'm sure there's still an AVSIM forum for RC. Pete
  3. I'm not sure which of your three alternative values for Logs Windows provides the program. you can only use one instance of each keyword. Are you saying SIOC cannot send keypresses? Can the keyboard itself not send keypresses? Pete
  4. You'd need Log=Keys set, as I said. But as I said, I can't get Notepad to receive anything. Weren't you going to try it with RCV4 instead? Anyway, quite honestly I don't know why you just don't make use of RCV4's built-in menu facilities and its choice reading from FSUIPC. As I used to do (changed to Pilot2ATC a few years ago). How does RCV4 present you with the choices and get the responses? It was always through FSUIPC, not direct, when I used it! Pete
  5. Yes, me too at the time I used RCV4. Now I cut it down from 3 HD projectors to 2 UHD projectors, but the same 210 degree curved scren. All the messages which would otherwise be shown on that screen are trapped by the FSUIPC facility to divert them, and sent to a client for display there -- using event.textmenu (see the AllTexts.lua plug-in). So the RCV4 menu was displayed on a small screen in my cockpit instead of on the curved FS view. Any button. switch, or key can be programmed in FSUIPC to send the keypress to FSUIPC corresponding to the desired answer to RCV4's menus. I was never actually aware that RCV4 accepted menu choices directly on its local keyboard! Pete
  6. I used RCV4 for many years, and on a Client PC, but always controlled it via the menus it displays through FSUIPC on the FS screen. RCV4 sets the possible selections using a HotKeys facility in FSUIPC. I never had to send any keypresses direct to RCV4, so why is your setup different? Surely you want the buttons on your special panel to send keystrokes to FS/FSUIPC in answer to the menus displayed? RCV4 detects them from FSUIPC. Pete
  7. I've been trying to find out what the hook function does not work on Windows 10, with no success I'm afraid. I tested with PostKeys=Yes instead, and that works as far as WideClient is concerned. Here's a log with Log=Keys set in the INI: 1797 c:\windows\system32 1797 c:\Windows\System32\Notepad.exe 1828 Attempting to connect now 1828 Trying TCP/IP addr 127.0.0.1, port 8002 ... 1844 Connection made okay! 1844 LUA: "E:\WideClient\WideClientLocal\Initial.LUA": not found 13813 Post/Send input for KeyHook action 2 13813 WM_KEYDOWN posted to Window 000c1088 ok, VK code 67 13891 WM_KEYUP posted to Window 000c1088 ok, VK code 67 13953 Action request sent 2 events 27032 Post/Send input for KeyHook action 3 27032 WM_KEYDOWN posted to Window 000c1088 ok, VK code 52 27094 WM_KEYUP posted to Window 000c1088 ok, VK code 52 27157 Action request sent 2 events 213125 Post/Send input for KeyHook action 3 213125 WM_KEYDOWN posted to Window 000c1088 ok, VK code 52 213203 WM_KEYUP posted to Window 000c1088 ok, VK code 52 213266 Action request sent 2 events 215485 Post/Send input for KeyHook action 3 215485 WM_KEYDOWN posted to Window 000c1088 ok, VK code 52 215563 WM_KEYUP posted to Window 000c1088 ok, VK code 52 215625 Action request sent 2 events 218500 Post/Send input for KeyHook action 4 218500 WM_KEYDOWN posted to Window 000c1088 ok, VK code 53 218563 WM_KEYUP posted to Window 000c1088 ok, VK code 53 218625 Action request sent 2 events However, monitoring the NotePad window (which top level was definitely 000c1088) using SpyXX there was no sign of those Keyboard messages going to Notepad. Now I don't know if this is because of some Win10 protection, or just a peculiarity of NotePad. Are you actually wanting to enter text in Notepad via a WideFS link? Or was this just testing for another use. If so, could you try the PostKeys method with that? I'll continue to research this, but I'm running out of relevant sources of wisdom! 😞 BTW, of the three methods available, both the default (via the Hook) and 'UseSendInput' methods do need the target window to have focus -- unless it has been programmed to declare the keys you are sending as 'hot keys', in which it should get them no matter what the source. But the PostKeys method directs the keypress messages to the program identified in the KeySend parameter (the results of 'Run1' in your case), so shouldn't need it to have focus. So, I'm puzzled as to why this isn't working with NotePad. It may well be okay with other programs. Pete
  8. What if Notepad has the keyboard focus? I'm afraid I don't know any other way to get keys into a program which needs the focus. Some programs using "hot keys" use a facility provided by Windows to be notified of a keystroke even without focus. I'll do some tests here tomorrow. I do use SendKeys quite a lot, and successfully, on an 8-way Network, but all the clients are Win7 based, only the Server is Win10. Pete
  9. Why try that? It’s for sending your key presses on the client to the server! Postkeys=Yes is what I suggested, and was also the solution for Chakko if you get to the end of that thread. Pete
  10. Error 5 is "Access Denied". Possible reasons are different privilege levels (i.e. one being "run as administrator" but the other not), or, more likely, you are running a 64-bit version of Notepad which can't be hooked by a 32-bit program. Try using a different method, like setting "PostKeys=Yes" or "UseSendInput=Yes" (see about page 17 in the WideFS Technical guide). Pete
  11. By default the separate throttle facility assumes a Reverse zone. If you don't want this be sure you check the NRZ (no reverse zone) option in the calibration tab before calibrating. FSUIPC5 and 6 are identical in this area. You should have used your FSUIPC5.INI (renamed to FSUIPC6.INI). Pete
  12. Profiles in a separate Profiles folder still need the entries in the INI which links to them for specific aircraft. Just copying over the folder isn't enough, you needed the entries in the main INI file, so you should have retained your previous INI. Pete
  13. Very unlikely. I don't think any USB webcam operates as a serial device needing a COM port allocation. Didn't you ask OpenTrack. It seems really something they need to deal with. Pete
  14. Sorry, this is not anything FSUIPC can do at present. The Lua library functions for programs loaded by Lua (ext.run function) include focus facilities, but not for individual windows within a process, and certainly not for P3D itself. You could perhaps do it with a Lua plug-in which uses the mouse library -- mouse.move to more the cursor to a suitable position, then mouse.click to set the focus there. I can't think of any other way. Pete
  15. That's what the added FSUIPC control "Traffic Density Toggle" is for. Assign your key to that. Pete
  16. I'm pretty sure they work ok -- but only when an NDB signal is being received by one of your ADF receivers of course. Please use the Monitor option in FSUIPC Logging tab to see what is actually provided. I suspect that to get zero you are doing the division before the multiplication. Check your calculations please. Pete
  17. No, running as admin is not a solution. Have you checked the relevant sections in the WideFS Technical manual? In particular this one: PTT (push to talk) for Roger Wilco, AVC and TeamSpeak If the specific solution for TeamSpeak shown there doesn't work for you, then these may also help you find the solution: Directing Key Strokes more precisely and Special KeySend facilities to bring a program's Window to the foreground and CLASS Names Pete
  18. I think you have not reinstalled it correctly, then. Try reloading from Steam so all the correct files go into the same place. Before then, though, try removing the SimConnect.DLL from the FSX folder so FSUIPC looks in the WinSxS folder instead, and also try each of the versions I sent, as I suggested. You have not shown me the correct part. And I don't want pictures. The error data is in Windows Logs - Application, as I said. Reduce the size of the 'Actions' window so you can see the whole Applications window. You can then copy and paste the text it displays in the "General" tab. Here's an example (not from FSX): Faulting application name: NVIDIA Share.exe, version: 73.3683.1933.5, time stamp: 0x5f8ee96e Faulting module name: KERNELBASE.dll, version: 10.0.19041.572, time stamp: 0x1183946c Exception code: 0xe0000008 Fault offset: 0x0000000000023e49 Faulting process id: 0x2274 Faulting application start time: 0x01d6c9a4d95edb92 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: e91acd8a-f1ea-42f5-9152-a292bed76b7f Faulting package full name: Faulting package-relative application ID: That is not needed. The Installer looks after replacing it. And by deleting the INI you were using you've lost all your settings. This is why I think the FSX-SE setup you have is not installed properly. I suggest that the only way to properly reinstall FSX-SE is to let Steam do it for you. Pete
  19. This is crashing in a very strange place -- when it is trying to open the SimConnect link. I've not seen such a problem before. I'm wondering if the SimConnect.DLL in the WinSXS folders is corrupted. That may not have been restored when you reinstalled FSX. Could you see if there's a SimConnect.dll in the same folder as the FSX.EXE (main program)? If not see if you can find the version 62607 SimConnect.DLL in the WinSXS folders. If you can, copy it to the main FSX folder. Otherwise, I attach two later versions: 62608 and 62615 for you to try, I'm afraid I don't have 62605 (which release of FSX-SE was that from? When you reinstalled, was it from the latest in Steam?). IMPORTANT: Please could you use the Windows Event Viewer to find the crash details for FSX.EXE which you will find in Windows Logs - Application. Post the test from one of them here please. The FSUIPC4.INI file in your Zip cannot be from the system featured in the Log as it is from a very old version: UpdatedByVersion=4530 It is also very incomplete. So where are you getting that from? Not the Modules folder I think. The FSUIPC4(new install).INI is a zero length file! And the FSUIPC4(unsure).INI is also from 4.53 and even more foreshortended than the other. So, why is there no real FSUIPC4.INI? I think you need to delete all those before starting it again. You said: So why is there no INI file from any use over those 3 months, but two (incomplete) from 4.53? Pete SimConnect 62608.zip SimConnect 62615.zip
  20. Try calibrating in Windows first. If you are using any other Joystick program (Honeycomb drivers?) best to uninstall that. Pete
  21. This is normally because a previous FSX session crashed, and because FSUIPC has threads which close later (to tidy up), it gets the 'blame'. Ah, so something else is wrong. In order to check what I need to see the FSUIPC4.LOG and FSUIPC4.INI files, from the FSX Modules folder. Either copy and paste them into your reply, or ZIP them and attach them. Pete
  22. The registration code, name and email need to be the same as for FSUIPC6. If the name or email is different from your FSUIPC7 registration you need to check that option and enter them properly. Pete
  23. No. The most likely reason is that you are running MSFS and FSUIPC "as administrator", but not your FSUIPC application (or vice versa). Any FSUIPC client needs to be on the same privilege level as FSUIPC or they cannot communicate. This has always been the case, it is no different with MSFS. Pete
  24. Okay. Understood - thanks. (On the sort of aircraft I fly, the AP HDG HOLD does the same thing, cancelling NAV and enabling HDG mode instead). Pete
  25. True, but unless the A/P is engaged surely that only provides Flight Director assistance to the pilot (on aircraft equipped with FDs). Pete
×
×
  • 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.