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

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

I'm looking for tutorials, videos, or documentation that helps someone transition from, say a C172 or B58, basically your average beginner GA aircraft to something like the CL650. Someone who has done casual flying but is now looking to expand and enjoy the flight sim genre a bit more. I really enjoyed flying the C172 and B58 with the REP. I enjoyed sync'ing the Baron engines and flying to altitude and tuning for performance as shown in the REP manual. Someone then recommended the TBM and after balking at the price for a few weeks, I bought the aircraft and thoroughly enjoyed it, kicking myself for not buying it sooner! My first adventure was taking a TBM I "purchased" from Papua New Guinea to my home base in France in FSEconomy. This made the CL650 an instant buy for me to support the amazing work of the Hot Start team. However, I have zero airline experience and have thus far avoided the FMC by using the RealityXP GTN module. I really don't know where to start to learn this aircraft so some guidance would be appreciated! For example, I wanted to know how to start up the airplane from cold and while I found the checklist, it might as well have been in greek or klingon as I didn't really know where to look or where to begin. Luckily, I found a tutorial video and just basically followed along! I can do cold starts on the F-16 in DCS and BMS and also the F-18 in DCS (still learning the Tomcat!) so I'm not entirely new to this but just for some reason find airlines or fancy jets a bit intimidating. Any help or guidance would be greatly appreciated! I know this is a new add-on so if anyone is working on such tutorials, please let me know so I can keep an eye out for that as well. Thanks!

Captains, In the days since release of the Hot Start Challenger 650 there have been concerns that Gizmo and even the Challenger 650 plugins were causing a major performance impact. We went investigating this, and even got Laminar Research involved to understand what was happening under the hood of X-Plane to try and sort this out. As it turns out, Gizmo is NOT the source of problems, and neither is the 650 plugin; not directly, anyhow. What's happening is somewhat complicated, but I'll do my best to be descriptive, yet brief. X-Plane is programmed to use up all of your CPU cores in order to try and attain higher frame rates. In doing so, there's some major texture paging going on. The problem here is that it leaves almost no room for the Challenger to get its CPU operations done in the process, and mixed with a ton of texture paging, everything goes bust and tasks get stuck in a queue where X-Plane drastically slows down, things pause/stutter, and the experience becomes abysmal. If you happen to have your Plugin Manager open in X-Plane while this happens it will present itself as if Gizmo or the Challenger are using up an insane amount of performance, but this is actually just a mean trick when looking at it from a user perspective. X-Plane slows down so much that it LOOKS like our plugins are to blame as their tasks are not yet performed while X-Plane does other things. Before I go further, I should note, this is NOT applicable to everyone! Most customers here seem to have a great CPU/GPU combination that can handle all of this, but if you're one of the people on the struggling end of the spectrum, you'll want to keep reading this post! Version 1.1.0 of the Challenger 650 introduces a new installer that has a selection for GPUs with more or less than 6GB so we can best optimize your install for you. This will help with some of the VRAM/texture paging operations. That said, there's still more to the puzzle. Because X-Plane is using all the cores/threads on your CPU, it is not saving "room" for the Challenger 650 to do its operations efficiently and the CPU becomes oversubscribed. Laminar Research is likely to fix this issue for developers at a later date after X-Plane 12, so in the meantime we have a workaround to use that Laminar has sanctioned to give out to those affected. If you are affected by this issue, please do the following (this is for Windows users, as the issue seems most prevalent with Vulkan): 1. First, find X-Plane's application and create a shortcut so that we can create parameters. Right click on X-Plane > New > Shortcut 2. Right-click on your shortcut, and select Properties on its contextual menu to open the shortcut's Properties window. 3. The shortcut's Properties window is the place where you can add command-line parameters for that shortcut. Select the Shortcut tab and look for the Target field. 4. You will see a place that has the path to X-Plane labelled Target. X-Plane's path will be in quotes. At the end of the quotes, make sure there is a space after the quotes, then type/paste: --num_workers=n <== Replace the red 'n' with a number equal to three fewer processors/threads than your CPU has (this accounts for X-Plane's "main thread"). For example, if you have a 6 physical + 6 virtual processor CPU (known as Hyper-Threading for Intel and SMT for AMD) for a total of 12 threads ("logical processors" as Windows refers to them), you should put the number 9 in place of the red 'n'. Also be sure you have the TWO hyphens/dashes in front of "num_workers"! 5. You can now rename this shortcut to something like Challenger 650 if you like. That way you can just click this one when you know you'll be flying the Challenger. If you are unsure how many processors/threads your CPU has, go into your About Computer setting and Google your CPU model number to find out. Be sure to use the total number with Hyper-Threading/SMT (if enabled) as your starting point! We know this is a bit unorthodox, but we're doing our best to make whatever solutions we can for as many people as possible. Hopefully this makes your flying more enjoyable!

Updated Docs http://togasim.com/mu2docs/supplements/bug_tracker.html http://togasim.com/mu2docs/setup/hardware_setup.htm Update work is closed for Version 2.01. I believe I got just about 95%+ of everything. I'll be at Oshkosh Air Venture for next 10 days and not working, but will eyeball the forums. The updated docs reflects the changes made that should be pushed out in an update very soon. The docs changes are mostly the bug tracker and also the hardware config page, which highlights the new hardware configurations to get the TBM-style throttle and "condition lever commands to emergency". -TomK

I’m not aware of anyone having found a legal means of acquiring them for public consumption yet, unfortunately.

I can confirm this. Having done flight performance validation on the CL650, Felis 747, and flight model reworks on my own project, and the community C90 mod, the flight testing is the slowest bit. I have a workflow and template that I work from to test the effects of changes to the flight model. And omg the spread sheets: some images below. The props took me about a day to validate. I'll be publishing a new patch with the HSTAB airfoils and some other inclusions, right now im currently within 2% of POH climb and cruise performance, I have some more tweaking to do.

it IS a wonderful sim that Hot Start have created here!!!! See the drawing (sic) below for the main gear locking mechanism. Claws that are part of the upper portion of the actuator (in black) grab the top of the lower portion of the actuator (in red - this is the shiny part of the actuator seen in the picture of one of the previous posts). The locking mechanism is a "hat" (in green) that positions itself over the claws and prevents them from releasing. When the gear handle is down, hydraulic pressure is continuously applied on the down side, which will (should) keep the gear in the down position, and the "hat" over the claws, even when the pins are not in. When you select gear up, hydraulic pressure lifts the hat, and pushes the lower actuator up a bit. The claws will spread and the actuator moves to the retracted position. Before you switch off hydraulic system 3, you have to put the pins in. The pin locks the "hat" over the claws, thus preventing actuator movement. If you forget to remove the pins and take off, the gear will not come up because the hat remains in place and the claws can't spread. People have tried...

There is not. But the list is a good indicator at this point.....When the TODOs are done, I'll test it all one final time and then begin packing it up for distribution. I've been making decent progress through the list so I don't suspect it will be too much longer. -TomK

I always arm NAV on the ground when flying an RNAV departure, no reason not to really.

Hot Start CL650 Substance Painter Paintkit View File This is the official Hot Start CL650 Substance Painter paintkit file. It contains several liveries within the "Paint" folder" on each UDIM. You are free to add to whatever materials or masks to those layers as you wish. There are other folders that are set as default textures, with materials included. These are the correct materials for the areas they are assigned to, but you are free to alter those as you wish. As usual, if you plan on changing anything, keep the original smart material, and copy/paste the original to a copy. This will save frustration if you wish to return to the original materials. Please read the included readme file. Submitter Goran_M Submitted 07/20/2022 Category Hot Start Challenger 650 Livery For https://www.x-aviation.com/catalog/product_info.php/take-command-hot-start-challenger-650-p-212?osCsid=3s771ioj1g7c3vdsh78u9ft174  

Noted on this, added to bug list. Thank you. Regarding the click zone, This is indeed a tough philosophical discussion. I'm on the fence about hiding the manips when hardware is present. I've heard arguments both for/against. I think this will evolve into an "options" where you can choose your preference but doing so requires a bit of coding infrastructure on my end....so hopefully we'll get everyone accomodated soon. I am not terribly happy with the 'unfeather test' / condition lever situation myself...its a fight against X-Plane...I fought this more than I would have liked. The only reason I accepted it for now is its a small part of the overall experience, but I won't be happy till its perfect. -TomK

Documents last updated 20th December 2022 IMPORTANT: you must be signed in to download the PDFs below. Not a user yet? Head over to Sign Up. 1128340285_CL650FMSPrimer.pdf CL650 Operations Reference.pdf 1323904309_CL650ExpandedNormalProcedures.pdf CL650 Checklists.pdf CL650 Checklists - Printable.pdf CL650 Flexible Take-Off.pdf CL650 Shared Cockpit Quick Start Guide.pdf