John Dowson

This is support for FSUIPC and WideFS/WideClient (+ related products. I cannot support XPUIPC or XPWideClient, sorry - they are from another developer. I suggest you try XPUIPC support. John

First, you posted in the wrong forum - I have moved your post to the FSUIPC7 sub-forum. FSUIPC7 can be used as freeware or as a registered version. The registered/licensed (payware) version has additional functionality not available in the unlicensed/freeware version, such as assignments and access to the lua scripting interface. Please see the documentation for a full list of features. There is a trial license available in a thread at the top of this forum if you would like to try the registered facilities. Please try before you buy. John

You must assign an axis before calibration, and you should assign to 'Send direct to FSUIPC Calibration' (i.e. make sure that check-box is ticked). Once you have assigned to an axis in that way, you should be able to calibrate it in the relevant calibration page. Please see the User guide section THE EASY STEP-by-STEP WAY TO CALIBRATE YOUR CONTROLS on page 38 if the User Guide. You should also have an aircraft loaded in MSFS (i.e. not in the main menu). John

Ok, thanks for reporting back. For the JF Arrow, there are also MF presets ALT_baro_knob_left and ALT_baro_knob_right, which will be listed in the Controls drop-down as 'Preset: Alt Baro Knob Left' and 'Preset: Alt Baro Knob Right'. John

Did anything change? Can you also please attach your FSUIPC6.ini file. Also, generate a new log, but this time with Axis logging enabled and move your yoke. Do your other assignments work, the yoke buttons/POVs and other devices? If you go into the axis assignments tab and move your yoke, do you see the in/out entries change, and do you see your assignments there? John

First, the offset is 0x0354, not 0345, and the offset is in BCD format, so you write 0x1200 to the offset, which is 4608 in decimal. John

This is the support forum. I appreciate you are trying to help others, but the place for that is the User Contributions forum. Please post there, with a suitable title for your posts. I am sure people will find them useful, but they will get little, if any, attention, on the third page of this ongoing topic... I am closing this topic now. John

But you said you were using FSX with FSUIPC4.... I cannot support XPlane/XPUIPC, sorry - never used XPlane and XPUIPC is from another developer. John

Offset 0x0354 allows you to set the transponder code, but you would need to write the code you want to use there in BCD format. If you want to assign a rotary for changing each digit, use the xpndr controls via offset 0x3110: 66455 XPNDR_1000_DEC 65651 XPNDR_1000_INC 66456 XPNDR_100_DEC 65652 XPNDR_100_INC 66457 XPNDR_10_DEC 65653 XPNDR_10_INC 66458 XPNDR_1_DEC 65654 XPNDR_1_INC e.g. to increase by 100, you would assign the clockwise rotary button that changes the third digit to write 65652 to offset 0x3110. John

Pete retired several years ago. What exactly is your problem? What FS and version of FSUIPC are you using? Have you tried the xpndr inc/dec controls? You can send use them with MobiFlight using offset 0x3110, which will send any control to the FS.

This usually depends on which aircraft you are using, which you don't mention. You can try the standard controls - Ap Alt Var Dec/Inc. Otherwise, check the MobiFlight HubHop resource (https://hubhop.mobiflight.com/) to see if there are is anything specific you need to use for the aircraft you are using. John

Ah, sorry max - should have known/checked that!

First, you posted in the User Contributions sub-forum. That is a forum for users to contribute solutions, lua scripts, how-to's, etc, and is not the place to request help. I have moved your post to the main support forum, where it belongs. This should be set when you arm your spoilers...i.e. whatever button/switch/axis position you are using on your controller for arming should change this offset (either directly or via the appropriate control). i don't use MobiFlight so can't really help you with this. You may get help from other MF users if you had used an appropriate title...I will update this for you, but please remember to give your posts an appropriate title that can attract other users that may be able to help. Maybe also see this post - the user who posted this may be able to help: John

Hi Paul, did you get anywhere with this? Re-reading this thread, if you are just looking for an offset to send a keypress, then you can use 0x3200. However, this sends the key press to the FS - if its a hot key in vPilot then it should also be detected by vPilot. John

Hi Jock, seems reasonable to me - thanks for posting your solution. Cheers, John

Which FS are you using? Have you checked the Offset mapping document for the PMDG 737 (in your FSUIPC documents folder)? If they are not listed there, then they are not provided by the PMDG SDK. John

Then it looks like you cannot use mouse macros with that aircraft. But what rotary switches - what functions do they control? What controls have you tried - either standard or custom? Have you tried the custom controls: ? As I said, I don't have any PMDG aircraft do can't really help you with this. You should specify the aircraft you are using (as well as the FS) in the title of any support request as this may attract other users who have the aircraft and may be able to help. John

What control are you trying to use? If there is a control for what you are trying to achieve and it doesn't work, I suspect that there is a problem somewhere else...If there is a conttol available, you should try to use this instead rather than a mouse macro. I need more details than this... After you select 'Create Mouse Macro', you then click 'Ok' to close the FSUIPC window. there should be no message window displayed until you actually click somewhere in the cockpit, and the letters should alternate between white-on-green and red-on-green, as explained in the user guide. Are you saying the message box appears without you clicking anywhere in the cockpit? I can take a look at mouse-macro making in FSUIPC4/FSX but I don't think this would help, as I don't have any pmdg aircraft, and this functionality has been around for many years without issues. Maybe also try in another aircraft to see if this is a PMDG-specific issue, or is a general issue on your system - or maybe it is not possible to use mouse macros with PMDG aircraft? John

Ok, thanks for the update Detlef, glad you got it sorted. John

Once in idle, you should be able to use the "THROTTLEn DECR" controls to engage reverse thrust. See this post: There are also plenty of videos around on how to configure the Bravo for throttle & reverse in airliners. Although these are mainly for MSFS, they should still apply to P3D as most of the controls are the same (SimConnect events), and they should at least give you an ide of the controls that you need to assign to - for example, see I don't have any PMDG so cannot really advise any further. I have added PMDG to the title of your post to attract any other PMDG users that may be able to assist. John

Can you explain what exactly you mean by this? Mouse macros aren't really the best way to assign PMDG controls in any case. PMDG have been good enough to supply individual <custom control>'s for pretty much everything. Just find the ".h" type file in the aircraft's SDK and follow those instructions. The list of controls is at the end. You need to calculate the control number then assign it via the <custom control> selection in FSUIPC. See this post in the FAQ section: You also posted twice for the same issue. I will delete the other post. John

As the message says, you need to select the correct device before toy assign to that device - your devices are shown above the assignments with the current profile the device is using. If assigning in FSUIPC, you should start/create a new empty profile for that device. But this is not the place for MSFS support really. You should familiarise yourself with MSFS before configuring FSUIPC. John

@sebgengen First, please do not hijack unrelated topics for random questions - create a new topic if you cannot find a suitable topic. Your question has nothing to do with the trial license, i.e only post here to get me yo generate a new trial license if the current one has expired. LINDA is a lua interface built on top of FSUIPC's lua interface, which requires a registered version of FSUIPC. For Saitek panels, you can also use SPAD (free) or SPAD.next (payware). John

Please see offset 0x310A in the FSUIPC7 Offset status document (although some of the bit numbers seem to be missing, which I will correct): Controls the joystick connection to the main flight controls. Normally all zero, set the following bits to actually disconnect the specific joystick axes (from least significant bit = 0): 0 Elevator 1 Aileron 2 Rudder 3 Throttles (all). 4 See below (throttle sync control) 5 Elevator trim 6 Throttle #1 7 Throttle #2 (see next byte for others) This feature is intended for use in protecting autopilot flight from interference from axis flutter. In order to protect the user from a broken or crashed application, all the flags are cleared 10 seconds after they have been set, so applications will need to repeat the setting every few seconds. ... John

This sounds strange to me. The flaps in the G58 have three positions: Down (DN light lit, lever down), APH (APH light lit, lever in central position) and up (no lights lit, lever in up position). Moving the lever in the UI will result in the 'IN TRANSIT' light to be lit while the flaps move, then goes off when in position. The flaps lever shouldn't move again from the position you set. If you assign to Flaps Up / Flaps Down, you can only switch between the UP and Down positions, and cannot set to APH. If you assign to Flaps Inc and Flaps Dec, you can move through all 3 positions, as in the UI. I don't think so as it seems to be working fine here. However, no controls are logged by FSUIPC when you move the lever in the UI, so internally it does look like its using something else, but this shouldn't matter as the external/SimConnect controls are working as expected as far as I can tell.. Check that you don't have assignments to flaps in MSFS - if assigning your controllers/devices in FSUIPC, best to start with an empty profile for that device in MSFS. John