John Dowson

Ok. No idea why these aren't recognised, but at least you have an alternative solution.

👍

I will now handle this... I have managed to clone the project and build it. You need VS2017. Tomorrow I will transfer it to my GitHub account and give you access there. I'll post the new URL when done. John

I am sorry but I do not understand what you are trying to say here... Your log is far too large for me to go through....why do you have Axes Controls logged? I just need to see what, if anything, is logged when you close the fsuipc window. Can you open the logging console (Log -> Open Console) and watch that to see what is logged when you close the window, and paste those log messages. Also, does this happen only with the button assignments window? What about the axes or key assignments window? Does it also happen when you click cancel, or only when you click ok?And why do you need to be opening this window all the time? FSUIPC doesn't send anything the the FS when you open close fsuioc window, so I really have no idea what is going on on your system.

If it is working, what is the problem? You can add the server name or ip address if you like, but make sure you are using the correct parameter - ServerName if using the name, ServerIPAddr if using the address. John

Not necessarily...but you can always assign a button to a key press that is assigned in MSFS. You usually only use this technique for internal events that are either not working when sent from an external application (such as these), or for events that are not exposed by the SDK for use by external applications.

Simple update - see attached (untested!). Glad this is working for you! Regards, John spitfireBrake.lua

I know what SIOC is, of course, but never used it and don't know what ' the SIOC Connection to FSUIPC' is. ok, thanks for the update. John

As I said, please provide your FSUIPC7.log file with the suggested logging activated and showing your issue, together with your FSUIPC7.ini. i.e. activate logging for Buttons & Keys as well as Events, reproduce your issue, exit FSUIPC7 and then attach your FSUIPC7.log and FSUIPC7.ini files. John

Did you also login with your Microsoft account? I have just checked, and the repo is still private. If you let us know your microsoft user account name, @Pete Dowson can either add you to the project, or make the repo public (it is up to him!). John

First, your WideClient is out-of-date (7.146) - please update to the latest version, 7.155. Your WideClient.ini has this: That is NOT the server name - should be: ServerName=DESKTOP-OVELNI8 or use ServerIPAddr=169.254.207.245 Try using the name first, and if that doesn't work switch to using the address. Also, please check your firewall settings (or disable all firewalls, client server and router, to test) - you may have added an exception for P3D and need to add one for MSFS. John

And the logs after quitting FSUIPC7? I need to see all 4 files together from the same session.

First, you need a registered version of FSUIPC7 for assignments - if you do not have a license, you can find a trial license in a post at the top of this forum. I have no idea what this is, sorry - I don't use SIOC. I suggest that you just try and see if your yoke is recognised by FSUIPC - if it is, you can just assign your elevators and ailerons in the normal way (see the provided documentation for this). Otherwise, if your yoke is not seen by FSUIPC, then you should ask about this on OpenCockpits (or the card support forum). If the yoke isn't seen by FSUIPC as a standard HID joystick type device, it may be possible to use lua. But I would ask about this with the card provider first, John

Please do not attach partial logs - always exit FSUIPC7 before attaching log files. Note that WideServer will not be started until you have a plane loaded and ready-to-fly, so WideClient will not connect before that. So, please try again and make sure that your aircraft is loaded and ready-to-fly. Any issues, please exit FSUIPC and WideClient before attaching logs, and also attach your WideClient.log and WideClient.ini files. John

The camera controls don't work in MSFS via external assignments. You have to assign your POV to the default key assignments in MSFS for controlling the view. These are, by default: lctl+Left, lctl+Right, lctl+Down, lctl+Up. John

Glad you found a workaround. I've looked into this further and WideClient IS certainly receiving offset updates when paused, regardless of the offset in question. All offsets in WideClient are treated equally in this respect, so I am not sure what your original issue was. I have attached the scripts I used for testing if you want to try them on your system. The server lua script eventTest.lua waits until the sim is paused, and then updates offset 0xA000 with a counter, once a second. The client lua script eventTestClient.lua has an event on this offset, and the handling function just logs the count and repeatedly reads the same offset until the sim is unpaused and the lua on the server sets the offset value back to 0. John eventTest.lua eventTestClient.lua

The MakeRunways source is (or should be) available for anyone to download and modify. It is available from a git repository at the following location: https://petedowson.visualstudio.com/MakeRunways/_git/MakeRunways So, to install locally, start VS and then click Clone a repository and enter that repository location. Make sure that you have Git installed on your PC. If you get any errors, let me know (I am not sure if Pete has actually made this a public repo yet...). I think you may also need to authenticate yourself with a Microsoft account first. I am also not sure what version of VS this is built with... you should be able to use this in all/most versions of VS, but you may need to install some older/newer libraries, but VS should prompt you with this - I wouldn't recommend updating the platform toolset if prompted. John

Ok, glad you found a solution. However, I do not understand why FSUIPC7 isn't recognising your zapbox buttons > 31, and would like to know if the buttons are recognised without the virtual joystick (and Joystick Gremlin) running. I cannot think of anything else that is preventing this. I, and many other users, use multiple devices with > 31 buttons without issues. John

I see you are using a vjoy device as well - what is this? Can you see buttons > 31 with that device? Could you repeat this test with the vjoy device disabled/disconnected? There is a registry issue with this device and that of the zapbox, but that shouldn't cause any issues (just warnings): Other than that, I do noy know what can be causing this - FSUIPC7 just isn't seeing those buttons for some reason. You can try the older method of handling > 32 buttons. which is using a lua plugin. There is an example lua script provided called HidDemo.lua in the lua examples zip file in your FSUIPC7 folder. I have also attach a version of this script updated for your zapbox device. Save this to your FSUIPC7 installation folder and add it to the [Auto] section of your FSUIPC7.ini file, i.e. Once that lua is running, see if you see any virtual buttons recognised when you press a button with a number > 31. If not, please attach your FSUIPC7.log file again. HidDemo.lua

You do not enter control assignments in the main window that appears on the desktop. That just provides a message window together with a menu bar which you use to open the assignment dialogs. What type of assignment are you trying to add, i.e. which dialog window? Can you please be more clear so that I can understand what you are doing, and provide your FSUIPC7.log file with the suggested logging activated and showing your issue, together with your FSUIPC7.ini. Thanks, John

Ok, thanks. Then it seems that Ö is using VK_TILDE and Ü is using VK_SEMICOLON. As Ä has VK 222, I expect this is using VK_QUOTE. This VK is not currently handled. I have enabled this key, plus two others (VK_0xDF and VK_0xE0), in the attached version, 7.3.16a, if you could try it. Thanks, John FSUIPC7.exe

Your ini file shows no assignments at all.... Which controller of yours has 71 buttons? Can you please run FSUIPC7 on its own (i.e. without MSFS running), activate logging for Buttons & Keys and open the logging console window, then press some buttons on this controller with 71 buttons, some that are recognised and some that aren't, and see what is logged in the console window and what is recognised in the button assignment window. Close FSUIPC7, then attach your FSUIPC7.log file and tell me what you saw for the different button presses, recognised or not.. John

Yes, and I said: Can you please do that, i.e open a command prompt and type dir %LOCALAPPDATA% and then dir %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache Can you see the file? I didn't assume this - I was just pointing out that the WASM/WAPI download is intended for developers, or WASM users that do not use FSUIPC7. It is better to correct the WASM installation problem. However, if you want to install it manually, you extract the file fsuipc-lvar-module.zip from the file SDK\FSUIPC-WASM.zip (in your case, this would be C:\FSUIPC7\SDK\FSUIPC-WASM.zip). Copy that to your Community folder, unzip it and then delete it. The information on the WASM is provided in the Advanced User guide. There is no tutorial. The WASM is just used to provide functionality for FSUIPC7, such as providing access to lvars/hvars and calculator code. So, for example, if you assigned a button to a preset, when you activate that button, the calculator code defined by that preset is sent to the WASM to be executed in the FS. What questions of yours have I not answered? I would have more time if you read my replies and followed my advice... John

Can you please show me your FSUIPC7.ini file, and an FSUIPC7.log file showing your issue, i.e. activate logging for Axes Controls, load an aircraft that has an assigned axis that isn't working, move that axis through its full range and back, then exit FSUIPC7 before attaching the FSUIPC7.log (you can compress/zip it if too large to attach directly). John

FSUIPC7 supports up to 128 buttons for each controller/device since v7.1.0. Button numbers in FSUIPC7 go from 0-31 and then 132 - 227, with 32-39 being reserved for a POV button. Can you show me your FSUIPC7.ini and a FSUIPC7.log file please. John