Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 07/16/2022 in all areas

  1. Hello all. I will endeavor to support and address issues on the MU-2 as rapidly as practical. The period after a release is always fraught with bugs and challenges, frustration and impatience. I have been there myself and please ask for your patience. I'd like to think that those who know me know I'll continue to support this product for many years to come and provide you a great value for your money! I am located in the GMT-6 timezone and work reasonably normal daylight hours. I generally don't work Sundays (though may converse on Sundays).
    9 points
  2. 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
    7 points
  3. Another one for today
    5 points
  4. Hey, why not another one, starting no 2
    5 points
  5. 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
    5 points
  6. XP12 will have this built in. There's no point in using dev time to add this to XP11, when it only works for OpenGL.
    5 points
  7. http://www.togasim.com/mu2docs/
    4 points
  8. Version 1.0.0

    25 downloads

    This livery is based off the real life CL-605 registered C-FGRS, however it's very generic which means you can assign any reg you want to it using the dynamic registrations. Huge thanks to Goran and everyone else in the Hot Start discord for helping me learn how to create this.
    4 points
  9. I took some more pics the other day, these levers are not as worn as in the Hotstart!
    4 points
  10. This will serve as an official announcement that we have released the TOGA Simulations MU-2 Marquise version 2.0.1 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.0.1 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! See all the v2.0.1 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.
    4 points
  11. Understand your sentiment Marc and many times, these bugs do seem silly, even to me. I'll keep fixing though and we'll get through this phase soon enough. -TomK
    4 points
  12. Back from Oshkosh Air Venture airshow. Thx for patience...I'm off and running again. http://togasim.com/mu2docs/release_log.html Slightly revised the bug tracker links at left side of page to be a bit more clear with regareds to versions. Also added new bug tracker page towards the V2.02 release for folks to follow along. -TomK
    4 points
  13. Kirk, In regards to the IRL engagement/use of the ATS, I've never heard of any technique or SOP whereupon TOGA is selected on the runway as the throttles are manually advanced through 25%. Would need more context to better understand. Typical SOP dictates we wait until taking the runway to select TOGA / N1 TO to avoid an unintended engagement of the ATS during taxi/ (although TOGA / N1 TO is often selected during taxi to the runway despite SOP) We can save that 'normalization of deviation' discussion for another day. 2 methods to engage ATS for TO that are commonly known or used IRL: (prerequisite = the ATS MSD indicates N1 TO) Slowly advance the power levels manually until ATS engagement (75% N1) - and thence let the ATS set TO thrust - with the PM checking that TO thrust has indeed been achieved by 80 knots. (most common). Press the ATS engagement button when on the runway and cleared for takeoff - and let the ATS take them all the way from idle up to TO thrust. (rare) My observation from your video is that you are advancing the thrust levers manually and quite aggressively compared to IRL. We do not advance the thrust levers that quickly. We also do not 'firewall' the throttles and rely on the ATS to trim or set power - that technique would probably trigger exceedances similar to your video. Reference this video from the 2 minute mark. I'd say this is very representative of a typical CL60 ATS takeoff IRL: From initial advancement of thrust levers to ATS engagement is about 7 seconds. (green lights illuminate either side ATS engagement button) Total time from initial advance of thrust levers to takeoff thrust is about 11 seconds. (vs about 4 seconds in your video) Time to 80 knots is about 14 seconds give or take. The point I'm moving towards is that ATS on this airframe was an afterthought/option that is not fully integrated. I think of the ATS as a 'helper' that has to be managed. The ATS IRL does some odd stuff - and we have to keep an eye on it. It often will overshoot the thrust targets, it won't keep up during approaches on gusty days, it won't keep up with speed changes, especially on the mach to IAS transition during descent. Then there's the airframe specific 'oddities' - such as ours where the throttles will split at low power settings triggering an occasional ATS disconnect. We have to help it / manage it quite a bit. The ATS limitations on the CL60 illustrate it's helper status. We can't use them for GA, CAT II, APR, steep approaches, or touch and goes. (to name a few, the list has 16 or so bullets) As such - relying on the ATS to trim thrust or prevent an exceedance on takeoff by firewalling the throttles - you're seeing what would probably happen IRL. I see you've troubleshot the ATS disengagement down to a saved state root cause - but if your goal is to emulate IRL technique - I hope this information will be helpful.
    4 points
  14. 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
    4 points
  15. There's a difference between a dev's time, and a customer choosing to be one of the few staying behind in X-Plane 11. That's ultimately your decision, but the explanation by @GridiroN was spot on. We will be implementing things like rain in XP 12. Making X-Plane 11 features that only work in OpenGL at this point is not a good use of developer time given the proximity of X-Plane 12. That's where 99% of the customers will be headed!
    4 points
  16. View File Hot Start Challenger 650 - OO-WEG This livery for the fabulous Hotstart Challenger 650 is adapted from a real world CL350 registered as OO-WEG. I hope you'll enjoy it. To install simply copy the "OO-WEG" Folder into xplane directory/Aircraft/X-Aviation/CL650/liveries Don't hesitate contacting me if you find errors or have suggestions in improving this repaint. Please do not redistribute this repaint without my permission. Submitter luke_1549 Submitted 07/16/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  
    4 points
  17. I thought it would be fun to add some RL pictures from time to time. . Here our Chaly is on the way in the Belgrade FIR.
    3 points
  18. Looking as new on the BBA tarmac in EGKB !
    3 points
  19. And another one, before start on the ground at EGKB
    3 points
  20. And here is another one, approaching SE Italy, sorry Rich but the chevrons are back!
    3 points
  21. Thank you Tom for bringing us this awesome new version of the Marquise. I'm toying around with it now for a couple of hours, and I simply love it. Had to leave this statement here so you don't think I'm just poking for bugs
    3 points
  22. Two things I've noticed right off the bat, 1. Toe brakes using default toe brake controls with saitek pedals don't really seem to hold at all. They will grab but not hold after the plane stops. 2. Default flaps axis assignment on a saitek throttle quadrant doesn't move the flaps. Any note on this? Fantastic airplane so far, only played with it for about an hour now but it sounds and flys (and looks!) amazing! Thank you!
    3 points
  23. Version 1.0.1

    46 downloads

    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 create a copy of the folder in the layers palette. This will save frustration if you wish to return to the original materials. Please read the included readme file.
    3 points
  24. For the early-birds https://forums.x-pilot.com/forums/topic/24825-toga-simulations-mu2-version-20-paint-kit-rc1/
    3 points
  25. Just a note to say Thank YOU! Took it for a spin this evening over the mountains towards Wenatchee, Washington.
    3 points
  26. Thx Alec. Its a process for sure. Being 'solo' on this particular project makes it a bit tough in that I have to spend time on the 3D whereas in the team scenario, someone could "improving the interface" during that time etc.. So my methodology is to get everything that is "tactile"..stuff you.see / touch / hear / operate.....get it so folks can fly it with their hardware....and then when all that's stable, I can start throwing in "luxuries".....GUIs...more prefs...failures....weight/balance stuff. etc. I mean...I love this thing..it'll get plenty of attention going forward still.
    3 points
  27. Dear All, I prefer to have my own reg num on my plane especially when I go on Pilotedge ;-) Also, while we wait for the official Paint Kit I have made a template for you to get your own reg with Photoshop: ie just change the reg num on the text field layers after downloading and installing the Google Font Karla. You will then need to convert the .png 24 you will export with Photoshop into a .dds file with Xgrinder (free). Enjoy, Cheers, C Exterior_3_ALB.psd
    3 points
  28. Man....I fooled everybody on version 1.x so I wouldn't have to model that complex front gear door!
    3 points
  29. 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
    3 points
  30. Better don't copy folders manually; there's an installer for the G500. Just follow the instructions provided in the manual
    3 points
  31. Version 1.0.2

    229 downloads

    This livery is based on a real Global Express, G-CEYL, which is operated by the charter company VOLUXIS. I had to adapt some of the stripes to better fit the Challenger, so this is not a totally accurate representation of the real aircraft, but it is as close as I could get it. For some extra flair, I have included custom normals with this livery to give it more of a semi-gloss finish. Enjoy!
    3 points
  32. Version 1.0.3

    790 downloads

    This is the official paintkit for the Hot Start Challenger 650. This paintkit assumes you have previous knowledge of painting in PSD (Photoshop) files and/or afphoto (Affinity Photo) files. DISCLAIMER: Upon opening the zip file containing the paintkit, you have agreed to the terms that follow. You may do ALMOST whatever you wish with these files. Create, share, modify, post on forums, all without restriction. You may NOT charge money for any textures created with these files. You may NOT sell this paintkit. (Unfortunately, it has to be stated.) If you choose to alter any files other than the empty layer between the Ambient Occlusion and Albedo layers, you do so at your own risk, and you do so, assuming you have made backups of the original textures. The only layer designed for changes or additions is the layer between the AO and Albedo layers. You may add as many empty layers as you wish, but make sure they are located between the AO and Albedo layers to achieve correct results. The wireframe layers that are included are a guide to the areas you can paint in. Anything outside of the wireframe is NOT to be painted on. If there are any questions, please visit the forums at forums.x-pilot.com or our discord. Happy painting!
    3 points
  33. Baggage door operation isn’t modelled/simulated in the current version as far as I’m aware.
    2 points
  34. Hi, Although not tested much, here is a configuration for the RXP GNS530W/430W for the Mu-2 GNS version. I've elected to connect fuel-flow and air-data to the 530, although I've not yet flight tested these. There's no auto-slew or OBS course-in as I couldn't get them to work. In addition, the GPSs are wired up to _replace_ the VOR signals when set to CDI mode. In lieu of some replumbing in the Mu-2 itself, I think this is the best I can do, but I'd be very happy to be corrected. At the very least, this gives you some starting coordinates for the panel rendering, which was a little tedious to calculate! DavidRealityXP.GNS.ini
    2 points
  35. Definity a bit subjective...in that some folks have described them as dim, etc....but I myself am in favor of 'more light' and its an easy tweak. I'll up the value until more people complain its too unrealistically bright than don't complain -TomK
    2 points
  36. Because there was a configuration designed for it to work with throttles 1,2 and 3. BUT other, highly desired preferences were not accomodated for a lot of users. In 2.01, I have accomodated this other functionality and in doing so, had to change the way the hardware is setup. HOWEVER.....with the new hardware assignments, The paradigms used in 2.0.0 can still be applied in 2.01 so the levers operate exactly the same as they did in 2.0.0 -TomK
    2 points
  37. I am inclined to go with your suggestion - it is true that we often had the left pack running because it was not only safer (and a bit more quiet) for the baggage handling personell, it would also cool the cockpit a bit better (at the expense of the cabin cooling ). So I noted your suggestion and will try to remember to implement it for the next update.
    2 points
  38. Version 2.4.1

    108 downloads

    Excel document replica of an aircraft technical log for logging flight and cycle data. This is logs 1-100, if you need more logs, just change the page number format to start at 101, 201, 301. etc and you will get a fresh set of 100 logs. I suggest keeping a blank file for the purpose of new logs.
    2 points
  39. Make sure you have CLB thrust selected, TO will blank passing FL150 and ATS will disengage as a result.
    2 points
  40. 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.
    2 points
  41. Thx Jerry, I put it in the Bug tracker for the Moo
    2 points
  42. I actually tried early on, but wasn't happy with either the sound samples I had....nor the hardware handling till last night The new throttle mappings will come out at the next update. With the implementation of the "TBM-style" throttle option, this will make implementing those sound much easier across differing configurations. So really its a matter of getting just the right samples...and once I have those, putting those sounds in is a 30 minute affair...at which point we can get it out to you guys. So yes...definitely on a short todo list. -TomK
    2 points
  43. I found that I can cover (nearly) all Linux users by providing one build for the Ubuntu and one for the Arch Linux distribution family. Unfortunately I haven't found a way yet to create a build catering to both, Ubuntu and Arch based distributions (experience gathered with the FSEconomy client). With the M1 architecture, Mac also adds an additional required build, bringing the total up to 5 builds (Win, Intel Mac, M1 Mac, Ubuntu, Arch).
    2 points
  44. I hope I'm posting this in the right place. If not, forgive me. I never knew this aircraft was so sexy. I'm learning to fly it and am enjoying all the quarks it presents. It's different from what I'm use to. If you haven't already, you guys gotta check out this video:
    2 points
  45. Do you by chance have a hardware switch bound to the default avionics on/off command? I ran into this on my first attempt...
    2 points
  46. No...this is definitely a bug on my end. ...verified. Glad you have the parking brake in the meantime till we get this updated! This is what I get for applying toe brakes during testing.....seeing the brake value go up and down and then walking away and going "ah, it works"...because I still have 1000 more things to test that day Great catch and definitely on the bug list. Thx for reporting. -TomK
    2 points
  47. Not at all. There is just a lot of logistics with regards to deploying a release. Its a process and we have a checklist and are working through it. Release is always an exciting time...but also a time to wisely 'slow down' just a bit and make sure we dont' miss something. We don't want to take off with our fuel valve set to OFF. -Tom
    2 points
  48. Recommended Videos: Reflected Reality Simulations: Preparation and Power Up Reflected Reality Simulations: Fuelling Foxtrot Alpha Aviation: Walkaround Foxtrot Alpha Aviation: Power Up APU and Electrical Foxtrot Alpha Aviation: Panel Checks and FMS Setup Foxtrot Alpha Aviation: Power Up Oxygen and Hydraulics Foxtrot Alpha Aviation: SPS, Radios and Avionics Foxtrot Alpha Aviation: EFIS Setup and Takeoff Briefing Foxtrot Alpha Aviation: Before Start, Start and After Start Foxtrot Alpha Aviation: Taxi Checks Foxtrot Alpha Aviation: Takeoff, Climb and Cruise Foxtrot Alpha Aviation: Weight and Balance
    2 points
  49. Version 1.0.0

    278 downloads

    A blank, white livery for the Hot Start Challenger 650. Suitable for use with Photoshop, paint.net, gimp etc.
    2 points
×
×
  • Create New...