Jump to content

meierzwo

Members
  • Posts

    72
  • Joined

  • Last visited

  • Days Won

    4

meierzwo last won the day on February 27

meierzwo had the most liked content!

1 Follower

Profile Information

  • Gender
    Male
  • Location
    EDDG
  • Interests
    HAM Radio, Sim Flying

Recent Profile Visitors

701 profile views

meierzwo's Achievements

Enthusiast

Enthusiast (6/14)

  • Collaborator Rare
  • Dedicated Rare
  • Conversation Starter Rare
  • Reacting Well Rare
  • First Post Rare

Recent Badges

24

Reputation

  1. 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.
  2. 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.
  3. 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
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. 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
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. ILS Approach at EDDG. No Brakes in use, only Reverse. Look at the Ghost Throttle to see the Positions.
  14. 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.
  15. Hmm, the Flightplan and the Leg you want to fly is active?
×
×
  • Create New...