Jump to content

DaveVanB

Members
  • Posts

    8
  • Joined

  • Last visited

DaveVanB's Achievements

Rookie

Rookie (2/14)

  • First Post Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. Checking the box "Has beta/reverse dentents" seems to allow me to get the Beta range correctly, even though the detent on the hardware throttle is not in play. The only other change I made, which I don't believe was necessary, was to change to Cubic for the Interp Mode. Probably any of them would work. Thanks so much for your help Tom. Dave
  2. I thought it was the friction lock. Glad I'm not going crazy. I'm using the Honeycomb Bravo throttle quadrant. It has a detent at about 25% of the motion range, but the throttle movement above the detent moves the levers in the SIM all the way back. Thanks for the Response curve settings. Tinkering with that might very well fix my issue. I'll report back what I find. Dave
  3. Thanks for the explanation and video. I did read the manual and it could be something with the way my throttle quadrant is set up. I keep the Condition Lever at Taxi. I pull the throttle lever all the way back as depicted in the photo in the documentation, where it says it should be in reverse, but it still goes forward accelerating to above 35kts. I can pull it over the detent and to the very bottom and it does go into reverse and the Beta Lights go on. Moving back above the detent, the Beta lights go out. So, maybe, what's going on, is I'm not getting into "Beta Mode" with the Power lever. Is there a trick to get into Beta mode, besides just moving the Power levers back? Also, in the video of the real aircraft, I noticed the pilot using 2 hands to change the Condition levers to Min-Cruise while taxiing. He moves the Condition Levers with his left hand and did something with his right hand, but it's too dark to see what his right hand did. Dave
  4. Good news is, I couldn't reproduce the problem. The second engine started just fine...likely because the first engine was not in Beta mode. I tried to get the first engine into beta mode while not in reverse thrust mode, but couldn't. So starting went normally. I even tried with reverse thrust/beta mode on the first engine, but still able to start. I suspect I somehow got the engines into Beta mode without reverse thrust and that somehow caused the problem. I do wonder if minimum power/forward thrust should cause the aircraft to taxi in excess of 35 kts. Is there a setting I can tinker with to get less thrust at idle without going into reverse? I have the condition levers at minimum. Thanks, Dave
  5. Tom, Additional attempts yielded success. I believe the difference is I had the beta range light illuminated when I was having the problem. I then did the procedure to extinguish the Beta Range light on the first engine and the second engine started without killing the first one. Dave
  6. Tom, Thanks for the quick response. I am using the HoneyComb Throttle Quadrant and the on-screen levers are moving correctly with the hardware levers, so I don't think it's a hardware issue. Here's a screenshot right before I try to start the left engine with the right one running. I did confirm that pressing the left Yellow start button shut down the right engine. Thanks for your help, Dave
  7. Tom, Just got the V2 of the MU-2 and looking forward to flying. After starting the right engine, moving the start switch to LH Gnd Start and pressing the Yellow Start button, the right engine immediately quits. Same happens if I start the left engine first. Probably doing something wrong, but I'm following the checklist and v2 Stream by Jon Fly. If I reload the aircraft from the Developer menu, it has both engines started. Dave
  8. PERFECT!!!! Finally lights are visible at night! Wish I had seen this a year ago! Thanks Chris!!
×
×
  • Create New...