John Dowson

Maybe, why not just try that as a preset, like the one I showed? But it would be better to use lua and do it properly, although it probably doesn't matter....whatever works for you really! Thanks @mtjoeng! John

👍

That is interesting, thanks! I keep forgetting Andrew has released his module for the MSFS PMDG 737. But that script/extract is also missing the functions PMDG_MPNL_AUTOBRAKE_move(numberOfpositions) PMDG_MPNL_AUTOBRAKE_show () - as well as the definition of the PMDG_EVT....Can you show those - as well as any other dependent functions. You always have to be careful extracting lua scripts from LINDA as there can be many dependencies, but it is a good reference to check how things work / what is available. @737AndiYou could try using LINDA if you are not familiar with lua. Or you could add the lvar L:switch_460_73X (which golds the current switch position) to an offset, and then use that as an offset condition for overloaded preset assignments...

👍

You can have multiple assignments to a button by manual editing the ini file. However, if you do this they will always be applied, regardless of the rotary position. Is there an lvar that you can use to determine the current rotary position? If so, you could add that to an offset and use that to determine the current rotary position, but O don't think this would work that well as the update of the lvar value will be a lot slower than the the check on this for the assignments. This seems strange, as if you are decreasing 6 times, and then increasing twice, isn't that the same as decreasing 4 times? BUT. lookig at the calc code for those 2 presets. they are the same....shouldn't the inc one use 46002? But you can do this by adding your own preset (to the myevents.txt file) that does this, e.g. PMDG_B737_AUTOBRAKE_MULTIPLE#46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) You could then (possibly) add an offset condition , if the current state of the switch is available in an lvar then you can add that to an offset and use that, and then overload the assignment to call the correct number if inc/decs depending on the current position. But its probably to do this in lua.... John

No. You don't need to use event files any more - they have been superseded by presets. However, you can still use them if you prefer that method, but you would need to install the MF event module WASM to handle those events. The event files included with FSUIPC7 are also now quite old (and I won't be updating them any more) and not complete (and possibly out-of-date).

There is no event file for the PMDG. However, you can create one if you wish, using the MobiFlight cip file. You would then also need the MobiFlight WASM module installed to handle those events. As event files have basically now been superseded by presets, I am no longer providing event files. There are no custom events provided and handled by the PMDG 737 as far as O a, aware - the custom events for this aircraft use the Rotor Brake control, with the parameter indicating the purpose/control. BUT, this will have nothing to do with your MCP not being able to connect. I don't know what your issue is with this and cannot really help you either. You need to contact whoever provides the software for this.

Where have you installed FSUIPC7? Make sure that it is not in a windows protected folder, such as under your Documents or Program Files folder. Also, check that it is not there but with the extension hidden - make sure that 'Hide extensions for known file types' is not checked in your Windows Explorer options. It should certainly be in your FSUIPC7 installation folder, alongside your FSUIPC7.log file, and is created the first time you run FSUIPC7.

MF presets have been included with FSUIPC7 since v7.2.16 - you do not need to use MobiFlight. The latest version, v7.3.4 (released yesterday) contains the latest MF events.txt file. To use these with FSUIPC7. you need the FSUIPC WASM installed and enabled (which you will have if using lvars), and they are assignable as any other control - in the drop-down menu for assignments. Please see the Advanced User guide for details on presets, as well as all other functionality provided by the FSUIPC WASM module.

Why don't you just execute the script: ipc.execCalcCode(“1 (>L:LIGHTING_LANDING_1) 0 1 r (>K:2:LANDING_LIGHTS_SET) 1 1 r (>K:2:TAXI_LIGHTS_SET)”) Or avoid lua altogether and assign to the preset Preset: NOSE LIGHTS TAXI?

Did you check that FSUIPC7 is running? Where/what software is this error message from? There is no *.evt file for the PMDG 737. Event files only provide access to custom events that are handled by either the aircraft or a WASM module. The event files that come with FSUIPC7 are mainly for use with the MobiFlight event module, although there is also one for the FBW A320. However, you do not really need use event files any more as they have been replaced by presets. A preset is a name attached to a calculator code string, which when used is applied by the FSUIPC WASM module. Event files are events that are mapped to similar calculator code strings but this is done in the handling module, usually the MF event module. The PMDG 737 seems to have implemented its custom controls using parameters for the Rotor Brake control. You can assign to this control directly, if you know the parameter values to use (I believe someone posted a spreadsheet containing these...somewhere...) - otherwise you can use (or at least take a look at) the preset calculator code, or see what is being used by a preset. For a searchable list of available presets, please see the MG HubHop resource: https://hubhop.mobiflight.com/presets/ John P.S. You seem to have raised the same question twice - I will delete the other one

It is John - Peter retired several years ago, although he still occasionally helps out. They seem to be working for most folks...I cannot confirm as I do not have this aircraft at the moment... See https://hubhop.mobiflight.com/. Please read the Advanced User Manual for information on presets and on how to use the WASM to access lvars, hvars etc. You do not need to use MobiFlight to use presets. MF presets are included (in the events.txt file) with FSUIPC7 and they processed/applied using the FSUIPC7 WASM module. You can use the MFConnector.exe to download the latest events file and copy it to your FSUIPC7 installation folder if you wish (i.e. when there are new presets not in the one that is distributed with FSUIPC7), or you can just add any new preset manually to the events.txt file, or the myevents.txt file.

You should complain/raise a ticket with Fenix as their installing is overwriting your original exe.xml with its own. It should update the existing exe.xml rather than replacing it. Yes - see attached. Bit its not that difficult - you just need to paste the new <Launch.Addon>...</Launch.Addon> section into your original exe.xml, withing the SimBase.Document element: exe.xml Take a backup of your exe.xml. If any installer overwrites or corrupts it in any way, you can go back to the original, look at the new exe.xml and copy the <Launch.Addon>...</Launch.Addon> section to the working exe.xml. John

FYI, v7.3.4 was released yesterday which contains the latest MF events.txt file, as well as several bug fixes. John

No - I added that ini parameter which, when activated, will try to do thus by calling the unregister_all_named_vars function, but this doesn't seem to make a difference. It should really be up to MSFS/Asobo (or maybe the aircraft developers) to do this - I don't think there is anything else I can do. I will look into increasing the maximum no of lvars available for the next release. However, there has to be some limit. It is recommended to clear your Community folder of (especially) aircraft that you are not using before starting MSFS. Many people use the MSFS addons linker for this. This also improves load times.

I am confused by your post. You say: but also: So some presets work for other aircraft, but non for the PMDG 737? If so, then it sounds like FSUIPC7 is functioning correctly and applying the preset calculator code, but if this has no affect then it is a problem with the calculator code, not FSUIPC7. Check the preset/calculator code on the MF hubhop preset list, and report any problems to MobiFlight. FSUIPC is aircraft agnostic - you can apply any preset to any aircraft. There are no specific files (apart from those you create) for any aircraft. But there were no PMDG presets available for the PMDG in the events.txt file provided by FSUIPC7 until v7.3.4 (released yesterday). If not using this version, download and try that as it includes a more current MF events.txt file (from yesterday).

This is already provided and is called myevents.txt - it is recommended to use thus file to add your own presets as the events.txt file will be updated/replaced when you re-install FSUIPC7. It is also recommended to submit any presets derived to the community-led MobiFlight HubHop preset list. Please see the Advanced user guide on using presets for details. This was released yesterday in v7.3.4 (as well as including the latest MF events.txt file, amongst other updates/bug fixes). Can you check this with the latest version as I think I have made further changes, but this does sound like an MSFS issue. If you don't want to use the MSFS key bindings, you can remove them - or set-up an empty profile for the keyboard as you would for other controllers if/when assigning in FSUIPC.

Yes. However, there may be other controls that set the value, rather than in or dec. However, if this is a rotary switch that goes through a distinct value set, then it is usual (for UI-oriented controls) to only duplicate this behavior. There may be other controls to set the value (or maybe an lvar), but using those may not trigger the associated UI animation. You could write a lua script to do this, but you would need something that holds the current state of the switch (maybe an lvar?) to determine how many inc/dec controls need to be sent.

Sorry, but I know nothing about the wiring of switches... I am not saying anything of the sort... What I am saying is that I cannot help you as you are continually NOT showing me your FSUIPC ini file (your actual assignments) or your FSUIPC log file (what is actually happening), with the appropriate logging activated. I do not even know what version of FSUIPC you are using at the moment. If you want me to help you with this, please show me those files and we can take it from there. John

Yes, PMDG aircraft have always been problematic when assigning direct to fsuipc calibration, or when calibrating when assigned to the FS, although some people seem to be able to do this without a problem. However, if there are issues, we recommend switching to sent to FS as a normal axis and not calibrating (and you can still scale/reverse via editing the ini file).

As I said, one is for the joy id, and one id for the joy letter. Both are needed to perform the mapping between letter and id. Yes, they are needed for the mapping. If you want to assign your own letters, you would change the numbers to letters, and on the next run the entries with the numbers/joy ids would be added back. To assign your own letters, there is no point setting that ini parameter back to No now. As this currently defaults to yes, you can just change the letters that have been assigned. You can add AutoAssignLetters=No in the [JoyNames] section, which will prevent letters to being assigned to new devices. If you are changing the letters and already have assignments to those letters, you also need to update your assignments to use those new letters.

And you do not have repeat set? If that is the case, then the switch must have one button in one direction, and another in the other direction, and you need to assign the toggle to both buttons (or it is not wired correctly...). Logging would tell you what is happening - activate logging for buttons and also events, flip the switch and see what is logged, and flip it back, and see what is logged then. You can post the FSUIPC7.log here, together with your FSUIPC7.ini if needed. The files are more useful than a video...

The FSUIPC_WASM.ini file under your Community folder will get overwritten when you re-install FSUIPC7. For this reason, it is recommended to copy the FSUIPC_WASM.ini file to the WASM persistent storage area and make any modifications there. This ini takes precedence over the one in the Community folder. From the Advance user guide: Glad you solved the problem though! John

You are using a switch, which sends a button press in one direction, and a release in the other direction. Therefore you need to send the toggle control on the button release as well.

That looks correct to me... you have 5 controllers, and each is shown with its windows assigned joy id and its FSUIPC assigned joy letter. FSUIPC uses the jou letter for your assignments, and uses that section to map the windows assigned id to the joy letter, which prevents issues that can occur if your joy ids change. But why do you want to do this? You should really leave this as-is unless you want to assign your own letters. But if you want to do this. the AutoAssignLetters ini parameter goes under the [JoyNames] section, not under the [General] section. From the User guide (page 20): John