Piston & Turbine Dukes

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?

Shameless bump for this ongoing issue. Fuel state saving has never worked for me (mainly flying the Grand Duke). For non AAO users, here's a simple utility that can save fuel state, trim position, radio frequencies and more. It can even save your location so you can move your plane to the exact spot it was parked at (which may not be an actual parking spot on the airfield): https://flightsim.to/file/26490/aircraftstate/343557 It can auto-save the state when you shutdown the aircraft. Once you've loaded up the sim another day, you can 'send data' to the sim to restore most of your aircraft's state (which works for the Duke's fuel load).

Just adding to this thread to confirm it's still an issue. I've been meaning to post about it for a while but kept forgetting. I have tried going to the modern control mode a few times over the last four years of MSFS, but always end up going back to legacy (and often with tooltips disabled altogether). Two issues to solve here, I believe: Clickspot has the wrong cursor for 'open' action Clickspot is too small - it's very difficult to get the mouse in the correct place ('close' clickspot is bigger) Hope to see this addressed in a future update!

This aircraft is certainly a thing of beauty in how it's been implemented in the simulator. Sometimes, I get a bit of an unnatural break or volume-jump in the sound during startup, when one sound stops and another kicks in (which is more akin to older simulators where the audio was much simpler), but it's not all the time. Not sure why. There is one developer that maybe just has the edge in the natural-sounding/dynamic startup, but we really have it so good these days thanks to the cream of the crop of add-on developers, that we have little to complain about. Yet still we keep asking for more details and depth...

Haha! No problem! I just fly with the plain white livery until my favourite one gets fixed. Only had the plane for a week (a busy one) but already have over ten hours on the Hobbs. Definitely on my Top5. Also always nice to see a developer who cares about his/her product and customer.

After doing the flight a couple of times, I think it's the wind throwing me off. GPS compensates for the wind and it set my heading for 66 degrees. If I set for 63 degrees, I get pushed to one side in a cross wind. looks like the KNS can't compensate for the cross wind either, I guess.

Not to necro an old post but if you're talking about how to file on vatsim. The equipment code I recently found is /I, RNAV with no GNSS and no RVSM. It's similar to /W but you don't even got an inertial reference system. As for waypoints, file the points you want to fly to, to connect your start and end airports, and file those points. Make sure they're all inside the range of a nearby VOR and manually select each waypoint as you pass over them. KNS navigation is essentially just like vor nav except anyplace near a VOR can be used and you don't need to zigzag from one VOR to another.

Seems like a reasonable compromise.

And it's your attention and appreciation for these details that makes it worth while for me to implement them! Thank you for your message

@Hartmannx Have you checked fuses? Is there any failures in an EFB?

Here is my setting of the cowl flaps on SPAD.neXt for X-Touch mini. Show the "close left" action, the same is for the right and for open. [image: 213b441a-c304-4f12-a689-6ed3b3ca8b76.jpg] The action is as follow: The condition is Battery ON. On pressing short and releasing the button, the cowl flap begin to close, the button light blink, after 16 seconds, the flap is just closed and the button light remain on.