Leaderboard

After doing a review of the flight model and taking a fine chisel to it I was able to get the Performance more in line with the POH cruise figures. The take off performance seems better but has not been evaluated. This mod is NOT supported by TOGA Simulations. They are aware of it. TOGA Simulations are not obligated to offer any form of technical support to a modified aircraft, so don't contact them. IF YOU CHANGE YOUR ACF YOU ARE ON YOUR OWN. If you are not familiar with modifying the acf file with a text editor you will find this challenging but doable. You will find this very difficult to do if you aren't using notepad++. You will find this very easy if you use a file patching utility (https://www.google.com/search?&q=applying+diff+file+windows) or (https://www.google.com/search?q=applying+diff+file+mac). Things this mod does: 1) New wing airfoils 2) New Prop and prop airfoils 3) New max power 4) Tuned prop governor 5) cruise performance TAS within 1% of POH values 6) Take off behavior more aligned with POH takeoff profile 7) *NEW* Added ventral and wing tank fins 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

Maybe someone did step?

Small change to the format on the bug_tracker page. I simply included a status at the top as to when the page was last updated. http://www.togasim.com/mu2docs/supplements/bug_tracker.html Unsure how this will work out over time. A lot of good ideas go by the wayside if they're too cumbersome, but I think this is pretty lightweight on my end. I'm not scheduling any type of regular update timeframe so it can be updated at any time. I sit down to work...do some stuff and after a while, say to myself, "self...folks may want to know that these changes have been addressed" and I then I update the page. I probably will; however, create a new post here for each significant update so that folks can see it in the forums as a "new post" and have it stand out a bit. -TomK

yea..did a test. no doubt I'm not representative of the norm with my trackball setup..2nd time I've messed that up! Talk about tunnel-vision....sheesh....anyhow, I swapped to a typical mousewheel and yea....very paintful I agree. My scrollwheel has all sorts of acceleration and "momentum" and I just spin it like a record player (a what?) and it it can blow through 30-40 increments in a quick spin. After testing with a normal mouse....single mouse click and single scrollwheel click logically should increment by 100' . Click and hold set to match the scrolling speed limit of the scrollwheels. The animation does have a 'mechanical speed limit' and I've matched the 'hold' speed to that. It takes approx 8 seconds to go from 0 to 25000' now with 'hold'. Much more reasonable and feels much more natural. Thx. gents.

http://www.togasim.com/mu2docs/

Hi, im not sure if these are bugs as I don't know the MU-2 in real life, but I fount some "anomalies" during my first fights with the MU-2: - the OM an IM MKR lights seem to be switched. Normally OM is blue and IM white. - the left speed indicator has no max speed indication like the right one. - shouldn't the turn and slip indicator also work on ground? - the slip indicator under the artificial horizon seems to be working inverted. Thank you very much for this beautiful aircraft!

I didn't mean digress with respect to whether or not it should move on the ground, I do agree with that. digress in the sense that I said it was "fixed" for next update as of that previous post. I simply had a curiosity on the response of the instrument for rapid yawing on the ground..but will implement it.

That is correct....good catch. Fixed for update another good catch. removed it from the right side for the time being, until I can transponse my air data code from the ixeg project. Indeed. fixed for update. wondering why I missed these...turns out these were some of the earliest instruments I did and I put in some placeholder code pending "wiring them to electrical busses and fuses" which I would do in the future and apparently forgot about them. All fixed up though. Thanks so much -TomK

Well...the bad thing is its on my 'paper list' here in front of me, (but somehow not on my bugs page....doh). Thank you for the report. -TK

FYI, here are the now implemented numbers for fuel capacities. There is some "wiggle room" based on what density value you take for Jet-A/.A1 of course....averaging or whatnot, etc. I've decided on the low end of 6.71 as its more conservative and probably a tad safer to be under with FSEcononmy than over IIRC. It should be close enough for FSEconomy I should think. Thanks again Jerry....so many numbers (next update).

Thx Jerry, I put it in the Bug tracker for the Moo

For the early-birds https://forums.x-pilot.com/forums/topic/24825-toga-simulations-mu2-version-20-paint-kit-rc1/

baro command implemnted, plus NEG flag

Just a note to say Thank YOU! Took it for a spin this evening over the mountains towards Wenatchee, Washington.

Thanks so much for the input: Altimeter does goes backwards from 99999; HOWEVER (and I forget to implement this...so thx)...it has a NEG flag on the first 3 digits. Clock will get replaced for sure. its subject to sit below higher priority items, but I don't like it either, which means I'm certainly going to fix it (GTX330 graphics too). Engine RPM....I'll check all the "numbers", both physical and FMOD, which of course drives the sound. It could be the values of FMOD are off a few decimal places. TBM900 throttle is excellent no doubt, but unsure if I can implement just yet, I'm looking into a solution with my current methodology. TBM900 completely overrides X-Plane controls/engine giving ultimate flexiblity between hardware and controls where I do not yet. I still rely on X-Plane's TPE-331 implementation for 60% of the functionality and that means fighting X-plane's default throttle joystick behavior. I do want this behavior in though (and indeed my own engine model) and will be giving it a good look see very soon to assess the options; however, it won't go in before the GTN, that's for sure. GUI: There is absolutely an advanced GUI plan with all sorts of goodies desired.... I just got into imGUI, this is my first go-round and once all the other particulars of the plane operation are stable, then I'll definitely turn my focus to "interaction". LibRadio. Not doubt if I can get it running on my architecture. Bug Saso for sure Final words..I've never been the GUI graphics guy in my other partnerships, always the flight model / 3D / systems guy, BUT I'm just starting to poke around with GUI interfaces....and you can be sure that the better I get, the more toys I'll start throwing in. I still have quite a few ideas I want to get into this product....and this Version 2.0 is the baseline! -TomK