light_blue_yonder

Hello @John Dowson Thank you for the script! I will try it when I get back to my sim computer. I have been slowly troubleshooting what exactly caused the original problem. The only thing I've done so far to make that original problem come back is allowing FSUIPC's calibration page to process the axes. Once it is set to "Not processed" in the values field, everything works as intended both in FSUIPC and in P3D. If I double assign an axis like the "solution" to the original problem, it causes a conflict - as expected. So, in short, I really don't know what caused the original problem. Before my reinstallation, I even deleted the controls config files and let the sim rebuild a new one; that didn't work either. I guess if anyone else runs into the same problem, all the advice I can offer is a complete reinstall, unfortunately.

It is the latter option. I use that with the PMDG planes, but you are correct. The way Aerosoft does their calibration appears to only allow reverse thrust by holding a key down, rather than allowing a toggle to go into reverse. Although, just as an idea, would it be possible to have a Lua script where when the button is pressed, it changes the axis assignment from a throttle axis to a reverser axis? Basically pressing a button to reassign the axis on the fly. I guess it's probably more trouble than it's worth. Plus, I have not even tested if a dedicated reverser axis even operates the reversers on Aerosoft planes.

Hello John, It's not so much that I solved the issue, but more that the issue just went away with a full re-install. Right now, it seems like the throttles work correctly by using either the "Axis ThrottleN Set" or the "ThrottleN" in FSUIPC, as long as the calibration page leaves the axes as unprocessed. Basically, it doesn't matter if it's assigned using "Send to FS as normal axis" or "Send directly to FSUIPC calibration," as long as it's not calibrated in FSUIPC, it works. But that still leaves the problem with not having the Throttle Manager Lua working, since FSUIPC doesn't actually process those axes, so it's not possible to have analog reversers, only a "press and hold F2" solution.

This is the lua toggle. I believe that it relies on the FSUIPC Calibration by using an offset to "reverse" the axis readings. I don't have enough expertise to confirm that, but I do remember looking in the lua file. When I reinstall, I'll put in the Milviz King Air by itself and see the throttles work. If it STILL doesn't work, then I know it's a Milviz problem. If it works, I'll put in FSUIPC, but keep the P3D assignment only, and go from there.

Hi John, I have some new updates since I finally got some time to sit down in front of the sim today. I reinstalled the Airbus and CRJ just for the sake of it. Strangely enough, the throttles on both of those worked when I assign through P3D or "Axis ThrottleN Set" in FSUIPC. This means that I can't use the Lua for the reverse toggle that a community member created, but the throttles move and the engines respond correctly. The Milviz still has the same issue. At this point, I am doing a full reinstall and I'll report back here when I put the addons back one by one. I'll leave everything default as much as possible and see if I can finally track down the source of the problem. Just to reiterate: the original problem applies to both the throttle levers in the cockpit AND the engines. As in, the throttle levers in the sim do not move, the engine indications jump for a split second to wherever I move my physical lever then jump immediately back to idle. So it's definitely not just a throttle levers animation issue. Using the F1/F2/F3/F4 keys make the throttles behave as normal.

Hey John, I appreciate your dedication! It does not matter what CRJ. Every airplane in the CRJ Professional addon has the same problem. This is the current list of products I have this problem with: - CRJ Professional - Airbus 318/319 Professional (I don't have the 320/321) - Milviz King Air 350i The addons that do NOT have this problem no matter how hard I try to replicate it: - RealAir Turbine Duke v2 - PMDG 737 & 777 (only ones I own) - FSLabs A320 (only one I own) - A2A C172 (only one I own) Again, I genuinely suspect that this is not an FSUIPC issue. If it was an FSUIPC-only issue, I shouldn't have problems by assigning the axes only through P3D's menu. I have said the same on the P3D forums.

Yeah, my original post didn't have a good flow, but that is also a combination I've tried. I've basically tried every combination within FSUIPC, and between P3D and FSUIPC. The only way that works is the "deliberately conflicting" way.

Hello John, I have tried every combination. Including calibrating in the calibration page while using "Send directly to FSUIPC Calibration". And when you say "that doesn't sound right at all", I COMPLETELY agree. That's why I was so confused. It makes no sense that it only works when I purposefully do something that I KNOW is suppose to cause problems.

I have read the Aerosoft documentation. It did not help. In fact, if it was limited to an Aerosoft problem, I wouldn't have the same issue between the Airbus and the CRJ, let alone the same problem with Milviz. So I'm thinking that there must be some shared factor between those three that is causing a problem.

Hello Pete, I have NOT used the calibration page. What I meant was assigning the axis as "Send directly to FSUIPC Calibration", which has the setting for "ThrottleN". Using this method OR the "Axis ThrottleN Set" both result in the same problem. It is only when I set the throttle axis in P3D's menu, AND assign "ThrottleN" in FSUIPC, do the throttles work. Using either one of these does NOT work. Which is why this is confusing me so much. It only works when I intentionally use a setup that may cause problems. Also worth noting is that the propeller and mixture axes don't have this problem, and they work fine when assigned using literally any method.

Hello John, I've tried the two suggestions here, to no avail. However, I have observed a new behavior. If I set the "Axis ThrottleN Set" in FSUIPC and nowhere else, the throttle goes to the position I had the level in when I exited FSUIPC. Like, if I put it at 50%, when I exit FSUIPC by clicking "Cancel", the throttle jumps to that position but doesn't move in any way. This is replicated in Aerosoft products and the Milviz King Air. I have reached out to both developers, and neither was able to offer a solution. The driver's for the hardware is correct as far as I can tell.

Solution: The only thing that worked was a complete clean reinstall of P3D, unfortunately. I tried rebuilding the controls config files by deleting them and letting the sim create a new one, and that didn't work. After the reinstall, I can't replicate the problem anymore, so I'm still not sure what actually caused the issue. So I guess that, unfortunately, the only solution is a time-consuming full re-install. I was recommended by a user on the official LM forums to crosspost here, since the people looking through the forums here may be in a better position to help, even though this may not be a FSUIPC-specific issue: Hello all, I'm having a very weird problem with separate throttle axes. This problem happens when assigning axes through P3D or FSUIPC. In a select few aircrafts, I can move the throttle fine when mapping one axis of my Saitek throttle quadrant to "Throttle axis", and it will move both throttles in the aircraft. But if I assign two axis each to "Throttle 1 axis" and "Throttle 2 axis", neither of them moves the throttles in the aircraft. I can get a response, but it seems like the input jumps up briefly to the position of the throttle before returning to idle. I believe they use the same type of throttle management (i.e. via SimConnect), but I have no idea if this is the cause or not. I have tried reinstalling SimConnect, but had the same problem. I originally thought this was an Aerosoft problem, since I had this issue in their A32X and CRJ. I recently got myself the Milviz King Air, and ran into the same issue. It seems like aircrafts that use a specific way of interacting with the throttles are having problem. I have no problems with the FSLabs A320, PMDG, and RealAir stuff. I have tried DirectInput and RawInput with no effect. Since this appears on some aircrafts but not others, and appears across aircrafts made by different developers, I'm suspecting that the issue stems from something in P3D5. Has anyone seen or heard of anything similar? Edit: something new I just discovered. I have to assign the same axis to the "Throttle 1 axis" in P3D, AND assign the "Throttle1" in FSUIPC calibration to get the axis to work. Assigning either one by themselves does not work. This has now become even more confusing.

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.

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.

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.