John Dowson

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

@ZenMusicSoaringThe trial license has been updated, valid until 10th April 2022.

I just tried this in the G58 and assigning to Flaps Up/Down is working as expected here, so I'm not sure why that isn't working for you. Are they working from the UI? Your log shows these controls being sent/received ok, so it is strange that those aren't having any affect in the aircraft...

If you are planning on using the SDK, you don't need a registered version. Registration provides access to assignment facilities, the lua interface, etc - see the documentation for a full list of the additional facilities provided by the registered version. John

Yes, it is always available...you just need to post here if its out of date and I will generate a new one (as it says in the initial post). I'm finishing for the day now. I'll generate a new one either tomorrow or Sunday, when I get time... John

First, can you please not start a new log file when providing logs for support - it is easier to see what is happening in just one log file, you can always zip it if its too big to attach. Your settings for the view controls don't work as these controls are not working in MSFS. From the README.txt file (included in the FSUIPC zip file you downloaded): I'm not sure why the flaps controls aren't working as I would expect them to work in the Asobo Baron G58. Could it be that these are working but the inc/dec values are too small to notice? Try changing the flaps assignments and set 'Control to repeat while held' and see if that gives any movement. Otherwise, use the standard method to work out what controls are needed - activate logging for Events, move the flaps in the UI and see what events are logged in the FSUIPC7.log file (you can do this with the console window open using Log -> Open Console). Then try assigning to those. I can look into this later if you still have issues with this - let me know. Also be aware that many MSFS aircraft do not use standard controls and you have to use a combination of lvars/ hvars events and calculator code for many assignments. FSUIPC7 also now includes access to the MobiFlight presets which you can also assign to - see the MobiFlight HubHop resource (https://hubhop.mobiflight.com/) which has a good search interface for finding presets for many aircraft, both Asobo and add-ons. John

Ok, but that is strange. Usually once an offset is allocated to a simvar (or sim event for writes) it doesm't generally change. \in the documentation I have, viewpoint piyvh, bank and heading are at offset 0x83D4 and marked as 'FS2004 only' (i.e. FSUIPC3!). Yes. They are offset addresses into an FSUIPC byte array. No. They are populated from FS memory locations in earlier version of FSUIPC (i.e. hacked) , but from FSUIPC4 onwards they are populated using the SimConnect SDK. Once an offset is allocated for a particular simvar or function, we try to keep that offset allocated for the same simvar/function across all versions of FSUIPC, although this sometimes isn't possible. Cheers, John

Are you using an MSFS version from Steam or the MS Store? If using a steam version, please see the README.txt file included in the zip file you downloaded: If you are using an MS Store installed version, delete this file: C:\Users\Pc\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt Also, please make sure that you extract the files from the zip file you downloaded before running them. From the log file you attached, it looks like you are trying to run the installer directly from the zip file (windows allows you to do this for some reason) - this can cause issues: John

Yes, better to use one function rather than two. However, two (or multiple) events on a key or button shouldn't be a problem really, but I cannot confirm that for FSUIPC3 - that may be restricted to a single event per keysytoke/button (and per lua thread). John

May not be there in FSUIPC3 - best to check. This really isn't the place for programming basics... The values are passed to the function via its parameters. The third parameter contains the downup value (hance this is why we call the variable that holds this downup) as an integer (not a bit), with possible values described in the documentation. Not sure what this means - 'bypass the downup function'? there is no 'downup function'... And event handling functions don't return anything. Did you not see my example above: I suggest that you look at some of the example lua scripts provided, or check out some of the user contributed lua scripts (see the User Contributions sub-forum). John

Thanks for sharing. Could you possibly create a post in the User Contributions section and attach your wiring and configuration diagrams directly to the post rather than linking to a shared (google) drive? The problem with such link is they tend to not last that long. You can also reference this topic for further details. Thanks and regards, John