John Dowson

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

Which FSUIPC window? The main one or a dialog box? How are you opening it? If it is the main window you are referring to, and you open this with Alt + F. then it could be that that key combination is also assigned in MSFS - so maybe check you MSFS key assignments. Otherwise, could you activate logging for Buttons & Keys as well as Events, and produce a short log file showing your issue.

Also, note other users may have an issue with the axis range, not just the reversing. As I said, the script expects each axis to be in the -16383 - +16383 range. Quite a few axes, especially those home-made using potentiometers, can have a different range. If this is the case, you would also need to calibrate the pot's range input to the script to -16383 - +16383. John

Great! It is not an issue if an axis is/needs reversing - many axes work in this manner. To handle this nicely in the script, you can add add two boolean variables - rudderAxisReversed, brakeAxisReversed, and then use those to determine whether to reverse or not. Then it is a simple matter of setting those to true or false. If you can attach the script you are using, I can make those changes for you. John

FSUIPC3 is now free - you can find a registration code on www.fsuipc.com. Here are the details: John

You should not uninstall default aircraft, as they will get re-installed the next time that you restart. There is no need to do this.. The problem with lvars, especially with default aircraft, is that the lvars from the previously loaded aircraft are still available. If I load the A310, I get the max of 3066 lvars, and this is with the Aerosoft CRJ, FBW A320, PMDG 737, JF PA28, Flying Iron Spitfire and several more aircraft in my Community folder. If I then switch to the C171, I still get 3066 lvars. However, if I then exit and restart MSFS, use the same C172, I only get 150 lvars. So, the solution at the moment would, when switching planes, first switch planes in MSFS, then exit and restart, and you should see the number of lvars reduce substantially. Can you try this as well to see if you see the same behavior? Cheers, John

You didn't offend me - sorry if it came across that way. I was just puzzled by your reply... Anyway, there are still quite a few MSFS key input strings I am not requesting, and it could be one of them, although it is strange that the key is registered as #~ by FSUIPC. Could you run FSUIPC7 without MSFS running. activating logging for Buttons & Keys, press the Ö, Ü & Ä keys (in that order), then close FSUIPC7 and show me what was logged - either paste the lines logged for each key or attach your FSUIPC7.log file. I will also see if I get emulate using a virtual keyboard (as I don't have a German layout keyboard!).

Just move the entire fsuipc-lvar-module module folder out if your Community folder. However, thinkin about this a bit more, that also cannot/should not caise MSFS to CTD, as WASM modules are sandboxed (that is the whole point if them!) and so if they crash, they should stop working and MSFS should continue. I really think your problem lies else where... John

Did you read my original comment? Did you look at the valid key input strings I referenced? If they are there, I can add them - I can't see them, but then neither can I see Ö and Ü... And there is something I have already done about this - allowing ALL keys to be recognised by switching to the keyboard hook method, as I said. There is no way that I can add key input strings via SimConnect that are not recognised by MSFS - surely you must understand that. So, in effect. I do not understand your last comment. and I have already provided an alternative solution. John

Keyboard input in FSUIPC7 is (usually) received from MSFS via SimConnect. The only keys supported by SimConnect are shown here: https://docs.flightsimulator.com/flighting/html/Programming_Tools/SimConnect/API_Reference/Events_And_Data/SimConnect_MapInputEventToClientEvent.htm - see the section Valid Input Strings. Unfortunately it does not look like these keys are available. You can raise this with Asobo - if they add input events for these, I can make them available to FSUIPC7. There is one possible way to get these keys in FSUIPC7, which is to switch from using SimConnect for key input events, and enable a global keyboard hook to be used instead. To do this, set the following in the [General] section of your FSUIPC7.ini file: UseKeyboardHook=Yes See the Advanced User guide for details on this parameter. John

Good news indeed...and good luck! Let me know how it goes... John

👍

That should work, but you also need to change the assignment index number (the first number), and make sure you do this either when FSUIPC is not running, ot if it is then the button assignments window must be open, and once you have saved the file you must press the Reload button to reload the assignments from the file. If it is just two controls that you want to send, and it is a button and not a switch, then you could also assign one control to the press and one control for the release. Another method of doing this would be to create your own preset, using the myevents.txt file. If you are not familiar with presets, if you show me the assignment line that you want to duplicate, and let me know the additional rotor brake value you want to add, I can show you what the calculator code for the preset would be. There may already be a preset available for this - you can check on HubHob. John

This is certainly not an issue with FSUIPC or the installer, and so there is nothing I can do. It is either something you are doing or system settings (permissions). You are not even running the FSUIPC7 installer! As I said before, make sure you unzip the downloaded file before running the installer, and I recommend just unzipping from your Downloads folder (not in your desktop). And check any anti-virus software which may be blocking or removing the installer. Have you actually checked it is there? Did you try what I suggested in my previous response? I am closing this thread now as thee i really nothing more I can say or do on this issue. Try google (as this is nothing to do with FSUIPC). John

It is for technical reasons in how the lvar names and values are passed from the WASM to FSUIPC (via the WAPI). I could increase this (would involve an update of the WASM and WAPI), and have already done this once (from 2044 to 3066) quite recently, in version 7.3.5 released 29th May. I may consider increasing the maximum limit again, but not at the moment. I don't want to be increasing this every 6 months if the number of available lvars keeps increasing like this. MSFS should only provide the lvars for the aircraft currently loaded - the rest are just noise. John

Extensive documentation for FSUIPC7 is installed in your Documents folder when you install FSUIPC7. Also available from the Documents section of this forum, although that will be slightly out-of-date. There is no such file. FSUIPC7 stores is user-settings in a file called FSUIPC7.ini, located in the FSUIPC7 installation folder. This file is created when you first run FSUIPC7, if not already present. John

Sorry for the delay - I will look into this further in the next few days... John

No problem - and me too!

Can you please turn off logging for both Lua Plugins and Log Lua Separately. If you want to show me a log file, I just want to see your FSUIPC7.log file, and also your FSUIPC7.ini file if you have issues. And, as I said, you should open the logging console (Log->Open Console) and monitor the output in real-time. I also suggest you re-read my previous posts to make sure that you have set everything up correctly. You are also using an extremely old and unsupported version of FSUIPC7 - 7.0.0-Beta from 19/8/2020. This is a very early version - please update to the latest (and ONLY supported) version which is 7.3.15. John