As of today, I'm quite excited about getting back to developing add-ons and participating in helping others improve their add-ons.  AI is really making quite the change for the better, and a lot of the initiatives we've been working on internally are fast approaching internal testing and getting closer to making their way to the community.   

So as far as my own add-ons go.....we are steadily working through this conversion from Lua to C++ and starting to see some quite impressive success.  It won't look much different to end-users obviously, but for our part, this is a major, major milestone.  Mind you once this AI conversion is done and we have the workflow.....coding will no longer be the long straw in aircraft development.  We will be able to focus on 3D quality and systems accuracy and not get burdened down in compilation and coding syntax and the physical time lost to typing.  It really is an exciting time, and I know its been a bit of a burden having to wait for AI  to grow up to enable this point.   First up will be the MU2....probably around late September or October if our current success is any indicator. ....it will be our prototype test case for leveraging AI.   Then we'll take that experience and expertise and apply it the 733 and get it ready for another decade of service....and with no upgrade charge to existing customers.  

On the one hand, I'm bummed its taken this long, and on the other, I really couldn't see any other path, as annoying as its been.  This is just the nature of technology evolution...and taking the time to retool was the wiser and more prudent path for long term sustainability.  Ben Russell's Gizmo Lua opened the door for incredible products and enabled really creative folks to execute their visions and for this I am very grateful.  As with anything in life though, it comes in seasons and we need to look to the next one.

-tkyler

Why doesn't the flap animation work in replays?

This is incredibly immersive.

Is it my problem or everyone else's?

(Sorry, using Google Translate.)

The outline of the installation process is:

• install the KLN90B plugin
• place the GPS and MD41 panels in the 3D cockpit in PlaneMaker
• customise where the GPS screen gets drawn on the MU-2's panel texture, along with the UV mapping for the GPS object - don't worry, I've done this step
• use a utility that comes with the plugin to add manipulators for the GPS and MD41 to the MU-2's cockpit

Steps:

1. Download Todir's KLN90B - get the latest .zip: https://github.com/todirbg/kln90b/releases (at time of writing this was 0.99.1b)
2. Copy the `objects` and `plugins` folder into your MU-2 directory - don't copy `cockpit_3d`
3. Replace the `kln90b_click_regions.obj` file in MU2/objects/kln90b with the attached version (this has the updated UV mapping)
4. Make a backup of your 4B OEM acf file e.g. `xsMU2B60_4B_OEM.ackbak`
5. Open the 4B OEM acf (not the backup!) in PlaneMaker
6. Standard > Objects > Add:
   1. select `kln90b.obj` from MU2/objects/kln90b
   2. set its coordinates to 6.94, 0.10, 0.71
   3. set lighting to Inside, shadow mode Interior Only, hi-res Yes/ticked/green/selected
7. Add `MD41_V.obj` in the same way, coordinates 6.94, -1.68, 0.56, same parameters
   
8. Save the .acf - leave PlaneMaker open for now
   At this point, you can test your progress by launching the MU-2. You will see the KLN90B and the MD41 mode controller on the panel, albeit with a blank screen and no clickspots.
9. Edit MU2/plugins/KLN90B/data/modules/main.lua (in Notepad++ or VS Code or some other sensible editor):
   1. line 28ish, the KLN90_panel component, change `position = {814, 0, size[1], size[2]}` to `position = {0, 1138, size[1], size[2]}`
      (this determines where on the MU-2's panel texture the GPS screen is drawn. I've picked a spot which appears unused.)
      
      The next three steps are to accommodate a bug in the installer utility
10. Copy MU2/objects/Cockpit_3D/Cockpit_3D_OEM.obj to the MU2 folder
11. Make a temporary copy of `xsMU2B60_4B_OEM.acf`
12. Edit the temporary copy in Notepad++ or similar:
    1. search for kln90b. you should find where the KLN90B object is specified, and just below it the MD41 mode controller
    2. search for Cockpit_3D_OEM.obj - you will probably find it just below the MD41
    3. note the objects are identified with a number e.g. _obja/27/, _obja/28/
    4. cut all the lines for the KLN90B and MD41 objects and paste after the Cockpit_3D_OEM.obj - for me they were numbered 27, 28 and 4 respectively. (cursed alphabetic number ordering strikes again)
    5. change "Cockpit_32/Cockpit_3D_OEM.obj" to just "Cockpit_3D_OEM.obj"
       
    6. Save the changes to the temporary copy .acf
13. Run MU2/objects/kln_installer.exe:
    1. select your temporary .acf copy
    2. select Cockpit_3D_OEM.obj
    3. it should generate a new file in MU2/objects/kln90b: Cockpit_3D_OEM_kln90b.obj - this is the existing cockpit object with extra clickspots and the screen all in the right places
       
14. Move MU2/objects/kln90b/Cockpit_3D_OEM_kln90b.obj into MU2/objects/Cockpit_3D
15. In PlaneMaker, under Standard > Objects, find Cockpit_3D_OEM.obj, click the box to the left of its name and change the file to Cockpit_3D_OEM_kln90b.obj
16. Save the plane in PlaneMaker

To undo all of this:

1. Replace xsMU2B60_4B_OEM.acf with xsMU2B60_4B_OEM.acfbak

Steps 10-12 are a workaround for a couple of bugs with kln_installer.exe, which doesn't expect files to be in certain locations or for a numbered sequence to go 27, 28, 3, 4... they might become unnecessary with a future version of the KLN90B

If you'd like to position the KLN90B instruments elsewhere, use the Visualisation settings in PlaneMaker to hide most of the exterior and interior objects, and make adjustments. Then run kln_installer.exe again to regenerate the _kln90b.obj cockpit object.

Snags:

1. MD41 buttons don't seem to light up properly in the 3D cockpit. You can click on the annunciators to get a 2D popup - but I'd rather the 3D instrument worked correctly and I never see the 2D popup
2. KLN90B overlaps slightly with the top of the weather radar
3. Autopilot / FD / HSI mapping not figured out just yet
4. Powered by the default battery bus (or battery switch?) - you can give it a dataref representing a voltage bus but there's none available currently representing the radio bus voltages. This could be modded in though.

Happy flying folks!

kln90b_click_regions.obj

I don't quite understand the checklist

4. Power Levers............................................GROUND IDLE 
 5. Run-Crank-Stop switches..................HOLD AT STOP FOR 3 SECONDS 
 6. Power Levers.............................MOVE TO REVERSE AT 60% RPM 

Obviously, I don't know what you have already been considering for development projects, but this would seem to be one for which you may already have a significant headstart should you decide to take it on.

As another TPE331 powered possibility, I would also be interested in the PA-42-1000 Cheyenne, a real hot rod although with less range than the Cessna 441.

I would certainly be looking forward to either of those suggested products and will be keeping my eyes open for whatever you do have in the pipe.

Things this mod does NOT do:
1) alter fuel flows *NEEDS TOM*
2) modify the lua code
3) make the airplane easier to fly

Things to do:
1) validate takeoff performance
2) validate climb performance
3) Tune EGT more, you will be at 660C at FL200 and cruise power *REQUIRES TOM*
4) Tune CG *DONE*
5) Validate OEI performance
6) validate airfoils xplane parameters (theres some nuanced values which dont affect normal regime flight dynamics but should be adjusted for correctness, these will become more important as stall behavior is validated) *DONE*
7) validate stall behavior - suspected flap aero is the issue, will probably require custom flap lift controller

Things used to make this mod:
1) POH and AFM
2) Hartzell Aluminum Blade overhaul manual

Things that were tested:
1) Climb and Cruise TAS at POH settings for 10k, FL200 at 11,500lbs, FL310 11,000lbs

Instructions:
1) unzip the airfoils zip file into the following folder

X-Plane 11\Aircraft\X-Aviation\Mitsubishi MU-2 Marquise v2\airfoils

2) BACK UP YOUR ORIGINAL ACF FILES. For those of you that want to use a patch file open the MU2_mod_unified.diff or the MU2_mod.diff and apply that patch file. MU2_mod_unified.diff is a context 0 unified diff file, the MU2_mod.diff is a WinMerg normal patch file. Proceed to step 4.

3) For the rest, I applaud your dedication, you will need to open the acf and manually modify the following (i highly recommend notepad++ for this)

DO NOT under any circumstances use planemaker to make the changes. Plane maker converts all the values on file open then reconverts the values on file save which WILL induce uncontrolled file changes. The more times you open any file in planemaker and save it, the more changes get imparted.

a) open the MU2_mod.diff file using notepad++
b) Each section is formatted in the following way

[start line number],[end line number]c[start line number],[endlinenumber
< old thing
---
> new thing

so for example

25621,25626c25621,25626
< P _wing/0/_Croot 0.500000000
< P _wing/0/_Ctip 0.583333313
< P _wing/0/_afl_file_R0 Clark-Y (good propeller).afl
< P _wing/0/_afl_file_R1 Clark-Y (good propeller).afl
< P _wing/0/_afl_file_T0 Clark-Y (good propeller).afl
< P _wing/0/_afl_file_T1 Clark-Y (good propeller).afl
---
> P _wing/0/_Croot 0.349166662
> P _wing/0/_Ctip 0.678333342
> P _wing/0/_afl_file_R0 NACA-2330.afl
> P _wing/0/_afl_file_R1 NACA-2330.afl
> P _wing/0/_afl_file_T0 NACA-0003.afl
> P _wing/0/_afl_file_T1 NACA-0003.afl

there was a change starting at line 25621 through lines 25626 the C means change. The change to be made are all the lines with ">" markers.
c) manually replace all the values in the acf with the ">" values. excluding the ">" markers and replace so for example at line 25621 to 25626 your acf will look like this:

P _wing/0/_Croot 0.500000000
P _wing/0/_Ctip 0.583333313
P _wing/0/_afl_file_R0 Clark-Y (good propeller).afl
P _wing/0/_afl_file_R1 Clark-Y (good propeller).afl
P _wing/0/_afl_file_T0 Clark-Y (good propeller).afl
P _wing/0/_afl_file_T1 Clark-Y (good propeller).afl

after modifying it should look like this:

P _wing/0/_Croot 0.349166662
P _wing/0/_Ctip 0.678333342
P _wing/0/_afl_file_R0 NACA-2330.afl
P _wing/0/_afl_file_R1 NACA-2330.afl
P _wing/0/_afl_file_T0 NACA-0003.afl
P _wing/0/_afl_file_T1 NACA-0003.afl

4) Save the file once all the changes have been applied.

5) In xplane adjust your prop lever axis response to go up to 100% per the image below


I am very limited in time so I have done my best to explain the process, I highly suggest patching the file instead of manually editing.

Enjoy. I will update things as they happen. I have very limited time to offer technical support (troubleshooting) for this, so I leave most of the trouble shooting as an exercise for the reader. Additionally the ods version of the W&B document doesnt contain the text labels that the excel version does (image of the excel version below)
 

airfoils.zip

MU2_mod_unified-2022-08-09.diff MU2_mod-2022-08-09.diff

W&B.xlsx W&B.ods

DOWNLOAD:  https://www.dropbox.com/s/adpm5dqlje0b91e/TOGA_MU2_Paint_Kit_v2.zip?dl=0

NOTE:  The 3D *.fbx model included in the download link has been modified slightly from that shown in the demonstration video. .  See  this link for more info (it will make more sense after you watch the video)

About a year ago I picked up the Q400 as my first turboprop (wanted to branch out and try something a little from my usual jetliner flights) and immediately was hooked on the unique handling (specifically landing) and visceral experience that two roaring turboprop engines provided... But now after a good while spent in the Dash, I've been wanting to find a new turboprop with a little bit more character... That's when the Moo caught my eye. And WOW! My first flight took a little while in getting to grips with how much of a handful she can be with each power setting (trim trim trim!), but even after just a few flights, I'm already getting my head around it and it's been just a joy to fly so far. I am also closing in on that perfect butter landing... I think my best so far has been in the -140ish FPM territory, but we'll get there. Anyway, that's all to say that you've got a magnificent product here and I'm a very satisfied customer. The provided documentation has also been very helpful too - big kudos on that! 

I do have a question that maybe someone has the answer to: while admiring the 3D model, I've noticed that the engine air intakes seem to be a bit bigger than most Mu-2's I've seen in pictures... Is this because of a different engine variant on our sim version? 

All the best and thank you for such a fine product,

- Cactus

I have followed the normal procedures and consulted this: https://www.togasim.com/mu2docs/supplements/troubleshooting.html#engine-wont-start

Can't start engines no matter what I do.

Any tips or a link to a video?

Thank you.

Not fully ready yet but I've put together a W&B and performance calculations Google spreadsheet, based on the 4 blades AFM.

W&B payload stations are listed as I configured them in Planemaker. Since we can only have 9 stations, it's missing some of them.

Performance results so far look pretty ok. I'm cross checking them with ForeFlight performance profiles for the MU2 and I'm getting +/- 10 Lbs in terms of fuel.

Happy to share if that could be handy when adjusting the flight model in future versions!

Cheers!

I have started a YouTube playlist of my terrible landings: 

The inverted power/pitch relationship of high engine aircraft always screws me up, but this module is a ton of fun

All these flights start near MTOW and land after burning about 600 lbs fuel, so they're still landing pretty heavy.

I have a long way to go before I'm touching down in my target zone at sub-200fpm speeds. The awful stuttering I get near the ground doesn't help.

I don't sim jets, so this is by far the hottest airplane I try to land, and it feels fast and dopey in landing config. I'm enjoying the challenge. I'm also enjoying the cruise speed!!

Hell of a module

http://www.air1st.com/around-the-word-n50et.html

Darrell

First of all, thanks for the MU2 XP12 upgrade!

I also have the RSG G500 and noticed that there seem to be a missing click region for the MFD knob push button.

Opening the Cockpit_3D_GLASS.obj, I didn’t find command button « rsg/g500/cmd/mfd/knob_push » which is in the RSG demo C172 3D cockpit adapted with the G500.

Am I missing something?

Thanks in advance and cheers!

The plan is to get the next release patch, 2.0.3 out for V11 (relatively imminent), and then begin the official port / testing process for V12.  Probably will begin the work next Monday.  I do not expect it to be terribly long.  Chances are XP12 will go through some growing pains anyhow and I'll be right there alongside the process testing/tweaking the Moo.

Experienced XP users should know to keep their XP11 versions around until they're fully happy with V12.  

Here's a few screenshots of the Moo in V12.  Not terribly bad, but I may tweak it after I get going.  Things tend to look a little bit shinier in V12...but also brighter, which is good.

Would be really awesome and necessary in a turboprop 

Thanks and take care!!

Keep up the good work TK...

Should be a simple thing but couldn't find the key bindings joystick key bindings for TOGA's MU-2 for AP (Engage). YAW, GA (Throttle) and Yoke's AP Disconnect and TCS under xscenery\mu2b60

Help mostly appreciated

I've tried changing the centre of gravity and the plane rebalances back to 5 degrees nose up. 

I've tried trimming it out hard, same thing.

Where can I find more of it? Thanks!

ps. Those made for previous version (v1.x) can be used for v2?

I have just purchased this plane and read through the manual.

However, I cannot find out what the yellow handle near the elevator trim wheel is for. Please see the picture.

Could someone please tell me? Thanks!

But, how do we know if the prop is already on the lock?

Thanks a lot!