tkyler

First Question....does the engine start when you use the mouse cursor to press the start button virtually? Second Question....do you use a hardware button to engage the starter? If so, what command have you mapped those buttons to? Finally, In the X-Plane "Data Output" section, search on "Mixture Setting" and output that to the screen with the "Show in Cockpit' checkbox. Same thing for "Igniter on/off" I'd like to see those two values during the engine start sequence, preferably while you're holding the starter button. TK

At the very least, you want to make sure you have the 2.0.2 update, which adjusted the engine torque at FI. With the power levers pulled back to Flight Idle on descent, what are the torque-meters reading? They should be approx 20% in 2.0.2. TK

your ignition switches are set to OFF in the above screenshot, those need to be in AUTO at least.

you may be able to tweak them with a response curve on those axis. I've certainly done this myself on my hardware (Precision Flight Controls...*cough...#anythingbut) TK

engine RPMs over 10%? 10% is the lightoff point and depending on the battery load or if you've attempted a previous start, the engines take a bit to get to the 10% point. This is one of the reasons I put the "charge batteries" preference in the GUI. For troubleshooting, consider hitting that button in the GUI to get maximum battery performance to get the engine over 10% as quick as possible. TK

That does sound like props still on the locks, though you did mention that you followed the procedure to remove them from the locks. When in ALPHA range and props off the locks, the torque meters should read about 15-17% at Flight idle and that should result in quite a bit of thrust and easily 10-20 knots taxi speed. The only way to be sure is to turn on X-Plane's 'data blocks' for thrust and/or prop pitch. Yes. There is a little blurb about why this is in the MU2 docs: specifically in the section titled "condition levers operation"....the paragraph beginning with: "For the most part....." I honestly couldn't say whats going on without looking at a bunch of dataref values simultaneously. ...i.e. braking values, prop pitch, thrust values, etc. TK

it does, but i'm starting to worry about too many options and 'band-aid' code as this seems to need yet another preference necessitating yet another GUI option and the more options, the more confusion to new users..... the more support and more documentation. I'll think through this. I don't want to make a quick change that results in even more documentation that folks won't read . But yea...I'll give it a think. TK

...given the checkbox "Auto stop power levers at detent", which you have checked, this is correct. This is MODERN behavior. What you are describing previously is LEGACY behavior, which does use the slash key. If you uncheck the "Auto stop power levers at detent", and then set your power detent ratio to zero (which you DO in the video), then you should get the legacy behavior where you bring your hardware all the way back...and the 3D throttles go to Flight idle...then you hit the slash key....and your levers should lift and then moving your hardware lever forward should move the levers backwards into BETA towards reverse. for LEGACY behavior, the upper and lower limits are not applicable.. For the update, the MODERN behavior is checked by default so that might be a bit confusing if you were previously set up for LEGACY. This is the 'furtherest' I've gone trying to accomodate a lot of differing preferences...as the Moo quadrant operation is a bit unique...and I apologize for some of these teething pains, but I do feel we're converging towards enough flexibility that once its understood and setup, it will accomodate most preferences. TK

What happens if you set your upper limit to 0.51 or 0.55 Dion? I certainly didn't program it with my REV axis checkbox checked....now that being said, some hardware IS indeed differing in these axis ranges and that is the very reason the REV checkbox exists....and if it turns out you need to check REV and I don't with my hardware, then who says who's hardware "gets the normal behavior", etc. If my hardware axis is backwards, I simply check "Rev axis" and move on. I'm out of town and do not have my hardware for testing TK

http://togasim.com/mu2docs/setup/hardware_setup.html#single-paddle-no-detent

Please post hardware axis settings, GUI prefs and response curves if still having issues. All 3 of these config areas affect the throttle behavior. TK

A valid radio navaid needs to be "received" by a navigation receiver. The NAV button does not work with GPS. TK

My favorite example to give -TK

Things have changed slightly for the better; however, I don't recall making any changes to the LEGACY behavior, which sounds like what you want, but you didn't specify so I'll just start guessing. When auto-detent is unchecked, then the hardware detent ratio comes into play. If its zero, then you desire "LEGACY" push for reverse behavior and use the toggle/reverse/beta commands to change modes between ALPHA/BETA. The levers have to be near flight idle for this toggle command to take effect and switch the lever directions....and this means your response curves come into play if you have any (which you should not for LEGACY behavior) . If its a non-zero value for hardware detent ratio, then you desired "aft is reverse, forward is power" behavior, just like the real thing...with the detent ratio specifying your desired 'detent' point on your hardware. TK

Updated Docs. Bug Tracker for the 2.0.2 is final. New section in the hardware setup on the GHOST THROTTLE feature...and a little blurb there for Bravo owners. Some new commands added also. Bug Tracker is best place to get the info. -TomK

You're welcome! Prepping 2.0.2 patch for deployment even as we speak. -TK

TODO list is done for 2.0.2 patch. Checking everything now and should push out an update pretty quick. -TK

all these items have been addressed for 2.0.2 patch...forthcoming. TK

hope this plays. last one was encoded wrong. this is H.264. In this video, When moving the levers UP in BETA...I am "holding down" the lift levers command to illustrate how it only lifts and "captures" when in the zone. (though I screwed up, leaving the pref window "in focus" for a bit before I figured it out.) levers.mp4

The graphic below shows an "upper limit" and "lower limit" value for users to tweak their tolerance zone for when they want to lift the levers. These are not %, but a ratio from 0 to 1, with flight idle point being at 0.5. So a nominal tolerance zone might be a lower limit of 0.45 and an upper limit of 0.6. Of course I'll document this before the update. -TK

so FYI....if my logic with my planned fix is flawed. let me know if I'm missing something. When the "lift both power levers" command is executed....then I test for 3 hardware axis values.....the single throttle, the left and the right. and if ANY of these axes are wihtin the tolerance zone, then the lift both command will lift both levers. Previously, I only checked the single paddle (THROTTLE) hardware axis...since the "both" was originally intended for just single throttle paddles. Now that's not the case. This should allow you to hit the one button on the Bravo and move either lever.

I was a bit on the fence on this one....as I can make an argument for some folks wanting "full reverse" with the lift-command; however, I think a simpler 'tolerance preference" might do the trick. A percentage value, defaulting to 0.1, which would would be a zone +10% above Flight Idle where you can lift the lever. If you want to lift it any time you want to, then just set that to 1, etc. I'm not biasing the zone up or down Its symmetrical about the Flight Idle position -TK

If I hadn't messed it up in the first place, we wouldn't be here at all....so I'll take the hit. The power levers are getting a thorough looking over...and the ghost throttle feature is forthcoming, which is also helpful in getting the throttles tuned for the typical use cases. TK

OpenGPWS crashes X-Plane on the mac the majority of times the plane is unloaded. I'll look at these again at some point...probably in V12. TK

can do Jerry.....never ceases to amaze me the combination of uses folks can use. TK