17 minutes ago, Lorby_SI said:

I have Saitek TQs, so I am mapping the reversers to the lever's button function that actuates when you pull it past the detent. Works absolutely fine and individually for each engine too.

Thank you for answering my question.

I have this "https://throttletek.com/747-400-boeing-throttle/ " , and for some reason, I can't map correct reversers properly. With FSUPIC I can, as I mentioned before I would rather use your software versus the other one. That's where my problem is. If you could give me some guidance on how to get it to work (step by step), I could try. Unfortunately, I'm out flying for another 4 days before I get home.

Thank you!

11 minutes ago, LRBS said:

Thank you for answering my question.

I have this "https://throttletek.com/747-400-boeing-throttle/ " , and for some reason, I can't map correct reversers properly. With FSUPIC I can, as I mentioned before I would rather use your software versus the other one. That's where my problem is. If you could give me some guidance on how to get it to work (step by step), I could try. Unfortunately, I'm out flying for another 4 days before I get home.

Thank you!

What aircraft are you trying to configure this for? That can be different for different planes in MSFS. And are those reverser levers actual joystick axis?

OK, so here is what I did with the default 747 real quick with two separate joystick levers:

1. One physical lever is assigned to "Throttle 1" from the "Select simulator axis" drop down. I have set Axis min to 0 and Axis max to 1. This lever only controls forward thrust, it can't go into reverse. The red triangle has been pulled entirely to the left side, and I've created a fairly large dead zone. The assignment is set to update the value "on change".

2. The second lever is assigned to the same variable, "Throttle 1", Axis min is set to -0.25 and Axis max is 0. This lever handles reverse thrust. The red triangle has been pulled entirely to the right side, and I've also created a fairly large dead zone. The assignment is set to update the value "on change" too.

With those opposite dead zones I make sure that the levers don't accidentally overlap. While this is easy enought to set up, it has a downside - whatever lever is moved last takes precendence. So you can go to full reverse at any time. This is usually not a problem when you have proper physical levers that lock the reverser. But if that is a concern, the same setup can be done with RPN scripts, like @touchdown84 has shown above.

And - this only works like this for the 747. Other planes require different approaches.

Edited April 24, 20224 yr by Lorby_SI

Thank you so much! I'll give it a try when home.

I know this is an old thread but it seems some changes have been made that allows for Bvar's to be mapped to axes and buttons directly.

I was creating a new profile for turboprops and was strugling to get the condition lever working properly when I stumbled onto this thread.
But instead of using Lvar's and a script I was able to map an axis to the variable "B:Fuel_1_Condition_Lever_Set". when set with a range of 0 min and 2 max it seems to operate the condition lever quite well.

This avoids having to map BVars to LVars. The only thing I could not get working is to use the zone below my idle detent on my quadrant as cutoff so the whole lower 33% of the axis works as idle which is not perfect but fine for me at the moment.

7 hours ago, orchestra_nl said:

This avoids having to map BVars to LVars

That is correct, the LVar/BVar mapping feature is still there (you just never know...) but marked as "deprecated" in the AAO menu. Please make sure to always get the latest version of AAO in the shop where you bought it!

If you have axis like the condition lever, that actually isn't an axis at all (it only has the three values 0,1,2 and nothing in between), set the "Rounding" attribute of the axis to "int" in AAO (to make sure that only those values are sent and the MSFS logic doesn't get confused)

7 hours ago, orchestra_nl said:

The only thing I could not get working is to use the zone below my idle detent on my quadrant as cutoff so the whole lower 33% of the axis works as idle which is not perfect but fine for me at the moment.

You mean on the condition lever? Or the throttle?

3 hours ago, Lorby_SI said:

If you have axis like the condition lever, that actually isn't an axis at all (it only has the three values 0,1,2 and nothing in between), set the "Rounding" attribute of the axis to "int" in AAO (to make sure that only those values are sent and the MSFS logic doesn't get confused)

I know, in reality a condition lever is more like a three-way fuel switch (cutoff, restricted fuel flow and unrestricted fuel flow). It is not actually an axis but the lever often look like one so if you have a spare mixture axis (which you would not need in a turboprop) it is not illogical to try and use it to set the fuel condition.

I did set the rounding to "int", i forgot to mention it

3 hours ago, Lorby_SI said:

You mean on the condition lever? Or the throttle?

I meant condition lever. the axis on my controller has a detent at the bottom and a small zone that acts as a button below it. It might feel a bit more realistic if "0" would be sent to MSFS by the button, and the axis just sents a '1' or '2', depending on its position.
It would be nice if an axis could be divided into zones and have each zone sent a specific value but I don't think this is possible yet, at least not through the interface.
Off course with scripts anything is possible:

I am thinking of a script that takes the value of the axis and sends 0-50% as '1' to the Bvar, and 51-100% as '1'. Perhaps 0-30 and 70-100 are better values, it creates a big deadzone in the middle. The cutoff value '0' could then be sent by the virtual button, perhaps with 'o' as key press and '1'  as key up (when the lever is moved out of the detentzone).
That would be relatively easy to create I think.

15 minutes ago, orchestra_nl said:

It might feel a bit more realistic if "0" would be sent to MSFS by the button, and the axis just sents a '1' or '2', depending on its position.

Set Axis Min to 1 and Axis Max to 2? That this is all that the axis does.

Or maybe use software detents to enforce it? AAO software detents are probably the closest thing to your "zones"

You may have to add the "button" as a combo button to the axis, with "suppress..." active. Then actuating the button automatically disables the axis - at least in theory...

Edited October 16, 20232 yr by Lorby_SI

45 minutes ago, orchestra_nl said:

I meant condition lever. the axis on my controller has a detent at the bottom and a small zone that acts as a button below it. It might feel a bit more realistic if "0" would be sent to MSFS by the button, and the axis just sents a '1' or '2', depending on its position.
It would be nice if an axis could be divided into zones and have each zone sent a specific value but I don't think this is possible yet, at least not through the interface.

OK, I just tried my idea on the C208 with a Honeycomb Bravo and it worked fine

1. Axis assigment

I am using the MSFS InputEvent "FUEL_1_Condition_Lever" but those currently only work when you are running MSFS in developer mode (that is an official bug in MSFS). BVar should work the same way though, except that the value range might be reversed.
Axis Min = 0, Axis Max = 1, Rounding Int, Reversed
Combo button set to the button action of the physical lever, with "suppress axis" checked ON.

2. Button assignment

Same input event with value 2 dialled in the box, assigned to the button action of the lever.

What happens is, that the axis part of the lever only switches the condition lever between middle and upper position. When I pull it into the detent, the axis is disabled and the lever is set to cutoff.
 

Edited October 16, 20232 yr by Lorby_SI

Thanks for your great help. Your suggestion also gave me more insight in how AAO works.

The "supress axis" option is great, never new this would come in handy. I was wondering how to avoid the two controls fighting over the same variable but this solves it.

I got it to work using Bvars since I could not find the InputEvent "FUEL_1_Condition_Lever" in the list. At first I thought it wasn't working until I discovered that contrary to my logic, '0' seems to be high idle and '2' is cutoff in MSFS.

For step 2 "button assignment" I had to create a custom event since for buttons there is no way to input a variable directly. For the Key Down event I used the value "2" and I also added a Key Up event with the value "1" so the fuel condition is set to low idle as soon as the lever is moved out of the detent.

Too bad the SDK is still a bit of a mess. This variable is not even listed in the SDK! It would save us a lot of work if developers could use the same variables for their products as long as their function is the same. We could more easily use the same profile for multiple aircraft.

3 hours ago, Lorby_SI said:

AAO software detents are probably the closest thing to your "zones"

A bit, but these will only hold the current axis value until the lever is moved out of the zone. You cannot assign a (custom) event or different value as you can do with a button AFAIK.
Perhaps it is possible to assign virtual buttons to these software detents which can be configured as buttons, but I think that with scripts it is already possible to intercept the values and send whatever we want to MSFS, but it does require more work to write and test those.

Thanks again for your help and insight.

31 minutes ago, orchestra_nl said:

You cannot assign a (custom) event or different value as you can do with a button AFAIK.

You could do that using multiple assignments to the same lever with different ranges of operation (using the blue triangles)

31 minutes ago, orchestra_nl said:

This variable is not even listed in the SDK!

That is because LVars, BVars, HVars and InputEvents aren't part of the SDK. Every aircraft developer can just invent them as they see fit. And they do.

The InputEvents are only available when MSFS is run in Developer mode. They were supposed to be accessible with SU13. That is a bug that Asobo is already working on.

Edited October 16, 20232 yr by Lorby_SI

Thanks for the info . Been trying to assign Condition lever axis with cutoff using AAO since MSFS changed the Condition axis in SU8 or whatever. This also works well for twin Turbos also, ie BKSQ B350. Thanks.

"For step 2 "button assignment" I had to create a custom event since for buttons there is no way to input a variable directly. For the Key Down event I used the value "2" and I also added a Key Up event with the value "1" so the fuel condition is set to low idle as soon as the lever is moved out of the detent. "

Edited October 16, 20232 yr by Adrian123

2 hours ago, orchestra_nl said:

I had to create a custom event since for buttons there is no way to input a variable directly.

I know. The dialog is cluttered as it is, and is has that down/up vs short/long action switch in the background too. I often thought about adding a direct input, but have yet to find a way that will actually help instead of making the dialog even more confusing. The only help there is is the shortcut to the custom input dialog on the event selection. 

I was hoping for the InputEvents in SU13, as they can be read directly from MSFS and appear in the event list automatically. But that will have to wait until the next MSFS update - unless you run MSFS in developer mode, which, to my best knowledge, doesn't have any real downsides?

4 hours ago, Lorby_SI said:

unless you run MSFS in developer mode, which, to my best knowledge, doesn't have any real downsides?

The only downside I know of is the logbook not registering your flights in developer mode, but I am using Little Navmap for that anyway.

Agree about the inputevents, makes our lives a little easier. Hopefully they will fix it in su14 but preferably before that.