John Dowson

First, you have no assignments whatsoever in FSUIPC7 - neither axes or button assignments. How is your parking brake assigned? Your log file does show issues - did you manually disconnect and reconnect, or was this automatic? Those entries show FSUIPC7 stopping after 20 seconds, connecting again then stopping after 3 seconds, then connecting again. Do you know why? Can you add the following to the [General] section of your FSUIPC7.ini file: TestOptions=x800 and activate logging for Events and generate another log file. Just load your aircraft, wait a minute or so, then test your parking brake assignment, then exit FSUIPC7 before attaching your log file. Please also explain how your parking brake is assigned. If using an FSUIPC offset, you should add logging for that offset (maybe offset 0x0BC8 as U16).

Than download it from the very first comment in this topic/thread. John

That preset doesn't work - not sure why. I took a look at this and you should assign to the Input Event FUEL_1_Condition_Lever on your axis ranges using a parameter of 2 for cut-off, 1 low idle and 2 for High Idle. I have done this for you in the attached ini file if you would like to try it. John FSUIPC7.ini

All registration/license details for products purchased via SimMarket can be found in your SimMarkeeeeey account. No. You have to click the Register button, which will validate the license details entered and generates the key file. If that is successful, you are good-to-go. If you have a key file, then you either clicked that button or copied it across from your old installation. John

By the way. '//' are NOT the characters that you use to define a comment. Use a semicolon ;. To keep comments in their place, if they are not the first comments in a section, you need to put the semicolon after the index number.

For the Asobo C208 Caravan condition lever, you have to assign to the presets not the FS event. There are two ways to do this: 1. Assign your axis to the button presets Fuel Condition Lever Cutoff, Fuel Condition Lever Low Idle & Fuel Condition Lever High Idle to specific ranges of your axes using the right-hand side of the axes assignment panel. 2. Define an axes preset for the condition lever in your myevents.txt file (create this file if it doesn't exist). Add the following: Restart FSUIPC7 and then assign your axis to this preset (C208 Fuel Condition Lever Set) using the left-hand side of the axes assignment panel. There may also be an Input Event that you can use, but to do this you would have to use an offset and a lua script, so try the preset first.

Please do NOT attach screenshots - attach your FSUIPC7.log and FSUIPC7.ini files. Depending on which aircraft you are using, you may need to assign to something else (e.g. a preset or Input Event). Your FSUIPC7.log file will tell me what aircrfaft you are using, so please show me/attach that. John

Can you please show me/attach your FSUIPC7.log and FSUIPC7.ini files, the former showing your issue (i.e. set logging for Events and Buttons & Keys, and press the button assigned to the parking break and then exit).

There is no way that FSUIPC can add these axes assignments by itself. You probably edit the ini file when FSUIPC was still running. When editing the axes sections, you must do this either when FSUIPC is not running, or if it is running with the axes assignment tab open, and click the Reload all assignments button after you have saved your changes. You should also change to use substrings in your profiles, i.e. change to Also switch to using joyletters - change AutoAssignLetters=No to AutoAssignLetters=Yes in your [JoyNames] section. John

@ark1320 & @kaha. I have added an option that will disable the opening of the FSUIPC7 main window all the time, even when a new version is available. To do this, add the following to the [General] section of your FSUIPC7.ini file: OpenOnStart=Never Note however that this will not take effect until after the next release, 7.4.6, so if you add this now FSUIPC7 will still open when 7.4.6 is released, but not for subsequent releases. John

I have finally gotten around to looking into this. The problem was that when you exit FSUIPC the size/position if all Wnd library windows is saved and used to set the size/position the next time you tun FSUIPC7. If the window is iconized, the size/position was still saved, but using this to restore when next run gives issues as the iconized size is then used on the window which is not initially iconised. I have fixed this by not saving the window position if/when iconzed. This update will be in the next release of FSUIPC7 (7.3.6). John

👍

This cannot be correct - joysticks are either a number (the id) or a single letter (joyletter). What do you see in the button assignments window when you press your button? Probably just 'D'- the 'P' in 'PD' is from your assignments, and indicates the action - a button press: The left one should register as different button numbers, depending on its position, and the right one should have one (or possibly two) button in each direction. If it has two, then one is a 'fast' button and the other a 'slow' button. If it one has one in each direction, there is a lua script available to allow fast/slow detection if needed. Try: 35=CP(+D,20)D,12,CPPMDG_B737_Cruise_Alt_Inc,0 -{Preset Control}- John

You could also register for an event but do nothing in the event handling function- just registering for the event will keep your script running/window open. You could even use a timer event if you wanted to close the window after a number of seconds/minutes. The lua script that updates the window could run the lua that creates the window if the window isn't available/created yet, or use the handle if the window was available. If using an endless loop to keep the window open, maybe add a sleep call in the loop body. John

👍

Thanks for the update. No need to feel like an idiot - this has been a problem for quite a few folks and it wasn't clear what the issue was. Did you assign to the discrete position presets using the right-hand side of the axis assignment panel, or did you try the axis preset I gave above? Maybe if you could post/share your assignments, this will help others. Cheers, John

This is the calculator code for that preset: @ 20 - 10.03 / near 0 max 100 min s0 l0 5 < if{ 714101 (>K:ROTOR_BRAKE) quit } l0 15 < if{ 714201 (>K:ROTOR_BRAKE) quit } l0 35 < if{ 714301 (>K:ROTOR_BRAKE) quit } l0 50 < if{ 714401 (>K:ROTOR_BRAKE) quit } l0 64 < if{ 714501 (>K:ROTOR_BRAKE) quit } l0 75 < if{ 714601 (>K:ROTOR_BRAKE) quit } l0 85 < if{ 714701 (>K:ROTOR_BRAKE) quit } l0 98 < if{ 714801 (>K:ROTOR_BRAKE) quit } 714901 (>K:ROTOR_BRAKE) This looks to be written for an axis/potentiometer range of 20 - 1023. To change to a standard range of -16383 to +16383, you can use the following (i.e. add this to your myevents.txt file and then assign your axis to it): My_PMDG_B737_Flaps_Set#@ 16383 + 327.68 / near 0 max 100 min s0 l0 5 < if{ 714101 (>K:ROTOR_BRAKE) quit } l0 15 < if{ 714201 (>K:ROTOR_BRAKE) quit } l0 35 < if{ 714301 (>K:ROTOR_BRAKE) quit } l0 50 < if{ 714401 (>K:ROTOR_BRAKE) quit } l0 64 < if{ 714501 (>K:ROTOR_BRAKE) quit } l0 75 < if{ 714601 (>K:ROTOR_BRAKE) quit } l0 85 < if{ 714701 (>K:ROTOR_BRAKE) quit } l0 98 < if{ 714801 (>K:ROTOR_BRAKE) quit } 714901 (>K:ROTOR_BRAKE) John

Then you need support from PACX / TFDI Design - cannot help with 3rd party programs from other developers. Be aware that if running FSUIPC7 as admin, all 3rd party programs must also be ran as admin, as well as MSFS2020 itself. Everything that communicates needs to be ran at the same privilege level. John

If you want the window to be always open, then you should have one script that creates the window and then waits for events to update the windows contents. The events could be anything - an offset change, a flag change, a button or key press/release, an event, etc. You do not need two scripts, or to create the window each time.

Another user has reported a similar issue and has determined that it is the flaps calibration that is causing this issue. So maybe try with just the flaps calibration removed, and maybe re-assign your flaps differently if you cannot use them without calibration. See John

How are/were your flaps assigned? Rather than assigning a flaps lever to an axis, for the PMDG you can assign to the presets that move the flaps between the discrete positions, using the PMDG B737 Set Flaps n presets (where n is 1,2,5,10,15,25,30,40 or Up - 9 discrete positions). You can do this on the right-hand side of the axes assignment panel. Alternatively, you can define a preset that does this (in a myevents.txt file) on an axis, similar to the PMDG B737 Flaps Set (Potentiometer) preset but adjusted for your axis range, and then assign your axis to this preset.

You can do that but I would not recommend it - a script should run and exit when finished. There is no other way to keep a lua thread running as this should not be necessary. Create the window in the other script and try to eliminate whatever is causing the "flashing".

Hi @Jackiie. If you are still having this issue, now that you can assign directly to Input Events you could try assigning to the input event AUTOPILOT_KAP140_1_ALT with a parameter of 1. This will simulate the actual button press and toggle between VS and ALT modes, and should give the same behavior as pressing the button. John

After looking into this further, I don't think i will be implementing this. Issues arise when there is a long press but only an event on a short press - should the short press function still be called? Presumably so, otherwise this would effect existing behavior, but this then means the function called depends on the events registered which is a pain to handle...This is also problematic with switches which are like buttons but are 'always on' or 'always off', which can also give issues (as FSUIPC doesn't know the difference between a button and a switch, it just sees the change events. Note there are already lua scripts that you can use to handle long and double button presses - see John

👍