meierzwo

Set the Mixture to NONE. Not needed for this Plane and this Setting could effect the Engine Start. It does it for me with the Honeycomb Quadrant, but only for one Engine. I'm not familiar with your Throttle Quadrant, so I don't know about the Lever Zones and how the configure them in XP. A physical Detent on the Quadrant is a Stop before you can move on further. F.e. a Stop between Alpha and Beta Range. In the real Moo, that's the Point you have to lift the Levers to reach the Beta Zone. The second Stop is the Stop before reaching the Reverse Zone. The Honeycomb Bravo has no real Detent but Switches to activate Reverse, Emergency Stop or Fuel Cut Off. Using the Modern Throttle Configuration with the Bravo, a Response Curve as shown in the Docs and Auto-stop power levers at detent IS CHECKED, the 3D Lever in the Cockpit stops at Flight Idle. That's half the Way down for the physical Lever on the Bravo. Using the Power Lever Lift Command, the 3D Lever goes now into the Beta Zone when moving the physical Level down further. When reaching the Switches for Reverse, the 3D Lever is in Ground Idle. With moving the physical Lever full down, activating the Switches, Full Reveres is activated. The Throttle Setup for this Plane is a little bit tricky. I need a few Hours before I had all my Settings done. You have to try out the different Methods and Settings. If your Quadrant has no Detent, try to set the Lift Zone at around 50 Percent Hardware Travel. So if you move the physical Lever down, the 3D Lever should stop at least in the middle of the physical move when going into Idle and the Beta Zone. Not sure about the Reverse Handling with this Quadrant. If there is no Switch, you have to use a Button or Key for toggling Reverse.

I see, I see. You didn't read or understand the Instructions correctly. Your Throttle Setting is wrong. Do not use "Throttle", use "Throttle 5". And the Response Curve must be linear. This Plane uses a internal System for the Throttle to simulate the Lift Zone and the Beta Range. Throttle 5 is used for this System for your Single Lever Quadrant. And you have to assign a Button or Keyboard Key for the Throttle Lift. Read the Section "Single Paddle with Detent" carefully: In X-Plane's joystick setup dialog, assign your power lever to the THROTTLE_5 parameter. NOT THROTTLE Make sure you have NO RESPONSE CURVE, just simple 0 - 1 mapping. In the GUI prefs, make sure the option Auto-stop power levers at detent is UNCHECKED. In the GUI prefs, set the Hardware Power Detent Ratio to match the position of your real (or imagined) detent position. For example, if your real detent is at 25% of your lever movement, set the Power detent ratio to 0.25 If there is a Switch for Reverse at the Bottom of the Lever like the Honeycomb ones, search for "Reverse" and assign "Move both Power Levers to revers from Ground Idle" to that Switch. Use the "Modern" Setup with the Ghost Throttle. With the Ghost Throttle, you can see the physical Movements from your Throttle and the Movement from the Cockpit Throttle Quadrant. The Setup for this Plane is a little different and could be a little challenge.

What Throttle Axis is assigned in the Throttle Settings?

Did you click on "View the orders I have made" below MY ORDERS?

Confirm. Did run fine. Just did a short Flight with a Full "First Flight of the Day" Checklist.

I think this Error Report could be canceled. With the new Beta, the Error didn't appear anymore. It was a rare one anyway. It didn't appear at every Shutdown, even with using the G500.

Since it happens only at XP Shutdown, it's not a big Problem. And it only appears, if I use a Plane with the G500 Pluggin installed. No matter if I use the G500 with that Plane or a other Cockpit Version. If I use a Plane without the G500 Pluggin, no Crash of OpenGPWS at the Shutdown.

Latest G500 Suite installed, XP12 is latest Version. On shutting down XP12, XP needs a long time to do that and I have the Safe Mode Splash Screen after restarting XP12. No Crash Report from XP. In the Log.txt (attached): 2025-03-24 18:21:12 OpenGPWS[xplane.c:344]: OpenGPWS disabling --=={This application has crashed because of the plugin: }==-- If I disable the OpenGPWS Plugin via Plugin Admin in XP, the Shutdown and Restart from XP12 is normal. Any Idea, what causes that Crash? Heinz-Juergen Log.txt

I use it regularly in XP12. Weight and Balance is Fuel only, no Passenger or Cargo. There are a few Bugs (no Lights for the selected COM, Right Push Button on G500 Inop) that annoy me but Flight Performance seems pretty close within the Limits of the SIM. I use the Classic Cockpit Version without the Radar. I hope there will be a Fix. Maybe one Reason is the Status of XP12 with it's fast changes in short Time that could be a Nightmare if you are the one and only Developer for a Project. Latest announcement from the Developer was, that he was working on this and some Performance Updates. But that he needs Time for Testing and his Time is limited because of other Projects. But a short sign of Life would be nice. And maybe a small Fix for the COM Lights and the Push Button.

You will like her. I first purchased the Toga MU-2 for XP12 and, as Inibuilds showed up with the Mu for MSFS, I owned it too. What a Disappointment. No Comparison in Handling, Performance and System Depth to the Toga MU-2 in XP12. A complete different Level. Inibuilds can do it better but for only 10 Bucks, more seems not possible. I also prefer XP. I have MSFS2020 since the very first Pre-Alpha but lost Interest after the much to early Release to the Public.

You should give her a chance. I have the Honeycomb Alpha and Bravo Devices and the MFG Crosswind Pedals only. Base Functions on the Switches and the rest is done in the Cockpit. And I love this Plane. But you are right. A Update is needed for some Bugs.

There is only ind_lts_dim_on and ..._off under mu2b60. And the usual global Panel and Instruments Brightness Dim. Looks like there are no Dataref for the Knobs on the Overhead Panel.

I have no X-Touch Control but I assigned a few Functions to my Honeycomb Devices. Landing Lights are the normal X-Plane Command. Beacon, Strobe, Taxi and Nav are under /xscenery/mu2b60/... Same for all the Deicing Switches, the Wipers and a lot of more functions. Don't know if this will help. Heinz-Juergen

These are for Friction Control for the Throttle and Condition Levers. They are working. Move them full forward with the Mouse and you can't move the Levers anymore.

Since the use of Gizmo is removed for the Islander BN2T, will other Products follow? Is there a Overview, which Product uses Gizmo and which not? I have the Mitsubishi MU-2 (need Gizmo), the RSG 500 Suite (?) and the Douglas DC-3 V2 (?) in use. And if Gizmo is removed, will it be possible to use the Planes with Linux? I know, there is no Linux Installer yet, but I have two XP12 Installations, one with Windows and one with Linux and I would be very happy to see the MU-2 in my Linux Installation too, doing it the XPlane Style. Simple copy of the Windows Installation to Linux. I only use XPlane in Windows or Linux only, not both together.

They are not connected when you are in GPSS Mode, AFAIK. Looks normal. The only Glitch I see, the Course Needle and the 3 Digit Course Heading (268) are not synchronous. Happens sometimes on Power Up. Rotate the left Course Knob and they should go synchronous.

I use Reverse often for Push Back with Props set to Taxi. Did the Job. In the Landing shown above, I was in Flight Idle first and then set the Throttle to Reverse. Maybe this triggers some Governors before Reverse kicks in. Once it is established, it looks stable. Normally, Throttle is short above Flight Idle and I'm going to Reverse in one Motion after the Wheels touch the Runway. And it is from Flight Idle into Full Reverse with my Hardware. I don't know how the real Plane will handle this. But I think, it is similar as with Full Throttle at Take Off. If you set 100% Torque to fast, overshooting it, a Governor kicks in and reduces Torque. Could be the same in Reverse. Could take a few seconds before Prop Blade Position, RPM, EGT and Torque are stable. So this little fluctuations could be normal. But your Situation is not normal with Torque and EGT goes up and down.

ILS Approach at EDDG. No Brakes in use, only Reverse. Look at the Ghost Throttle to see the Positions.

I'm using Honeycombs Alpha and Bravo Equipment and MFG Crosswind Rudder Pedals. Taxi is sometimes very slow and I have the same experience as you, but it seems to be a problem with the Brakes, not fully released. I have this often after Landings, when leaving the Runway and changing Throttle and Props to Beta and Taxi. The Plane slows down, is very slow or stops. But giving Full Brakes, waiting a few seconds before releasing the Brakes solves the Problem mostly. And sometimes it is the Weather and the Terrain. I can stay in Beta just below Flight Idle most of the Time, a little bit more Prop is needed sometimes. It's not the Hardware, the Moo is the only Plane with this Taxi Problem. If the Keys "v" and "b" on the Keyboard are assigned with the Brakes (Default XP Setting), hitting them accidentally may also cause that Problem. Reverse is working for me. It kicks in late and could be more effective but I did not see any governor kick in. Torque and RPM is stable once Reverse is established. The Bravo Quadrant has only switches to apply Reverse. They are set to "Move left (right) power lever to reverse from ground idle". That seems to work. Prop Levers full forward for landings. And the Button Sounds and Animations seems okay on my Side.

Hmm, the Flightplan and the Leg you want to fly is active?

You are Welcome. I'm on my second "Journey around the World in 30 Days" now. Some long Trips with Refueling, some shorter ones.

Thanks for that but I have a copy of the POH already. Best regards Heinz-Juergen

The MU-2 has a pressurized Cabin. To adjust the Cabin Pressure look at the Copilots Side, the Instruments underneath the Yoke. At the Air Cond Panel there are Bleed Air at the left and Cabin Temperature at the right. Temperature is on Auto. In XP, Passengers couldn't complain. The rest of the Controls on the Air Cond Panel are in Default Position. For Take Off, Engine Start and Shutdown, set Bleed Air to Off. After Take Off and in stable Climb, set Bleed Air to Both. In case of a lost Engine, set Bleed Air to the running Engine. You need Bleed Air On for the Cabin Pressure. The Instrument in the Middle is the Control for the Cabin Pressure. With the Cabin Alt Knob on the right Side, you set your Cabin Altitude. If you go over 12000 feet, set your Cabin Pressure to 10000. The Instruments on the right shows your Cabin Pressure, the Difference between Cabin and Outside Pressure and how fast the Cabin Pressure is changing if you set a new Pressure. For Example. My longer Flights are mostly at a Altitude of 15000 Feet. Bleed Air is Off until I reach a Altitude between 3000 and 5000 Feet. You can switch it On earlier but for Take Off, you will Full Power. Now I also set the Cabin Pressure to 10000 Feet. That's all. For Descent, I slowly set the Cabin Pressure back after reaching 10000 Feet. Set it at least to 1000 Feet above Airport Altitude. Before reaching Final Approach, I depressurize the Cabin - Cabin Altitude to 0. It may not be the correct Procedure for real Life Operations, but my Passengers are very brave and silent. If you forget to set Cabin Pressure and going to High, there will be a Master Caution Warning and an Indication Light at the Annunciation Panel.

Yes, makes sense. If I purchase it, I think it will be very useful for the Com Settings too. Dialing in the Frequencies with the Mouse even on the Pop Out Screen is not what I like very much. And I didn't count how often I had the left Rotary Switch in the wrong Position when trying to change Heading, Altitude or VS with the Bravo. I painted the small Indicator on the Knob in white but it happens recently. And changing the Values with the right Rotary Knob has a tendency to overshoot. Do you use the Octavi with the plug-in only or with MobiFlight too?

Same here. My favorite Plane in XP12. There are a few Bugs but nothing that made it unusable. cfirandy. I also use Alpha and Bravo and was thinking about the Octavi IFR-1. What Functions you are using with the Octavi IFR-1? AP Functions are almost done with the Bravo.