I bought this program as it seems to have some helpful functionality (and because it was annoying having to restart it every 20 minutes while I test fly), but unfortunately there are some game breaking issues I am facing.

I use the T.Flight Hotas on MSFS. All axes on MSFS are turned off, except rudder.

With the PMDG 737, I can't flare the airplane on landing because elevator inputs quit responding at ~20ft AGL.

When I try to hold brakes using the paddle axes (I have it set to the right side being a brake axis) it will quit holding brakes after a second, or it will stay permanently applied (the axis are displaying in the program correctly but MSFS is not behaving that way).

Rudder is completely unusable when mapped in AAO as it is constantly snapping back to center. (This is the only axes I have set back to MSFS).

Please help? Every axis is set to their default, except what needed to be reversed and the brakes having their center point adjusted.

1 hour ago, nartbag said:

I bought this program as it seems to have some helpful functionality (and because it was annoying having to restart it every 20 minutes while I test fly), but unfortunately there are some game breaking issues I am facing.

These problems must have been the same when you tested it - so why did you buy it? The product description in the shop specifically says to test first and only buy when you are sure that it works as desired.

1 hour ago, nartbag said:

With the PMDG 737, I can't flare the airplane on landing because elevator inputs quit responding at ~20ft AGL.

Sounds strange. I don't seem to have these issues. Maybe make sure to create new assignments for every axis, don't change existing ones (to avoid Axis Min/Max issues). 
Why are there 4 thrust lever assignments for a 2 engine aircraft?

This is my own config - there are a few things that are only there for testing purposes, but the main controls should be in here:

Edited January 22, 20233 yr by Lorby_SI

Another idea about the elevator problem - maybe try the AXIS_ELEVATOR_SET event instead. I wouldn't rule out the possiblilty the the PMDG logic does "something" with the elevator simulator variable at this point. I have trouble testing the flare, on my devel system MSFS is not stable enough to make it that far.

11 hours ago, Lorby_SI said:

These problems must have been the same when you tested it - so why did you buy it? The product description in the shop specifically says to test first and only buy when you are sure that it works as desired.

It's barely $20, not a huge deal to me. Given the fanfare of this program and how nice it works otherwise (very responsive controls in the air) I didn't intend on giving up getting it working. 

11 hours ago, Lorby_SI said:

Maybe make sure to create new assignments for every axis, don't change existing ones (to avoid Axis Min/Max issues).

I'm not sure I understand what you mean by this. I am creating new assignments for each one by using the + button at the bottom, unless there's some duplicate button I haven't found.

11 hours ago, Lorby_SI said:

Why are there 4 thrust lever assignments for a 2 engine aircraft?

This was more to get a base template to be copied to other aircraft. I'll delete these and test.

11 hours ago, Lorby_SI said:

Another idea about the elevator problem - maybe try the AXIS_ELEVATOR_SET event instead. I wouldn't rule out the possibility the the PMDG logic does "something" with the elevator simulator variable at this point.

I did a test flight and this seems to have fixed the issue. The same worked for the rudder. Thanks!

The only other persisting issue I seem to have is when trying to use the paddle on the front of the throttle for progressive braking, but I think this is a limitation of the sim. I am trying to have it completely ignore 0-50% and use the remaining 50% of the axis to control (0-100) braking intensity so I don't have an all-or-nothing solution for brakes (i.e. landing aircraft without an autobrake). It appears to constantly be applying 50% brakes when the paddle is centered and I can see the braking animation moving when I depress it. The issue happens with both the event and the sim axis selection for left and right brakes.

This is what I am talking about when I refer to paddle:

15 hours ago, nartbag said:

I'm not sure I understand what you mean by this.

It is not unheard of that Axis Min and Axis Max values may be off when changing an existing axis assignment from variable to event to trigger or to something completely different. These values control how the "physical" axis input is mapped onto the item that is transmitted to the simulator.

15 hours ago, nartbag said:

The only other persisting issue I seem to have is when trying to use the paddle on the front of the throttle for progressive braking, but I think this is a limitation of the sim. I am trying to have it completely ignore 0-50% and use the remaining 50% of the axis to control (0-100) braking intensity so I don't have an all-or-nothing solution for brakes (i.e. landing aircraft without an autobrake). It appears to constantly be applying 50% brakes when the paddle is centered and I can see the braking animation moving when I depress it. The issue happens with both the event and the sim axis selection for left and right brakes.

This is what I am talking about when I refer to paddle:

Not sure, I've never looked at that one. How is that controlled? AVar, LVar, BVar? Is it an axis or button(s)?
 

Off the top of my head I would suggest either changing Axis Min/Max (if it is an aixs = with that you can limit the range of the axis that is transmitted to the sim) or use RPN scripting for these special purposes.

Edited January 23, 20233 yr by Lorby_SI

16 hours ago, nartbag said:

I did a test flight and this seems to have fixed the issue. The same worked for the rudder.

That is good to know, thank you!

14 hours ago, Lorby_SI said:

It is not unheard of that Axis Min and Axis Max values may be off when changing an existing axis assignment from variable to event to trigger or to something completely different. These values control how the "physical" axis input is mapped onto the item that is transmitted to the simulator.

Not sure, I've never looked at that one. How is that controlled? AVar, LVar, BVar? Is it an axis or button(s)?
 

Off the top of my head I would suggest either changing Axis Min/Max (if it is an aixs = with that you can limit the range of the axis that is transmitted to the sim) or use RPN scripting for these special purposes.

I'm not sure how to determine which var type it's using. If I manipulate it in the axis assignment window, the range is 16-bits. I've tried setting the axis min and max to 32768-65536, and adjusting the arrows in the main window, but it would still map the center as 50% braking, instead of the 0% I'm trying to get. Does this make sense?

Below is an example of the configuration. There would be two of these, one for each brake (left and right). The min/max are their defaults from AAO.