John Dowson

Please stop posting links (sharing?) to other comments in the same topic - use the "quote" mechanism to reference previous comments, i.e. select the text that you want to reference and then a 'Quote selection' box will appear which will quote the text in your new comment. Alternatively, you can copy/paste the text, and then format as a quote in the menu bar directly above the area where you enter your comment. This will make your messages far easier to understand (take a look above!). Please activate logging for Buttons and key operations and Debug/Trace Lua plugins (assuming you are using FSX or P3D). Then generate a short log file showing your issue, i.e. load an aircraft and press the F3 / F3 keys a few times, then exit FSUIPC and show me/attach (not paste contents!) your FSUIPC ini and log files. I still don't even know what FS or version of FSUIPC you are using, but your files will tell me this...presume it is either FSX or P3D - if you are using MSFS (2020) then this lua script may not work (and you are also posting in the wrong forum...) You can also take a look at the log file as well, or, better, open the logging console (check Send to console window in logging tab) when you do this to see the log in real-time - first check the lua is started and running without issues, and then that the key presses are triggering the lua moveThrottle function, and check if any throttle events are also sent. This should give you a clue as to why it isn't working, and if you post/attach those files here I can also take a look. John

No, you do NOT edit the lua script. just leave that as it is and place it in your FSUIPC installation folder and add the [Auto] section to your FSUIPC ini file (see below). Then, start the FS, open up FSUIPC and assign the keys you want to use to LuaSet Throttle as I said....if you do not know how to assign keys, please see the provided User guide. No, add the following: [Auto] 1=Lua Throttle Please re-read that section, this is not that hard to understand, and it is clearly explained....I do not understand how you could think it would be "[Auto.throttle.lua]".... Note that you need a registered/licensed version of FSUIPC to use lua and the assignment facilities.

As I said, you cannot assign to the mouse using FSUIPC, so I cannot help you with the mouse/throttle issue. You can use the script available in this topic for the F2 and F3 keys. To do this, you need to save the Throttle.lua to your FSUIPC installation folder, and then assign the F2 and F3 keys to the control/event LuaSet Throttle with a parameter of 2 for inc and 3 for dec (and 1 for cut if you want to assign for that). You should also have the lua auto-started by adding it to the [Auto] section of your FSUIPC ini file - see the Advanced User guide if you don't know or are not sure on how to do this. You should also remove the key bindings in P3D/FSX if doing this. You can also select other keys instead, but whatever keys you use make sure they are not also assigned in the FS. John

How have you assigned the throttle to your mouse? Are you using FSUIPC for this - if so, how? Could you please show me/attach your FSUIPC ini file. Lua files go in the FSUIPC installation folder (or in the LuaFiles folder, if that is set). But I am not sure if you can use that lua if you are using the mouse for throttle, and I am not sure how this works. Could you explain further - or do you mean that you are just using the mouse to control the throttle in the VC? The lua uses flags to control the throttle : flag 1 for cut, 2 for increment and 3 for decrement. FSUIPC doesn't handle mouse assignments (except for specific purposes such as mousewheel trim/move/look), so you cannot assign your mouse to set those flags... John

It won't be an issue with the WASM then. You could try and see if you can reproduce in a debugger to see what the issue is? Otherwise a debug (or maybe even a trace) log from the WAPI for when this issue occurs would be helpful. You shouldn't need to do this - you can use registerLvarUpdateCallback to get a callback when an lvar value changes, which would be better than polling. John

That is strange in itself - FSUIPC starts the numbering at 0 whereas windows ar 1, so usually #25 in windows would be #24 in FSUIPC. That does sound strange...you could try activating logging for Buttons & Keys and see if anything is logged on that change - open the logging console (Log -> Open Console) and check in real-time. If there is no button press event registered, there may be a release event for the previous position that you can use.... John

What do you do to get it working again - restart your application or restart MSFS? If you have to do the latter, it could be an issue with the WASM. Did you check your FSUIPC_WASM.log file? Are you using any other WAPI clients (e.g. FSUIPC7)? Could you set Debug level logging in the WAPI (WasmPtr->setLogLevel(LOG_LEVEL_DEBUG)) and in the WASM (via the FSUIPC_WASM.ini file) and show me both your WAPI log file and the WASM log file the next time this occurs. Thanks, John

Sorry but I don't understand your issue.... Presets are available by checking the Select for preset checkbox in all assignment dialog windows. To find an appropriate preset, use the MF HubHob site - https://hubhop.mobiflight.com/presets/. Note that there a re no presets listed for the 737-800, but you can use the ones for the 737-700. If you are having issues using presets (or anything else), please show me/attach your FSUIPC7.ini file, together with an FSUIPC7.log file showing your issue (and with logging for Events and Buttons & Keys activated). John

As I said, it is better to edit the [Profile.xxx] to specify a substring that will match all variants/liveries, rather than adding the aircraft to a profile each time you use a new livery. John

This can only occur (sometimes) if you have installed FSUIPC7 in a windows-protected folder, such as under Documents or Program Files. If that is the case, re-install into a non windows-protected folder. However, for most reports of this issue, it is either due to: 1. A different variant/livery of an aircraft being loaded that is not covered by the name in the existing profile. If this is the case, you can add the new variant to the same profile, or better to edit your FSUIPC7.ini to give a substring to the aircraft names in the [Profile.xxx] section so that they match all variants (and no others). 2. A misunderstanding of how the button assignments work with profiles. With axis assignments, you will only see the axes assigned in the current profile, and the profile name will appear in the window title bar. For button and key assignments, this is not the case. To see your profile button/key assignments, you need to manually check the 'profile specific' check-box before pressing the button/key, or only the general assignments will show. This is because it is possible to add general button/key assignments to an aircraft that uses a profile, but not for axes assignments. Any further issues, please show me/attach your FSUIPC7.ini and FSUIPC7.log files. John

Could you please post a link so that others can find it if they come across this post. I don't see why - ir is quite straightforward: 1. Download the Rotaries.lua (save to your FSUIPC7 installation folder) and add this (or create) and [Auto] section in your FSUIPC7.ini to automatically start the lua file when an aircraft is loaded. This will give support ffor both fast/slow buttons on the Bravo - the trim wheel and the inc/dec rotary. 2. Copy the IngnoreThese statement to your [Buttons] section of your FSUIPC7.ini. This will prevent the rotary buttons being seen in the FSUIPC assignments window, as you will assign to the virtual buttons provided by the Rotaries.lua instead. Change the letter B to the letter used by your Bravo, if is is not the same - see the [JoyNames] section of your FSIOPC7.ini to determine what letter to use. 3. Copy the trim assignments to your [Buttons] section, and again change the letter B to the letter used by yout Bravo, if different, and make sure the assignment indes numbers (the first number on each assignment line) re unique, and if not, change them. It really isn't that complicated. John

👍

You could have tried searching the forum for this, which is what I have to do when such questions are asked - it would save us both some time.....! See John

Note there are two custom controls for this: You are using EVT_MCP_COURSE_SELECTOR_L (70008), but It look like you need to use EVT_MCP_CRS_L_SET instead, i.e. 84132 John

From the documentation: The control you want to sent is Button Flag Set, which has a control number of 1003, so you need ipc.control (1003, param) where your param = 256 * J + B. So, for joystick #1 button 3 you would use: ipc.control (1003, 259) They are different flags, specific to lua. Note also that if you want this to run every time you start FSUIPC, you can use either ipcInit.lua or ipcReady.lua and you then don;t need to use the Auto section - from the FSUIPC Lua Plug-ins document: John

👍 You can use a lua script to do this and have that started from your [Auto] or profile-specific [Auto.xxx] section. You can send the Button Flag Set control with a simple ipc.control statement. John

Could it be the magvar (bgl) data? See https://www.aero.sors.fr/navaids.html : (from Dr P3D) But 3 degrees seems a big magvar change....Let me know if you update/try this and get better results.... John

If the latest combined VC++ redistibutables are not installed, yes. I don't know what comes installed by default on a new PC. Please see the documentation I rferenced - that gives instructions and a link to download. Please refer to the manuals and other similar support requests before requesting help. I have responded to this same issue many many times now.... John

Please see the provided Installing and Registering FSUIPC document, section Invalid Key Problems. If all three parts of your registration (name, address/email, key) are as specified in your purchase order, then the issue will be with your VC++ redistributables that need updating. John

You can try sending two flaps inc controls on up, and two flaps dec controls on down - this should skip the intermediate position. You can try assigning a flaps up on button press and release, and similarly for down. That may work, although I'm not sure as this depends on how the flaps lever works in the Bravo (my system with the Bravo is not up at the moment so can't check - I can do this later/tomorrow if needed). Otherwise, you can open your FSUIPC7.ini file and duplicate the flap assignment lines (best done with FSUIPC not running, or with the button assignment window open, then click the reload button after making and saving your changes). Just copy and paste the flap assignment lines and change the index number of the assignment (the first number) so that it is unique. Presets are included. You need to check the Select for Preset checkbox in the assignment window. See the Advanced User guide, WASM section, on presets. Make sure you are using the latest version of FSUIPC7, currently 7.3.16. John

Looking at your CRJ 7-- profile: The PMDG aircraft is called and so matches your CRJ profile. Change yout CRJ 700 profile section to: You should also change your PMDG B738 profile section to: i.e. use substrings to match more variants rather than the full aircraft name (including variant). John

It should be... You are holding it as an unsigned byte (UB) - try changing that to SB. If it still doesn't work, let me know and I will check using negative values here. John

Just noticed that you posted this in the FAQ sub-forum, where it explicitly states NOT for support requests. Please use the appropriate support forum when requesting support - in this case it would be the FSIOPC7 / MSFS sub-forum. I will move this topic to the correct forum. John

Ok, thanks for the update. Argh! You should get into the habit of making backups before major updates, just in case...can save a lot of time....! Good luck! John

Details are currently on the Download Links -> Useful additional programs page, and will also soon be on www.fsuipc.com (once I have gotten around to updating this page): John