John Dowson

'Send direct to FSUIPC calibration' contains the FS and FSUIPC added controls that go through calibration before being sent to the FS. This is generally the preferred method, although can sometimes produce problems with some aircraft, mainly complex add-on aircraft, due to priority levels. If you have issues with this method, switch to sending to FS as normal axis. There are many more axis controls available when sending to FS as normal axis, and many cannot be calibrated (although they can be scaled) in FSUIPC's calibration facilities, although some of the main control axis can still be calibrated if needed, although this can sometimes cause issues (again, due to priority levels as well as masking issues). John

Save it to your FSUIPC7 installation folder, replacing the one that is currently there. Make sure you have the WASM installed and enabled - if the menu items under he Add-ons-WASM menu are enabled, then the WASM is connected (try listing lvars to confirm). John

How are you using them? Can you provide an example? If they are not listed by FSUIPC, I cannot see how they can be used via lua. It doesn't matter when you start FSUIPC7/LINDA, and the WASM is always started by MSFS, regardless of whether FSUIPC7 is running - it is in your Community folder. And the lvar list is provided by the WASM, and will be generated (i.e. the scan for lvars performed) LvarScanDelay (WASM ini parameter, default value of 5) seconds after leaving the MSFS main menu (when the PLANE IN PARKING STATE simvar changes to false), regardless of whether FSUIPC7 is running or not. Try increasing the LvarScanDelay parameter, or perform a WASM Reload() at some point to see if they are picked-up.

What do you mean by 'accessible'? If they are not listed, how can you know they exist and their value? Not that I know of... The FSUIPC WASM scans for lvars by asking for the lvar name in a loop on the lvar id (using the gauge API function get_name_of_named_variable) and stops when either a null name is returned or the maximum number of lvars that FSUIPC can handle (currently 2044) are found. I guess if an lvar was registered with a null name (if possible...I would expect/hope not!) then this would stop the scanning and any further lvars would not be found. Another possibility is that they are created some time after aircraft load, but a new scan is performed when listing lvars (from the WASM menu) and so they should still be seen if created later when you list them. How do you know these lvars exist, and how are they accessible? Do you know their ids?

I was just suggesting logging the events in the FS as seen by FSUIPC, so in FSUIPC - just activate event (non-axis controls) logging, open the logging console, flip the switch off->on an on->off and see what events/parameters are logged. Turn on logging for Buttons & Keys - this should show you what FSUIPC sees when you flip the switch, and both button presses and releases are logged. John

Assignments will only be added to your FSUIPC7.ini if you add them... If assigning in FSUIPC7, check that you are using an empty profile for your controllers in MSFS - or at least that you do not have dial assignments - i.e. an axis/button assigned in both MSFS and FSUIPC7. John

Yes, as the one you were using had flap assignments that you were unintentionally triggering. The way to achieve this is to use the menu option Options -> Reset to Defaults, or just delete your FSUIPC7.ini and let a new one be created. There is no need...as your only assignments are axis controls to flaps, you may as well just use a default FSUIPC7.ini, as you are at the moment. You could remove the assignment (and calibration) lines from your current ini to maintain the profiles, but as the profiles do nothing without any assignments, there is really no point. However, I have removed these in the attached FSUIPC7.ini... John FSUIPC7.ini

This is not correct....you had some controls to flaps set in your general axis section so this would apply to all aircraft: and you also have some fir specific profiles: You also have various flaps calibration entries: So with the loss of airspeed and the wind noise, I suspect you were deploying your flaps by mistake. John

Ah, ok - I didn't know that had been released. As they are rotor brake parameters, you can assign a button directly to the Rotor Brake control/event, and give the number as the parameter. Alternatively, if you want to use them as presets, you can create a file called myevents.txt, and add them as follows: PMDG_GLSD_MCP_AP_VNAV#38601 (>K:ROTOR_BRAKE) PMDG_GLSD_MCP_AP_LVLCHG#39101 (>K:ROTOR_BRAKE) ...etc Note however that most of these (if not all) already exist as MobiFlight presets but with different names: PMDG_GLSD_MCP_AP_VNAV === PMDG_B737_MCP_VNAV_SWITCH PMDG_GLSD_MCP_AP_LVLCHG === PMDG_B737_MCP_LVL_CHG_SWITCH ...etc These MF presets are not available in the current events.txt file included with FSUIPC7, but will be included in the next release (in the next few days). I've attached it below. John events.txt

As I responded to your other post on this...are you sure that isn't for the P3D PMDG 737? As @adnanso pointed out in this post, you should look in this file for the MSFS Rotor Brake control parameters: ..\pmdg-aircraft-737\Documentation\PMDG\PMDG_NG3_VC_700.xml You can then assign to the Rotor Brake control with the appropriate parameter, or create a preset. Also check the MF preset list (https://hubhop.mobiflight.com/) as one may already be available.

Are you sure that isn't for the P3D PMDG 737? As @adnanso pointed out in this post, you should look in this file for the MSFS Rotor Brake control parameters: ..\pmdg-aircraft-737\Documentation\PMDG\PMDG_NG3_VC_700.xml

There are currently no specific FSUIPC offsets for the MSFS PMDG 737. As I said in my first response, I am waiting to see if the data is available to populate such offsets. John

Ok, that is interesting, thanks. I'll take a look...once I have the aircraft....!

There is an Export presets button at the bottom of the search grid - I presume you can use that, although I have never tried. You shouldn't modify the events.txt file, as ant changes will get overridden when you next install FSUIPC7. If you want to add events, use the myevents.txt file. However, you can just use the update events.txt file I posted earlier, as suggested by @adnanso. This will be included in the next FSUIPC7 update, hopefully tomorrow but maybe the day after. Event files are different - these are for custom events. You could use these, but you would then also need to install the MobiFlight WASM module which handles these. Presets are an alternative that are executed by the FSUIPC WASM module. John

No, not really... But if its a toggle, there is no 'on' signal, just a toggle one (i.e. to change the state from on to off or from off to on, depending upon its current state(. Have toy tried logging events, and see what is logged when you switch on and off via the UI? This should tell you what events and parameters are used. John

You can zip it - it should compress pretty well. That sounds strange - panning should not affect the parking brakes, and not 'setting them up' should make any difference... So it sounds like it is related to something in your original FSUIPC7.ini. You can post that and I will take a look. You could also try putting it back to see if the problem still occurs. If so, maybe comparing the FSUIPC7.log files produced by the original ini and the new/default ini may show what is happening. John

This is an internal axis control only and is not currently available via the SDK. I will add it if and when it becomes available.

1001 and 1002 are additional FS controls added by FSUIPC (see Advanced User guide, not offsets. And I don't think they will work with vPilot. You can assign the key in vPilot to PTT, and then write to an offset to send the assigned key press. The controls for this are 1071 (Key Press/Hold) and 1072 (Key Release), or maybe 1070 (Key Press and Release) - again, see the Advanced User guide for details. To send any control to the FS using offsets, you use offset 0x3110 (See the Offset status document for this). Alternatively, you can send key presses via offset 0x3200 instead. John

PMDG custom controls should be documented in the PMDG SDK...maybe in the header file...I have still not seen this for the MSFS version of the PMDG 737. Hoping to have this soon. John

As the instructions say, only delete the folders that match the VID and PID for the device you are trying to correct. Also, I would strongly advise taking a back-up of your registry before making any changes. Also, make sure that you have not installed any saitek drivers or software. If so, uninstall those and let windows install the default drivers. John

If it is a toggle, i.e. clicking it once switches on, clicking again switches off, then you would use the same control/parameter for both operations. That is if the control is just for the switch. If PMDG provide separate on/off controls (I don't know as I don't have/use this aircraft) then you would use those separate controls. Please don't post for support in the FAQ section - use the appropriate support forum. And give your post an appropriate title and other PMDG users may be able to assist... John

Is this different to the Steering Set control? What is this called? I have not seen such a control and cannot find it in the documentation...Maybe this is an internal control and is not available via the SDK - if this is the case, it won't be available via FSUIPC until Asobo provide access to this as an external event/control. There is a simvar available, STEER INPUT CONTROL, but this is documented as read-only. Have you tried using the Steering Set (axis) control? This is available when you select 'Send to FS as normal axis' (and not when 'Send direct to FSUIPC calibration' is selected) John

Are you sure that you are using the correct parameter? The parameter value is (I think) a value which represents what type of mouse click to simulate for the particular switch. See the following guide on how to determine both the control number and parameter value to use: John

Yes, this was fixed and released for FSUIPC6, but I have not released the fix for FSUIPC7 yet. I have attached the next release, v7.3.4 below - I will release this officially once I have gotten around to updating the documentation. John FSUIPC7.exe

Did you try logging (events) to see if anything is logged when you activate the speedbrakes in the UI? Also, check to see if there are any lvars available for this. Also keep an eye on the available MF presets for this aircraft (https://hubhop.mobiflight.com/) - I can't see any at the moment, but this is the community resource where such things are added and made available when found. Note the preset list (events.txt) installed in your FSUIPC7 folder is most probably out-of-date and will not contain any of the PMFG 737 presets. I have attached the latest one below - use this to replace the one in your FSUIPC7 installation folder. John events.txt