Left vs right throttle discrepancy
-
@Black-Square no failures and engines at 100%. They are fine on the ground, and then usually start to require differential throttle settings the longer I fly. I usually do about 45 minute to 1 hour flights when it becomes noticeable. Torque becomes about 10% different, ITT maybe 50 degrees or so. And it’s always the left engine with the lower values. Once I land they are both “synced” again. Both throttle inputs are calibrated the same settings (using Honeycomb bravo).
-
ok, longer flight now and have the same issue. Both engines 100% shape. Every some time TRQ of left engine going down a little bit 10-20 Lb-ft, so I need put left forward to have same TRQ values for both engines.
Second wired issue, fuel flow in Engine trend monitor and Garmin TDS have different values of fuel flow, endurance etc.
-
I observed this too. Left engine gauge shows always 10~20lb/ft lower numbers.
I believe my hardware throttles are calibrated perfectly.
But to be sure, I'll try switching throttle 1 & 2 axis and also binding only one hardware axis to both input axis before I report again. -
I am one of those that only has a single throttle, a Saitek X52 that I've had for well over a decade. I wonder if an option can be made to sync the props in the efb for us single throttle guys. I do understand and appreciate the realism of different throttles and I would totally do it if I had dual throttles, but maybe think about a prop sync option. Thank you. Love my Turbine Duke.
-
There seems to be a little confusion in this thread despite my last message. Let me explain what's going on here in two different ways:
What the simulation sees: Both engines perform identically for a given throttle setting.
What you see: I don't like aircraft (especially ones with digital readouts), where it's too obvious that both engines are digital facsimiles that perform identically under all conditions. For this reason, I program slight variations in the variables that affect apparent engine performance, so that they appear to be real machines. All engines parameters will not match between two engines, even if you carefully match one parameter by manipulating the power lever. For example, two PT6 engines on the same airplane can burn several GPH more or less fuel than the other at the same torque setting.
How you should respond: Users with dual throttle inputs may adjust their power settings to best synchronize whichever engine parameters they like. This will have a negligible effect on the aerodynamic simulation. Users with one throttle input should not worry about perfectly synchronized engines, because the underlying simulation is always perfectly synchronized. Allowing the higher torque or ITT value of the two engines to be the limiting factor on the combined throttle input is also not unrealistic, as this is how the aircraft is operated during critical phases of flight in the real world, when the pilot is moving the power levers together and not focusing on small differences between the two engines.
I hope this clears some things up. Please let me know if you have more questions or suggestions.
-
I’m still not entirely clear. Maybe I can frame this in terms of a yes/no question. As has been reported by a few users, the left engine torque and ITT becomes lower than the right engine after a certain time in flight, at the same throttle setting. In order to equalize the left engine torque/ITT with the right engine, the left engine throttle setting must be set higher than the right throttle. Is this expected behavior?
-
@Black-Square I wonder. Do you think you could randomize it a bit? Makes sometimes the left lower and sometimes the right lower. Is there an easy way to add a coin toss on startup to pick an engine to be different this flight?
-
I absolutely support the idea of slightly randomised airframes, but if that were possible then I would like each livery to have its own persistent randomisation (generated the first time it's flown), as it's unlikely that the underperforming engine would swap sides between two flights. I think that's a level that Black Square aircraft aren't looking to simulate (but I live in hope; aircraft persistency is the best thing since sliced bread).
What Nick is saying, if I understood correctly, is that both engines are always performing identically (for a given throttle setting), but the displays/readouts are slightly randomised, so they don't show 100% accurate values. This gives the illusion of slight variations which would be observed in real life. (Real life analogue to that would be the aircraft's sensors having variations between engines, even if the engines had the exact same values.)
Rather than fudging the readouts, it would be nice if MSFS had a randomisation parameter that could allow developers to assign a certain amount of variability to different aspects of the flight model. Imagine the support headaches it could cause though!
-
I had some experiment with my Thrustmaster Airbus TCA throttle quadrant.
- two in-sim throttles to one hardware throttle axis
1.1) both to left
1.2) both to right - cross-assignment for two in-sim throttles to two hardware throttle axis
2.1) left to right
2.2) right to left
In EVERY cases, I could ALWAYS see lower numbers for the left engine.
I thought it might have something to do with the inherent asymmetry in the Dukes IRL, like air conditioner etc.
But the statement below excluded that possibility:
@Black-Square said in Left vs right throttle discrepancy:What the simulation sees: Both engines perform identically for a given throttle setting.
So it was like:
@Black-Square said in Left vs right throttle discrepancy:I program slight variations in the variables that affect apparent engine performance, so that they appear to be real machines.
Now everything makes sense.
Then I wish that "slight variations in the variables" could be randomized or turned off, because it feels a bit weird to see those "variables" work as if they were "constant" like I observed. Especially if one had slightly uncalibrated throttle quadrant the apparent variation could be unrealistically exaggerated.
However randomizing those variables for every flight might feel unrealistic too.
How about making the "Repair Engine" button on the tablet to trigger the randomization? - two in-sim throttles to one hardware throttle axis
