OneOffRegistrationUser

It's funny that I recently fixed this for my copy by FlyWihLua script. Attaching just in case. MU-2_Brakes_Fix_v2.lua In order to make it work - search sim/joystick/joystick_axis_values with datareftool, found your brakes axis numbers and change this two numbers in script with proper numbers(mine are 26 and 27): local Left_Brake_Axis = 26 local Right_Brake_Axis = 27 Offtop: tkyler, I saw your interview with Q8, a lot of amazing stuff and very motivating!

https://forums.x-pilot.com/forums/topic/26656-mu-2210-pax-and-fuel-load-manager/

Well, I'm personally do not mind to pay extra for updated Moo. And saying that I do not event expecting anything new, just current issue-log cleared.

Hi folks! Reporting Brake application rate issues I just noticed with my setup (TM Pendular Rudder): 1. Brake application rate in MU2 preferences being applied to Right Toe Brake axis only. Left Axis is unaffected. 2. There is no option to remove this effect entirely for direct input from hardware. Even with minimal possible settings 0.01 - there is some noticeable delay on braking. 3. [not confirmed] It feels like braking forces are not being applied to wheels on press-n-hold, but force gradually growing with noticeable delay. ( irrespective to settings in P.2.) I will be happy to be proved wrong. Thanks!

Example script to map Mu-2 dataref to XP command(s) Mu-2Assesories.zip

Hi folks, @tkyler that Yaw damper situation is still drives me crazy- it looks like it is not really working on Mu-2. Lamp in cockpit reacting OK, datarefs are looks OK, buttons work, gizmo scripts are encrypted (so who knows), but seems there no any effect neither on flight model neither on rudder itself. Tried different planes - once yaw damper enabled you can feel it in windy day and see rudder moving. With that - can I please ask to confirm it is not working in current state and will be fixed "in two weeks" or my expectations are wrong or anything else please?

Try standard: sim/autopilot/heading_down sim/autopilot/heading_up

X-Camera will help. Free version.

Hi, appreciate your interest! Sorry, I do not have options to test GLASS, and also away from my SIM PC. Tho I this can share: 0. Do all above. 1. !BACKUP! your XPlane12\Aircraft\X-Aviation\Mitsubishi MU-2 Marquise v2 2. Open xsMU2B60_GLASS_XXX.acf with PlaneMaker 3. Go to Standard -> Weight & Balance -> Payloads 4. Set all numbers and options exactly as shown on attached photo. 5. All done. You are Fantastic! 6. Have fun.

Second (optional) script Mu-2Assesories.lua in this pack will help. Can be uses as standalone script.

I might be wrong but(it hard to see on video): - You do not really need to press red buttons (primer?) - Throttles should be at Ground Idle or at list lower than Flight idle. - It looks like switches are on Crank, while should be in Run. - Your Main tank is empty. Engines are feeding from Main tank in MU. It seems last point is the most possible reason. XP12 managing fuel wrong way for Mu. If you concerned - try one of mine amended ACF (and fuel loader) here in the forum.

Well, seems so. Or with XP12 auto-generated payload of some sort. With this ACFs you do not have to use Script to load payload actually, new "Payload Stations" will be available on native XP12 load screens. Tho with script you will have more options to load pax. Also it is allow to properly load fuel (Mu fuel management is bit different than native XP).

Hey dorianR666, welcome to the club. Sad you have it. Please see workaroung few posts above. It is tested and works OK for me.

Found it! Comparing 2.0.4 vs 2.1.0 Which one is closer to realty?

Just checking: engines spool-up time feels like twice faster than in 2.0.4. Is it me or something changed? Noticed this looking on the time required to hold start button until it lit.

Wow, thank you! I'm happy you like it! I'm not exactly looking for something specific really, just overall feel and opinion if it's good. I'm quite interested in feedback on takeoff\landing behavior, coz I feel like original Mu's FM is quite sensitive in these regimes.

Hi folks, this is experimental 5B_GNS ACF adjusted with items below. Despite knowing that XP is doing some tricks with flight model and authors trying to compensate this fact - this is attempt to use some POH numbers in XP. Changes: - Propeller placement point moved 90mm forward for 5B version. - CG and it's limits aligned to MAC. - Payload stations added. - Static Gyration disabled. - Additional fins (on tanks and rear part of fuselage) added to flight model. I do not really think any major effect should be expected here. Just feeding my perfectionist's ego. Tested in flight loaded and empty - looks\feels OK. Any feedback will be really appreciated. xsMU2B60_5B_GNS.acf

Hi folks, this is updated ACFs with added Pax and Payload stations for Mu-2 (2.1.0) and Load Manager script. No settings changed from original except Payload stations. Custom (original) Gyration is enabled. You can disable it in PlaneMaker to let X-Plane calculate moments of inertia depends on Pax\Payload. How to install: 1. !BACKUP! your XPlane12\Aircraft\X-Aviation\Mitsubishi MU-2 Marquise v2 2. Copy xsMU2B60_XXX.acf form ZIP to XPlane12\Aircraft\X-Aviation\Mitsubishi MU-2 Marquise v2 3. Copy Mu-2_Load_manager.lua \XPlane12\Resources\plugins\FlyWithLua\Scripts 4. (Optional) Mu-2Assesories.lua \XPlane12\Resources\plugins\FlyWithLua\Scripts How to use: 1. Open window via: Plugins \ FlyWithLua \ MU-2 Marquise Load manager or Assign Keyboard\Joystick button via \FlyWit\Lua\Mu2LM control(see Manager_Open_Close_Key.JPG) 2. LOAD Fuel: Input required Fuel in Lbs., Press LOAD FUEL - Fuel will be loaded to aircraft respecting Tanks sequence. 3. LOAD PAX: 3.a. IF "Random Pax" UN-checked: input required number of passengers, Press LOAD PAX: Script will load requested number of PAX respecting seating sequence, with each Pax weight = 195 lbs. 3.b. IF "Random Pax" Checked (Default) and Pax total weight equal to 0: input required number of passengers, Press LOAD PAX: Script will load requested number of PAX respecting seating sequence, with random Pax weight for each Pax within range 70-275Lbs. 3.c. IF "Random Pax" Checked (Default) and Pax total weight inputted: input required number of passengers, input required total weight of passengers, Press LOAD PAX: Script will load requested number of PAX respecting seating sequence, with random Pax weights but Total weight equal to specified. 4. LOAD BAGGAGE: Input required BAGGAGE Weight in Lbs., Press LOAD BAGGAGE - BAGGAGE will be loaded to aircraft into BAGGAGE area. 5. Note Total Weight and MTOW, if exceeded it will change from MTOW OK (green) to MTOW EXCEEDED (red). Note: All input fields are limited to Numbers found in POH. Note 2: No Pilot Payload exist in this loadout due limitation of XP12 and assumption that aircraft is trimmed\adjusted\loaded to compensate pilot weight. Mu-2Assesories.lua This is Optional script required for additional Lights, headset and parking brake Controls. This script adding several control commands you can map to your hardware to utilize buttons or switches to manipulate Nav, Beacon, Strobe, Taxi and Landing Lights, plus Parking brake (in Hold-on, release-off mode) and Headset. How to install: Copy Mu-2Assesories.lua to XPlane12\Resources\plugins\FlyWithLua\Scripts . Look for new commands in "Mu2Misc"block of keybindings\controls. Mu-2-LoadManager-for-2.1.0_v1.zip

Sure. Processor 11th Gen Intel(R) Core(TM) i5-11600K @ 3.90GHz 3.91 GHz Installed RAM 32.0 GB (31.9 GB usable) Video: RTX 3070 Ti (8GB), driver 531.79 (default settings) Edition Windows 10 Version 21H2 OS build 19044.2846 XP: 12.05r1

Try mine here in forum. :) I'm going to issue new version for 2.1.0 tommorow.

Reporting back: Bad news: All Mu versions are affected for me. Good news: - Int_Glass_Reflector.obj - once it is removed from ACF issue is gone but together with that nice thermal pads. Removing NLM or LIT not solving this issue. - Workaround: Set Int_Glass_Reflector.obj as Glass (Inside) in ACF. Issue is gone. Seems like reflection is gone too, which makes me even more happy! :) Real root case is still unclear. everything is defaulted including driver settings and XP shaders reset. Only Windshield affected for me, side-window nearby is perfectly fine. Thank you for your time looking in to this.

Regret to say that, but I have this with Mu only. 4B_OEM and 5B_GNS - same results. Updated video driver, refreshed XP12, restarted. Looks like it is somehow interfering with mealiness or reflection, if you ask me. Or incorrect rendering order. Please see below default 172, Q$XP also fine. Effect is seeing better on dark background.

Testing with 5B_CNS.Yes, it is every time. Did multiple reloads, no luck. Let me check other variants and report back.

Hi folks, just checkin if this is only my problem or someone have similar? Windshield rain looks pixelated. Side windows are fine. Clean install of Mu.

Hi folks, sorry for re-opening this. My initial suspects were Traffic Global and ASXP. While doing some test flights, I got this error without ASXP, so uninstalled Traffic Global, made some successful flights with ASXP. Now I got it again. So it looks like this issue is related to MU to some extent. The XP crashed while taxiing on the runway, just like before. I'm a little at a loss to name something specific: just a regular start-up, taxi, boom. Just saying: I do not have this "C:\GitLab-Runner\..." on my PC. 0:26:44.153 E/SYS: MACIBM_alert: Using RE_lo andf RE_hi index -1! 0:26:44.153 E/SYS: MACIBM_alert: Re #=-2147483648 0:26:44.153 E/SYS: MACIBM_alert: Re #'s avail=4 0:26:44.153 E/SYS: MACIBM_alert: Airfoils/Clark-Y (good propeller).afl : mid foil 0:26:44.153 E/SYS: MACIBM_alert: C:\GitLab-Runner\builds\2dtum6M9\0\x-plane\design\source_code\engine\veh\definitions\aifl.cpp:235 --=={This application has crashed!}==--