Leaderboard

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

This will serve as an official announcement that we have released the TOGA Simulations MU-2 Marquise version 2.1.0 update. All customers who have purchased the MU-2 Marquise v2 up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the MU-2 Marquise v2 from today forward, your purchased download will already be updated to version 2.1.0 for you. What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php 2. Find your original MU-2 Marquise v2 download and re-download the file. It will download as the latest version! This version brings official X-Plane 12 support. See all the v2.1.0 changes by clicking here! As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support! Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.

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).

@Ralf Maylinglad you got it worked out.. Sorry for slow reply, family weekend. -tkyler

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

I have a confession. I was approached about 10 days ago to participate in a short-notice endeavor (X-Plane related) that was tough to refuse and had me put the IXEG work on hold for this time frame....so this short delay in our original time estimate is squarely on my shoulders.....but I feel was the wiser decision for my continued work in X-Plane. I'm back on to the IXEG tomorrow. This side endeavor will become known sometime today I suspect. The good news (hint) is that completion of this endeavor will allow me to continue on the IXEG development right after the V12 port version comes out, and not have to detour back onto any other work....and there is a bit of an 'Easter Egg' in this endeavor that reveals the two projects we plan on working on in 2024. So we'll roll out the V12 port and I'll jump right back onto the FMS and other improvements planned for the remainder of the year. So this endeavor delays the V12 port, but moves forward the follow-on work. Those improvments (FMS, new nav data, beginnings of new 3D exterior) will take the better part of 2023 I'm sure, but we'll start that immedately after the V12 port release. As far as time frame for the V12 port now.... I can't say exactly. we always feel "close" because all the big stuff is out of the way. My todo list largely consists of finishing the interior texturing (rear galley), putting in the wing flex and squashing Jan's list of 'mostly small' issues, that's the list. I am dealing with 3 graduations of my kids this weekend (and family get-togethers).... and they will get my time to celebrate their achievements. I'd like to be done within 3 weeks, that's all I'll say. Will we be done in 3 weeks? I don't know. If not, I'll certainly be closer than I am today and still moving! -tkyler

Got a few more from a recent flight showing the aircraft easing into Le Bourget

I would like to chime in here - I have worked with Tom on this over the last week intensively - previously I had test flown the 737 in XP12 (after we fixed the major roadblocks of even getting if flyable, like making the flaps work, etc.) and I had tuned the flight model. Tom worked hard on 3D modeling over the last months with little for me to do (I am too stupid for blender and those things) and now with him approaching the end of that work, I dove back into flight and system testing. The more I test, the more stuff shows up that does not work anymore, because Laminar changed things - and these changes are all improvements in modeling systems, yet they still leave our "old" way of doing/overriding them unusable. So in a very real way we have to redo a lot of the things we already did for XP11, it is not a quick conversion at all - and this is something we definitely underestimated when we initially said to "upgrade to XP12 for free". The move from XP11 to XP12 is not an upgrade, it is in many areas a repeat of the dev work work we already did for XP11. And I am thankful for most of our customers to be very understanding of the fact that we charge a small price to compensate us for this! I think the old 737-300 still has a lot of life in her, I thoroughly enjoy my "test flights" and find myself again and again to "just finish this approach" even though I was just testing some autopilot PID constant ... simply because it is fun to fly and looks great in XP12 . Cheers, Jan