John Dowson

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

A couple of things you could try: - assigning to the default keypresses instead - F1 to idle, F2 (on repeat) to increase reverse thrust - assign a button to Throttle Reverse Thrust Toggle (or Set Reverse Thrust On/Off) and then use throttle axis for reverse. Also available for individual engines. - if assigning to the above in FSUIPC has no affect, try assigning in MSFS. If it works when assigning in MSFS but not FSUIPC, you can assign keypresses to the events/controls in MSFS (there may already be a default key press assigned, if so you can use that) and then assign to the key presses in FSUIPC. There is also no problem having mixed assignments - some in MSFS, others in FSUIPC. Note that I don't have the Fenix and so cannot test these. It may be that you also have to calibrate for reverse thrust in the MCDU first - see the following tutorial: Also, please see this post on avsim" https://www.avsim.com/forums/topic/619709-solved-fenix-throttle-calibration-no-reverse-on-axis/. Maybe some other Fenix/FSUIPC users can help you further with this.... John

No it won't - that is an illegal button assignment - you can only assign to one action per assignment line. You need to adds 2 additional assignment lines for each of your 3 buttons. If you have no current assignments to those buttons (which I guess is the case, as you are just using the button flags which are toggled automatically), for button 1, assign the press to Button Flag Clear for button 2 (i.e with parameter 56 * J + B, as stated in the manual), and either then duplicate this assignment and change the parameter to clear the button 3 flag, or (if your buttons are the press/release type) you can assign to clear the button 3 flag on release. As well as not being the correct format, you need to clear the flags when the buttons 1/2/3 are pressed, NOT on the rotary buttons, which should just inc/dec the appropriate value (and not change any flags). John

I can't see how the CRJ profile can be loaded when you are using the PMDG B728. Could you please attach your FSUIPC7.ini and FSUIPC7.log file, the latter generated when you experience your issue, i.e. with the PMDG aircraft loaded and the CRJ profile selected 9please exit FSUIPC7 before attaching the files). Does this also happen if the PMDG us the first aircraft loaded or only when you switch aircraft?, i.e. if you exit MSFS / FSUIPC with the PMDG aircraft loaded and then restart, is the CRJ profile also then loaded? Thanks, John

Great! Yes, I am sure there is...are you using button flags for you compound conditions? if not, switch to using those. Then, when button 1 is pressed, you can have two additional assignments that clears the button flag for your 2nd and 3rd buttons, and similarly, button 2 would have additional assignments to clear the flags for buttons 1 and 3, and button 4 to clear the flags for buttons 1 and 2. See page 21 for details on the "latching" flags, as well as the controls to set/clear/toggle these manually. Btw, I have just noticed that you are using FSUIPC7. There is a specific sub-forum for FSUIPC7 / MSFS - I will move this topic to that subforum. John

Do you have a license? You need a registered version for the lua facilities - if you have not purchased yet, please try the trial license, available here: Use the provided resources - the documentation that comes with FSUIPC (there is also a zip file containing example lua plugins), and the forums - you can look in the FAQ sub-forum and the User Contributions sub-forum for lua scripts that others have provided. John

You should always try the trial license before purchasing, to make sure that the registered FSUIPC version is suitable for your needs... This sounds very strange - FSUIPC isn't doing much here, except receiving data from the FS, and no difference between the free and registered version. Could you leave it running for a few minutes to see if anything changes, and if not, exit FSUIPC and then show me/attach your FSUIPC7.log file. You can also try disabling auto-start (i..e re-install and uncheck the auto-start button). Then try starting FSUIPC7 once your aircraft is loaded and ready-to-fly. John