Jump to content

meierzwo

Members
 View Profile  See their activity

  • Posts

    71

  • Joined

  • Last visited

  • Days Won

    4

 Content Type 

Everything posted by meierzwo

  1. meierzwo
    Yes, it's working again. TNX.
  2. meierzwo
    And here is the complete Log.txt Log.txt
  3. meierzwo
    Dark Red on Dark Grey is hard to read. From the Log.txt after a Clear & Reboot in the Gizmo64 Console: 0:03:20.656 G64: core: Run: [OnBeforeReboot] 0:03:20.656 G64: debug: --- -- --- -- --- -- --- -- --- -- Firmware Reboot -- --- -- --- -- --- -- --- -- --- -- --- 0:03:20.660 G64: core: curl_easy_init() provided by:[F:\X-Plane 12\Resources\plugins\Gizmo64.plugin\win_x64\libcurl.dll] 0:03:20.666 G64: core: Boot Count: 3 0:03:20.667 G64: core: OpenAL: Shared OpenAL context.. 0:03:20.669 G64: debug: Firmware v21.03.20.0220 0:03:20.677 G64: debug: gxt: AutoLoading.. 0:03:20.677 G64: debug: gxt.load: Console 0:03:20.678 G64: debug: gxt.load: ToolTray 0:03:20.678 G64: debug: gxt.load: Mute 0:03:20.678 G64: debug: gxt.load: Preferences 0:03:20.679 G64: debug: gxt.load: RebootButton 0:03:20.679 G64: debug: gxt.load: GateKeeper 0:03:20.680 G64: debug: GK: Load license from disk.. 0:03:20.680 G64: debug: GK: License is good. 0:03:20.681 G64: debug: GK: IPC v21.03.18 loaded. 0:03:20.681 G64: debug: gxt.load: MAXX_RWC 0:03:20.681 G64: debug: gxt.load: LuaGC 0:03:20.681 G64: debug: gxt.load: Shell 0:03:20.682 G64: debug: gxt.load: Stats 0:03:20.682 G64: debug: gxt: Completed AutoLoad. 0:03:20.682 G64: debug: firmware_init.lua completed. 0:03:20.682 G64: core: Run: [OnKickStart] 0:03:20.682 G64: debug: KS: Gen 2 loader.. 0:03:20.865 G64: debug: GK: License is good. 0:03:20.865 G64: debug: KS: End OnKickStart.. 0:03:20.865 G64: debug: -------------------------------------------------- 0:03:20.865 G64: core: Register Draw Call: OnDraw_Windows 0:03:20.865 G64: core: Alias: OnDraw_Windows_Toast 0:03:20.865 G64: core: Alias: OnDraw_Windows_ShardTasks 0:03:20.865 G64: core: Alias: OnDraw_Windows_ToolTray 0:03:20.865 G64: core: Alias: OnDraw_Windows_MuteSymbol 0:03:20.865 G64: core: X-P Lua Memory Stats: 0:03:20.865 G64: core: Max Used: 4.160 MiB 4362092 B 0:03:20.865 G64: core: In Use: 4.154 MiB 4355922 B 0:03:20.865 G64: core: Gizmo: 4.154 MiB 4355922 B 0:03:20.865 G64: core: Delta: 0.000 MiB 0 B 0:03:20.866 G64: core: Run: [OnBoot] 0:03:20.866 G64: debug: GK: Auto license update is on. 0:03:20.866 G64: debug: GK: License days remaining: 14.99 - No update required. 0:03:20.866 G64: debug: GK: Update required when <= 2.00 days. 0:03:20.866 G64: debug: :------------------------------------------------------: 0:03:20.866 G64: debug: xscenery: Load mu2b60 Scripts - vnil 0:03:20.866 G64: debug: xscenery: Load mu2b60 Hot Fix - nil 0:03:20.866 G64: debug: :------------------------------------------------------: 0:03:20.867 G64: core: Run: [OnFirstFrame] 0:03:23.251 G64: error: http API call_back: function name: : sportys_contest_state: [string "core_utilities/xsLib_eventCallbacks.lua.ra1"]:262: [string "<!DOCTYPE html><html><head><script>window.onl..."]:1: unexpected symbol near '<' 0:03:23.251 G64: core: Run: [OnError]
  4. meierzwo
    Restored a Backup of the Plane but the Error stays. It's only with the Mu. All other Planes from X-Aviation have no Error Message with the Gizmo Plugin. I can use the Mu and renewing the License did work too.
  5. meierzwo
    Suddenly I get this Error Message from the Gizmo Plugin with 12.10B2. But first since today. Yesterday everything was okay
  6. meierzwo
    Before 12.10, Oil Temperature stays in the Yellow on Ground Ops and reaches Green only in Flight after Take Off. With 12.10 B2, Oil Temperature now quickly reaches the Red Zone and above in Ground Idle and stays there in most Parts of the Flight. Did a Flight at 15000 Feet with 80% Torque, 98% RPM and Oil Temperature was at the End of the Scale. It goes into Green after reducing Torque for Decent but was always very close to the red Mark. Fuel Flow seems also a little bit higher than before. Looks like LR did some changes with this new Beta.
  7. meierzwo
    MU-2 Preferences (from the Gizmo Plugin): Check Manips with Hardware
  8. meierzwo
    So, that's strange. I can't move the Throttle Levers into the Max Reverse Position. Even if I delete all Bindings for my Hardware Throttle Quadrant. The Levers stuck at Idle. Edit. Found it. The Condition Levers had to be out off Fuel Cut Off.
  9. meierzwo
    Is Max Reverse for the Throttle Leavers not implemented?
  10. meierzwo
    Okay. But you should be able to move the Prop Levers in the Cockpit with the Mouse as described in the Manual. No other Bindings to Props anywhere? If not, it's Time for the Developer to have a look on this. Anyway. Only having a single Lever Setup for this Plane may not be the best choice with all its workload. It's okay with Jets or single Engine GA but if you fly Planes with more than one Engine and you have to fiddle around with Throttle, Prop and Condition Settings all the Time, its Time to think about a Throttle Quadrant with at least 3 Axis as a minimum like a Logitech Throttle Quadrant.
  11. meierzwo
    As the Developer described in the Manual, after doing changes with Axis it is necessary to start a new Flight. All Joystick Axis will be scanned at at a new Flight so maybe some changes will not be recognize correctly until the new Flight.
  12. meierzwo
    Prop 5? Throttle Axis with one Lever should be set to Throttle 5.
  13. meierzwo
    Maybe a misconfiguration with the Bravo. Lever 1 and Lever 2 are set to Throttle 3 and 4. Lever 3 and Lever 4 (the blue ones) are set to Prop 1 and Prop 2 - these are the Condition/Prop Levers in the Cockpit. Lever 5 and Lever 6 (the red ones) are unused and set to None. In other Turbo Props, these are the Condition Levers. But not in the Mu-2. See this Thread too.
  14. meierzwo
    What's your Hardware Setup/Joystick Configuration? You can't move the condition (Prop) Lever even not with the Mouse in the Cockpit?
  15. meierzwo
    Do you mean in the Cockpit? Overhead Panel, Left Side, Lower Switch named Wipers. If you want them on a Switch on the Bravo: turn wipers on and turn wipers off.
  16. meierzwo
    Glade to hear you got it to work. Yes, Madame Moo is a challenging Bird and wants your full attention. Hardware Setup and Flying is not on the easy side. But a lot of Fun. For Pitch Control, it is a good Idea to experiment with the Response Curve. Linear could be a little bit to much of oscillating Ups and Downs. My Landings are still on the Bad Side, too. Reverse kicks in a little late. But if you are below the Throttle Detent of the Bravo in the lowest Position, the Cockpit Throttle Levers should be down in the Reverse Position.
  17. meierzwo
    You have done a new Joystick Profile for the Moo? Lever 1 and 2 are assigned to Throttle 3 and 4? Throttle Button 3 and 4 assigned to: "Move left (right) lever to reverse from ground Idle." Prop Buttons 5 and 6: "Move left (right) condition lever to EMER STOP." Response Curve for both Throttle Levers done as described in the Manual? See attached Picture. You have to add a Button or Keyboard Command for Lifting up the Levers to reach the Beta Range. I use a Button on my Alpha Yoke. The Key or Button must be assigned to: "Lifts both power levers for dual level hardware." Next are the Mu-2 Preferences from the Gizmo Plugin. Go into the Cockpit and move the Mouse to the upper right Side of the Screen until the Gizmo Menu appears and click on the Mitsubishi Logo. We will use the "Ghost Throttle" Settings and the upper and lower Power Lever Settings. Look at the attached Picture of my Settings. I use the Bravo with this Settings. Watch at the Ghost Throttle in the Cockpit. Set it to always On for the first Time. You see the real Movement from the Hardware Throttle and the Lever Position in the Cockpit. On Full Throttle, when moving the Levers down, the Cockpit Position will stop at Flight Idle. That will be somewhere in the Middle of the Hardware Position. You can move the Hardware Throttle down and you will see this with the Ghost Throttle, but the Cockpit Position will stay at Flight Idle. In the real Moo, you have to lift up the Levers for reaching the Beta Range. For simulating this Lift up, the assigned Lift Button is needed. Go with the Throttle slight above Flight Idle and Press and Hold the Button. You will here a clicking Sound and now you can move the the Throttle into the Beta Range. You can see this with the Ghost Throttle. Both Levers are now going down simultaneously.
  18. meierzwo
    Hmm, did a Flight around Sint Maarten this Morning at 20.000 Feet. Torque at 66% with Throttle full forward. Props at 98%. Airspeed around 200 knots. Fuel Flow was at 240 Lbs/Hr. Realistic Data?
  19. meierzwo
    XP 12.08.03. Some Changes with Beta 3. Main Tank could be used now. Did a Start only with Main. But Tip Tanks still feed the Main, not the Outer. But I did not see any Overloading of Main anymore. So, Tip Tanks are filling up the Main very Quick until Main is on Full Capacity. If Tip is empty and Main not Full, the Outer Tanks took over and filling up the the Main. I must say, I did not watch the Behavior before. Fuel is on Auto. Tip filling up the Main quick if it is not Full, Outer take over if Main is still not Full. Is that the correct Behavior? Edit. Just studied the Fuel System. Seems to be correct in this way and the "Bug" from Beta2 is solved. I always fly with full Main Tanks.
  20. meierzwo
    Jepp, it's broken. Doing a Flight with max Fuel Capacity in all Tanks. Starting the Engines with Main Only, then switching to Auto and watching the Fuel Indicators in Flight. Tip Tanks are draining and Main is raising up. Tip Tanks reaching the Level from the Outer Tanks and now both Systems are Draining. Main still raising up. Tip and Outer Tanks running Dry and the Engines are out. Switching Auto Fuel System Off and Restarting the Engines didn't work because Main Tank is not used. Next Test. Only Fuel in Main. Auto Fuel System Off, Outer and Tip Tanks with no Fuel. Starting the Engines did work but after a Minute, they Shut Down. Main Tank is not used for Feeding the Engines, only the Wing Tanks, but the Wing Tanks still feed up the Main Tank over the Limit. Next. Fuel in Main and Outer, but not in Tip. Auto Fuel System Off. Engines Running, feed from Outer, Main is not raising up. Waiting until the Level is about 100 lbs in the Outer Tanks. Now adding Fuel to the Tips. Auto Fuel System still Off. Fuel Level in the Tips is now Draining but no Feeding to the Outer or the Main. Tip Tank is reaching the Level from the Outer Tank and now the Level off both Systems is draining again. Filling up the Tip again and now Auto Fuel System to Auto: Main Tank is filled up very quick (was at 600 lbs) until its normal Full Level is reached, then the Filling Rate slows down but the Main is still feeding with Fuel. Tip is loosing Level at the same Rate (First quick than slow), Outer is not filled up. Not with Auto Fuel System ON or OFF. It looses Level when the Tip Tanks are reaching the same Level.
  21. meierzwo
    Could be a Timing Problem if you switch them very fast nearly in the same second. I had this sometimes on my now retired old and outdated Gaming PC. But not with the new one.
  22. meierzwo
    I checked multiple Times. I got the Sound on Ground and also later in Flight. Also if I switch them on for the first Time in Flight. But only when switching them ON. No Sound on OFF. But the Sound is not the loudest. With Engine and Prop Sounds on a high Level, it's easy to overhear them.
  23. meierzwo
    Still little Information. Which xp12 Version? Beta? RC? Pedals direct to the PC or via USB-Hub (Passive or Powered one). Any Logitech Drivers installed? They are not needed IMHO. If you have that Problem again, open the Joystick Configuration Page for the Pedals and check, if you see the Movement there and the Hardware is recognized by the SIM. If the Hardware is recognized but the Action is not send through the Plane, the Plane or a Subsystem is not loaded correctly. There could be a hint in the Log.txt, so you should post it here or in the xplane.org Forum. As I wrote, I had this sometimes with early Versions of xp12. Hardware was recognized by the SIM but not in the Plane. But this was gone with later xp Beta and RC Versions.
  24. meierzwo
    And if you have any leftover Mixture Settings from a previous Joystick Profile, delete them. Or you could have Troubles with the Engine Startup Sequence. For the Throttle Lever Liftoff for changing between Alpha and Beta Section, I use a Button on the Alpha Yoke. The MU2 has a TOGA Switch and I don't want to loose that Function. Personal Preference. Edit. For a Pilots Handbook look here:
  25. meierzwo
    Hmm, strange. What SIM Version are you using? Rudder Hardware and how they are connected to the PC? It sounds like the SIM Version could be the culprit. Any Hints in the Log.txt? In earlier Versions of the XPlane 12 Beta, I noticed sometimes strange Reactions or Responses from my Flight Controls when changing Planes. Like a Profile or Subsystem was not loaded correctly. Add-ons or Plugins could also be a Troublemaker.
×
×
  • Create New...