Leaderboard

Hello all. Those who have followed know that the IXEG 737 develoment has been stagnant for a long time while I've worked on my MU-2 project and stabilize it after the release. That stabilization phase is nearly done. XP12 is imminent and I'll be porting the MU2 to XP12 beginning next week...and it should not be terribly long (I hope). After that, the 733 will move back into rotation as the primary focus of development with the port to v12 being the first priority. The IXEG is minimally operable in V12, but that's all we can say. We obviously had to make it baseline flyable in order to test/develop it with all the XP12 changes, which have yet to be addressed. As such, our official position for those who wish to try the V11 IXEG in V12 is "VFR joyriding only". I expect we'll set up a 'volunteer forum' where folks can give feedback as to their V12 observations as its better to have more eyes on this stuff; however, we request that nobody report any shortcomings of the V11 733 in V12. We are keenly aware of a lot of things that have to be changed....so we'll want to wait until we believe we've caught all we can find before other folks chime in; otherwise we'll end up with a massive stack of the same reports. So, certainly keep XP11 around if you wish to fly the IXEG seriously until we get it ported over. I've always kept "old version / new versions" side by side on my computer for these transitions. Long-time XP users know that after a major release to X-Plane, there is an inevitable debug period that goes on for some time, though many other devs have begun already, we're behind. ....but nice to have the process underway.....Below screenshot shows what the cockpit looks like in V12 daytime. -TomK

An X-Plane 12 update will come for most all products, including the TBM. That said, X-Plane 12 is considered Early Access. We are not necessarily focused on releasing updates just yet while the dust settles and bugs get worked out.

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

I have not officially begun to test / port the MU-2 to X-Plane 12; HOWEVER, I have been testing it regularly in X-Plane 12 and the good news is that it seems at first glance....to be mostly functional....FOR.....daytime flight. I say this because the biggest change in X-Plane 12 is the new atmospheric and lighting engine..and this requires new "directive commands" for lighting that were not present in X-Plane 11. The nightlighting is practically non-existent until I make the required changes. Also I have to make some notable changes to take advantage of the rain effects....so the V11 version "in V12" will not have the new windshield effects. So....daytime and dry seems to be mostly OK using the V11 version in V12. I know there are some turbine engine changes also I have yet to test...so unsure what their effect will be. 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.

Please for god's sake make it a paid upgrade, if only to get you guys to be more financially motivated in your work. The IXEG has been languishing for years, and I've seen addons from other developers being released at an unfinished state, and those devs lose interest as sales slow to a trickle. I loved the 737 Classic and I would love to throw money at you guys if I can get a fully featured (i.e. proper VNAV and holding), fully functioning addon. I also want the -400 and -500 if you want to make paid extensions as well, like what PMDG is doing. Also some Brunner force feedback yoke support would be nice.....

It would be nice, but also keep in mind the XP 12.00 beta period will likely be several months long, and be a constant moving target for developers. So we’ll see.

Just a developer commentary to any who may also read this. CaptCrash did discuss these with me and I am happy he is looking at the performance and I am also keen to improve the performance numbers; however, the relative work (relative to everything else required to be done to get 95% of the customers happy) ... to get the last 15% of performance accuracy is such that I have always found it best to do those final refinement tweaks last, after everything else is working. This is generally because the final performance tweaks can be made quite quickly....with all due respect to the FLIGHT TESTING...which is not very quick though. As soon as the obvious issues slow down, I'll will take a deep breath and start on the fun stuff, which includes performance. Call it.."round 2" of V2 work! -TK

There is no way to know this for certain. So far the plane loads and flys in v12. But, Austin has made engine model changes that we do not have yet. I am hoping that any changes will be minor and be part of a free update if necessary.