John Dowson

👍

Did you restart FSUIPC7? Presets are only loaded when FSUIPC7 is started. Also, check you are using th correct preset - the image shows that you are still using the MF preset from the events.txt file. You need to delete them - click Delete all followed by Ok. John

Then you need to reverse the axis range in the preset, i.e. //A2A SIM/Comanche 250/Engine MY_PA24_250_Carbheat_Axis#@ -1 * 16384 + 327.68 / 0 max 100 min (>L:Eng1_CarbHeatSwitch, Number) John

1. If you are assigning the preset to an axis, then you do not need to check Select for preset'(top-right). This is for sending presets on axis ranges as button controls, Remove this. 2. The correct way to send axis values to a preset is by checking Send Preset to FS, which you have done, but then you also need to check the first box below this and select the preset from the drop-down menu. 3. The following preset: PA24_250_Carbheat_Axis#@ 15 - 10.0 / 0 max 100 min (>L:Eng1_CarbHeatSwitch, Number) subtracts 15 from the axis value ("15 -") then divides by 10.0 ("10.0 /"). If you are using a standard axis, that will have a range of -16384 to +16383, and you need to calibrate this to the lvar range of 0 - 100. To do this. define your own preset in the myevents.txt file as follows: //A2A SIM/Comanche 250/Engine MY_PA24_250_Carbheat_Axis#@ 16384 + 327.68 / 0 max 100 min (>L:Eng1_CarbHeatSwitch, Number) Then assign your axis to this preset (using the left-hand side of the axes assignment panel, not the right-hand side). John

Your upload limit will increase as you post more - it is restricted/rather low for new users. Try compressing/zipping them - they should compress well as they are only text files. Otherwise, you can share them using one of the web transfer services to do this, such as https://filetransfer.io/ or https://wetransfer.com/. I have the G2 so I can check with that aircraft here. John

Sorry but I do not understand what you are talking about. There are no facilities in FSUIPC to create SimObjects, - I have no idea what 'FSUIPCInt.CreateSimObject' means...

What version of the ATR do you have installed? Maybe check for an update. I have just checked here and all is working as expected. On my dev system, I have both condition levers assigned to the same axis, and this works fine: which is using the following presets (in the myevents.txt file): MSATR CONDITION1 LEVER SET2#@ 16384 + 10923 / near 0 max 3 min (>L:MSATR_CONDITION1_POS) MSATR CONDITION2 LEVER SET2#@ 16384 + 10923 / near 0 max 3 min (>L:MSATR_CONDITION2_POS) I have also tested with the following macro (ATRCondition.mcro): and have assigned buttons to this, just testing with condition lever 1 only, and setting the parameters on the assignment as such: and they all work as expected. So you are certainly doing something wrong.... Please check that you are using the latest version of the ATR and try the above - either on an axis or buttons or both. If not working, please attach your ini and log files again, the latter with appropriate logging activated (i.e. Extras, Events and Buttons & Keys if using buttons, and Axis Controls if using an axis). Maybe easier if you try the buttons first, but up to you. John

No need. I will just use a spare button. You will have to update the scripts I provide for your controller letters, axes letters button numbers and offsets to use anyway. This seems very similar to the Spitfire differential braking, except the control for that was on a brake lever which is an axis. Should be simpler on a button. John

This post is for the Spitfire brake. I referenced it for you as you need to do something similar for the CJ-6 Nanchang. I will help you with this in the thread where you asked. Once this is done, you can create a User Contribution similar to this to explain to others how to do this in the CJ-6.

Ok, that should be possible via lua. How are you planning to control the "brake handle"? Do you want this assigned on a button or key press? I will take a look and provide you a lua script to test, but it may take several days as I am pretty busy at the moment (well, always!). John

Not sure I understand this. The ATR has 2 condition levers that each have 4 discrete ranges. Why don't you just use two of the Bravo axes to control this using those presets? Ok, so setting the L:MSATR_CONDITION1_POS and L:MSATR_CONDITION2_POS lvars to a value between 0 - 3 no longer moves the condition lever? That is strange, and something must have changed. I will take a look and get back to you. John

Ah, ok.... Can you attach your macro file please. As the condition lever has 4 discrete positions, I am not sure how you are controlling this on a button. Why don't you use an axis (the Bravo has plenty!) and use the axis presets defined in this post: John

Also, please see this comment on the same issue (PMDG 737 reversers): Also see further down for another possible configuration (I have just asked the user to post his settings). It seems that nothing is perfect for the PMDG 737 reversers - configure and use what mostly works for you. The main issue seems to be a jump from reverse to forward motion when killing reversers which is rather strange! John

@C.Schaffhausen said: Could you please share your assignments for this for other users to try. Thanks, John

i have this aircraft now. I can see this brake lever, and it is documented as: 39 Brake grip on Rear Control Stick, Press and hold to set wheel brake active. However, I cannot seem to 'press and hold' this - when I click it, it moves to the right slightly, sends a BRAKES control, and then goes back to its original position. I presume the toe controls only control the rudder (i.e. only lateral movement, no movement on each pedal. How is this supposed to work? Does moving the tie pedals usually control the rudder, and when you want differential braking, you move the brake lever to the right (and hold it) and then use the rudder control for differential braking? You can assign a button or key to the FS control BRAKES, on repeat. This will move the brake lever and keep it in position while the button/key is held. If you then want to use the rudder pedals for differential braking (if the aircraft supports this), you would have to use a lua script to control both rudder and breaking. You would write your rudder axis value to an FSUIPC offset, and then monitor this offset in a lua script. When the offset changes, your handling function will receive the axis value, You then decide if this is a rudder control or a brake control by looking at the state of the brake lever (you can also monitor this to determine if braking or steering). As I now have this aircraft, I can help further, but I need to know how this works in the aircraft, and how you want to assign to reflect this. It seems that if the brake lever is sending the BRAKES control, it isn't doing differential braking. John

For the 737 reversers, rather than sending Throttlen_Cut on the reverser release: try sending an F1 key press instead: Otherwise there are two presets that you can use to kill reverse thrust (i.e. to assign on reverser release): PMDG B737 Eng 1 Reverse Thrust Kill PMDG B737 Eng 2 Reverse Thrust Kill These use the PMDG custom controls: #define EVT_CONTROL_STAND_REV_THRUST1_LEVER (THIRD_PARTY_EVENT_ID_MIN + 680) #define EVT_CONTROL_STAND_REV_THRUST2_LEVER (THIRD_PARTY_EVENT_ID_MIN + 681) so you can use them directly instead if you don't want to use the presets. John Later: Ah, ok. They seem to work here... Try them anyway, and if not working switch to using those presets.

Also, please activate logging for Lua Plugins, so that I can se the timestamps of the lua calls to see what is taking time - no other logging necessary, especially NOT Lua Plugins Separately.

The PMDG 737 has always used throttle cut followed by throttle decr to activate reversers - I don't think there are lvars (or custom controls, which is what the PMDG normally will use if the standard controls don't work). But I will take a look later. To diagnose an issue, I always need to see the .ini and .log from the same session/flight, so I will have to look at your previous files. If you update the ini, and would usually need to see the log generated from using that ini. You can opt to not log/ignore such controls (i.e. ones that are continually sent) using the DontLogThese ini parameter, e.g. Those timestamps do not correspond to the log file you have posted.... Please see the following (long) topic on how to assign to the reversers in the 737: I also have this set-up on my Bravo on my flight system for the PMDG 737. I will check if that is working and send you my Bravo config. John

Looking at that ini, there is no axis assigned to throttle1: ?

This seems rather strange, as you are sending the left/right brake controls on the R (rudder) axis, and are also repeatedly sending BRAKES_RIGHT or BRAKES_LEFT when the rudder is more than approx 2/3rds full left or full right.

I am not sure I understand this - and I don't have this aircraft. Do you have a reference on how this works or can you provide further details? How is the "brake handle" recognised - is that an axis or button, and is any control logged when used, or maybe an lvar is changed? You will probably need to use lua if you want an axis condition. You would write the axis values to an FSUIPC offset, and have a lua script monitor these offsets, calibrate the value and send the appropriate control depending on the brake handle position, which would also need to be monitored. There is a User Contribution for something similar, where a brake lever is used to control differential braking on a rudder axis - not the same I know, but shows the technique of how to send different controls on an axis depending on another lever: I can see if I can get hold of this aircraft and take a look, but this may take a while. John

Can you please make sure you are using the latest released version of FSUIPC7, 7.4.11, or even better try the latest beta release, available from: and show me your FSUIPC7.log, FSUIPC7.ini and csv files. As I said, I only see this here when FSUIPC7 is started by MSFS via the EXE.xml file, and I have no idea why this is. I will look at you files to see if I can see anything, but there is not much I can do. What is the load like on your system? What aircraft do you have loaded - if using an airliner, have you tried with a GA aircraft? John

Controls that go from external apps via SimConnect do not go through the same route as internal controls. This has already been raised with Asobo - see https://devsupport.flightsimulator.com/t/xml-key-event-bindings-do-not-intercept-key-events-via-simconnect/8320. I am not an aircraft developer/gauge programmer, so cannot really assist you with this xml code. Can you see the Input Event in FSUIPC (Log->List Input Events)? If so, you can use this directly. However, you can only assign to Input Events for buttons, keys and when entering/leaving axis ranges. To assign an axis to an Input Event in FSUIPC, you have to assign the axis to write to an FSUIPC offset, have a lua script that monitors the offset (using event.offset), calibrates the axis value to the Input Event range, and then send the Input Event using ipc.execInputEvent. It is also not clear to me how Asobo determine what Input Events are available via the SimConnect Input Event interface/functions. This would also be a question for Asobo. Sorry I can't be of more assistance - as I say, I am not a gauge programmer and you would get more help with this on the Asobo forums. John

The MF Hub-Hop resource/website is the community-driven effort for discovering and publishing presets. I am certainly not going to create a 'proprietary' set of presets - these should be available to the community. And from what I have seen of the C510, it seems to mainly use Input Events for a lot of external control. It is NOT possible to use input events via presets, which is why a presume there are no presets yet available on the MF Hub Hop site for this aircraft. This has been requested before and I have already spent quite a while looking into this. It turned out to be too problematic for several reasons, and I am not going to look at this again, at least for the time being. I am just too busy. I don't see a need. If you just want to know what input events are available, use Log->List Input Events. Just switch on Input Event logging when you want to see if an input event exists on a certain button/function, and to see what parameters it is using. No - there is no distinction between where key presses come from, I just get a key press/release events (not the source), so this is just not possible.

There will be no radar facilities available in the first release of AS for MSFS, but they are working on it. I will look into adding this to FSUIPC7 when available in AS. Regards, John