Throttle Manger LUA Reverse Ratio Values

[light_blue_yonder]

Hello guys, I recently started using the ThrottleManager.lua in P3DV4. The problem I found was that if the reverse ratio is set to the default value of "1", you will reach max reverse in your aircraft before your throttles reach 100% travel. This makes it a bit harder to physically feel how much reverse you are using, especially in powerful turboprops. While I understand that real reverse zones are shorter than forward thrust zones, I find that using 100% of the physical throttle travel for reverse is a more controlled feel for flight sim.

So I decided to work out exactly what the values are and put them here for anyone looking for the same experience. I will update it as I go along with different aircraft. All these values are tested on the Saitek Throttle Quadrant, but it *should* work with all throttles since it is a ratio value.

 

Each entry in the list will be in the format of "Name of aircraft" and [throttle reverse ratio value]

"FSLabs A32X" [1] *do not change this value. Instead, go to the MCDU and set your detents there.*

"PMDG 737NGXu" [0.372]

"PMDG 777X" [0.250]

"RealAir Turbine Duke V2" [0.259]

 

If you want to do this yourself, simply open throttle manager lua file and edit the value. If your physical throttle reaches max before the virtual reverser reaches max, increase this value; if the virtual reversers reach max before your physical throttle, decrease this value. It's not technical work, just trial and error.

P.S. If anyone knows how to make these values profile specific like joystick calibrations are, please do help me out.

Edited May 21, 2020 by light_blue_yonder

[Thomas Richter]

Hi,

Quote

P.S. If anyone knows how to make these values profile specific like joystick calibrations are, please do help me out.

just make copies of the file and name it to your needs, do the changes for the specific aircraft or series of aircrafts you want to use it for. Then use the method below, described in FSUIPC Advanced manual page 40 (see below).

Quote

Automatic running of Macros and Lua plugins
By some editing in the INI file, you can arrange for one or more Macros or Lua plugins to be executed, in order,
automatically whenever the current aircraft is changed (or, indeed, first loaded), or a specific named aircraft (or Profile)
is loaded.
This allows switches, offsets, and other things to be set specifically for an aircraft (or aircraft type, for Profiles) when it
is first loaded.
This is done by adding new sections to the INI file with the title{
[Auto]
or
[Auto.xxxx...]
where the xxxx part is the aircraft name, or part-name (as in Aircraft Specific sections), or a profile name when profiles
are being used.
These Auto sections thus parallel the Keys and Buttons sections -- the naming and selection follows the same system.
The generic [Auto] section is carried out for all aircraft changes whilst the specific ones are only applied to matching
aircraft or profile.
Each Auto section contains a series of numbered lines (1=..., 2=... etc) each of which is either a Lua command, or a
Macro call. For example:
[Auto.737]
1=Lua SetMyOffsets
2=737 OHD:Air Allbleeds
When Lua calls run a plug-in which doesn't self-terminate, the plug-in thread still running is killed automatically on an
aircraft/profile change.

Thomas

[light_blue_yonder]

49 minutes ago, Thomas Richter said:

just make copies of the file and name it to your needs, do the changes for the specific aircraft or series of aircrafts you want to use it for.

Thanks for the reply! I have done exactly that.

1. Renamed the file to ThrottleManagerPMDG777.lua

2. Add 

[Auto.B777]

1=Lua ThrottleManagerPMDG777

to the .ini file. (Yes, the profile name is B777)

3. Load up the 777, and it's not working. In fact, the LuaToggle for throttle manager is gone in the button assignments page.

Edit: I also made sure to change the name under the [LuaFiles]. Even using [Auto], the Lua does not function. The log shows that it does load, but there must be something inside the actual Lua file that is dependent on the file name.

Edited May 21, 2020 by light_blue_yonder

[Pete Dowson]

2 hours ago, light_blue_yonder said:

I also made sure to change the name under the [LuaFiles].

That's generally not a good idea. The [LuaFiles] section is maintained by FSUIPC and it would have added the Lua name when it saw it. It just wouldn't have deleted the old one.

The problem is that the name "ThrottleManagerPMDG777" exceeds the maximum length for a plug-in name. This is what it says on page 1 of the Lua Plug-ins document:

Note that the filename part (preceding the .lua filetype) can contain spaces and other characters
acceptable to Windows, but there is a limit of16 characters on that name

Pete

 

[light_blue_yonder]

23 hours ago, Pete Dowson said:

The problem is that the name "ThrottleManagerPMDG777" exceeds the maximum length for a plug-in name. This is what it says on page 1 of the Lua Plug-ins document:

Honestly, I'm blind. 🤦‍♂️ l was searching all over that document trying to find anything about processes that may be file name dependent. Thank you for pointing it out to me!

Also, I understand the automated process of the [LuaFiles] section. I only tried to manually set that value when leaving it alone didn't run the Lua file and then I noticed that it doesn't delete Lua files that no longer exist. Now that I know my problem, it all makes sense.