Leaderboard

I suppose I should demonstrate some form of life. I'll have to get with Jan on that as our radar (best I recall) had most of the features of the real thing. As far as "coming out soon", here's what I'll say....and this is overdue for sure....and I'm not going to convince anyone to believe me or not on the timing. It will get looked at and updated at some point. As sure as this is my 20th year actively involved in X-Plane work, it will continue to be so. A year and a half ago, things changed for me when Laminar announced its new store initiative in Montreal. I took a job with Laminar to completely rewrite its developer documentation. This was a "look to the future" for both myself and X-Plane, at the cost of 'now'. Laminar are looking to embrace a future generation of developers and we need to have better learning materials to engage this generation to develop for X-Plane, so I'm that guy....thats for Laminar. For myself, I needed more stability and a cushion, as the add-on market for X-Plane is still too thin to have any kind of long term security. Taking on this work with Laminar has allowed me to close out all other obligations and stay in the X-Plane ecosystem for the foreseeable future. The 'problem' for my customers and X-Aviation thus far, is that the initial phase or work to revamp and deploy the documentation was/is huge. New developer web site, new manual formats, a new, interactive PlaneMaker manual, lots and lots of rewriting, new illustrations...etc....and that has taken a good while to develop and received all my focus to get to what we call the "initial deployment" of the docs out the door. That initial deploy is not terribly far off. After the initial deployment, I will settle into a more regular time schedule that will afford me the time to get back to my own work. It has been my effort over the last year to try and achieve a point where I can only work on X-Plane endeavors between now and my retirment......and there have been personal hurdles along the way that are neither anyone's concern or business, but real to me just the same. It is my intention to crack open the MU2 and 737 again in early October, to resume work on my 'X-Aviation' things. I have discussed this with X-Aviation also. Between now and then I am focused on getting an initial deployment of the new docs out the door for Laminar. We will look at the IXEG radar early on for sure. I want to remain developing for X-Plane fully and it is my firm belief that this path i've taken was the required path to do so, and I apologize for the silence and delays. -tkyler

zzz....oh man...just woke up after a 18 month hibernation! Seriously....Nothing is forgotten, only life has happened. Here's a quick summary: Spent last 18-24 months in a significant life transition as I approach and prepare for retirement. Lots of loose ends to tie up and leave in the past. I now work full time for Laminar, a big change...and I have been positioning myself to stay in X-Plane work exclusively for the future. I'm wrapping up a 2-year private contract for the BETA ALIA production aircraft (which will be in X-Plane). I'll complete that work next month. Gizmo based code in all my products is nearing end of life and had complicated the update process due to the volume of code to rewrite......however AI has enabled a path to relearn concepts & rewrite the code as its become "X-Plane SDK aware" in the last year...This reduces the effort drastically and is a major catalyst. No fees for future updates on the MU2 or IXEG when they eventually go out. Updates will always be free for existing customers. They've earned that. After ALIA delivery, I'll return to push an update to the MU2 with the Gizmo code-base....I won't get OCD....I'll just push what I have, which is a good amount. After MU2 update, I begin code rewrites to serve as my future code platform for the MU2, IXEG and the forth-coming 717. This is foundational and absolutely required to guarantee long term compatibility for these products. Those aircraft will be the only three products I will maintain into retirement and beyond. That's the highlights. This gap in work has been all about my focus and preparation to sustain myself after retirement, and stay within the X-Plane ecosphere in the process.

Hello All, This will serve as an official announcement that we have released update version 1.9 for the CL650. All customers who have purchased the CL650 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 CL650 from today forward, your purchased download will already be updated to version 1.9 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 Challenger 650 download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: Release Highlights: Fixed various manipulators being reversed on the overhead Particle effect luminosity is incorrectly set in XP12 making them appear extremely bright Rewrote large portions of shared cockpit to allow for multi-crew, passengers, spectators and a much simpler setup process (documentation forthcoming) Engaging the yaw dampers requires holding the buttons down for a couple of seconds As we no longer utilize Gizmo, Mac ARM support is now complete and Mac users should stop running X-Plane through Rosetta if you don't have any other products which require Gizmo (the installer will point them out if you do). Improvements: 4536: Add support for rudder and steering control using only keyboard & mouse 4565: Add support for SayIntentions and custom ACARS service provider URLs 4569: Retune AP flap constants to avoid excessive altitude excursions 4573: Refactor pitch FMA mode to hold the commanded attitude more tightly 4577: Implement persistent logging of CB pop reason 4589: Add waypoint description codes introduced in ARINC 424-20 4590: Switch to reduced bank angle for hold path at FL316 not FL245 4593: Update world magnetic coefficients to 2025 4606: Implement gRPC API 4629: Workaround for weak X-Plane's aileron effectiveness at low airspeeds 4643: Switch to using nvcompress for DDS generation (better texture colors) 4649: Implement compressed normal maps for XP12 4600: Add support for new combined wheelbrake axis 4468: Stab/mach trim and yaw damper buttons must be held down to engage 4698: Expand shared cockpit to allow for multiple concurrent connections and easier setup Bugfixes: 4535: Typo in pressurization study screen tooltip 4538: Crash on XP11 when aviationweather.gov returns zero METARs for an airport 4537: Mouse yoke breaks on 3rd party airplanes if the CL650 was loaded previously 4539: Module boot time variation is producing doubled audio on startup from DCU and PSEU 4534: FAA obstacle database not decompressing correctly due to ZIP version change 4541: Remove IRU debug logging on release builds 4542: Typo in AFCS visualizer reads "Nm/s" when it should say "Nm" 4543: Deleting last leg of an airway in LEGS when preceding and following legs are discontinuities can crash 4545: AC AUTOXFER FAIL indications on MFD synoptic page should be driven directly by CAS trigger 4546: Recompute a vertical direct-to on mod exec 4547: On executing vertical direct-to, disable the NO VPATH-PILOT CMD suppression 4372: Sporadic and spurious NOT IN DATABASE messages 4551: Bad memory allocation in DCU wire-to-lamp definition parsing code 4556: CTD due to phys.c assertion in atmos_main for shared cockpit guest in X-Plane 11 4558: Harden netcode against ingesting values too large to represent as an FP16 4552: Various manipulators are reversed in latest stable release 4563: VTBS has overflowed the maximum number of SIDs (200) causing a crash when attempting to pick a SID in DEP/ARR DEPARTURE 4571: CTD due to assertion "abus_isval(tod_pause.time2tod)" failed 4574: NWS actuator shoudn't be feeding off the inboard brake hydraulic line 4582: Regression: fix for 0004495 broke AIRWAY INTERSECTION page's ability to automatically resolve the intersection 4583: earth_nav.dat parser needs to normalize whitespace before line splitting 4584: Fix heat damage on engine isn't fixing damage from engine fires 4585: DataRefTool crashes trying to immediately read our datarefs before their setup is completed 4592: FDR data incorrectly labels stick shaker signal as pilot-commanded AP disconnection signal 4595: MFD display reversion is erroneously triggering MFD XTLK flag 4607: Aircraft contrail particle effects are broken in XP12 4608: KLAX ORCKA5 produces spurious UNABLE FPLN ALT due to short leg sequence across discontinuity 4610: FCU clogged failure can cause crash due to incorrect meter_valve_rat clamping 4624: IF legs need to be stripped out when following an enroute transition that bypasses them 4493: Linux with AMD GPU without Zink is borked on latest beta build Object Fixes: Main Panels1.obj Dsus fastener positions fixed on right side panel. Object Fixes: Nose Gear Bay.obj Mesh added to fill in gaps around edges of opening. 4625: NOT ON INTERCEPT TRACK is coded completely wrong 4626: Increase XTALK FAIL message time delay to 10 seconds 4627: SBAS VPL should be ignored when flying an approach in RNP mode 4602: Anti-ice fluid on wings not visible from inside 4628: Refactor nose door implementation to properly route through relay K4GA 4631: Tie amber generator circles on the AC synoptic page to corresponding GEN OFF CAS messages 4632: Use tighter holding pattern radii at all altitudes 4636: PPOS flight plan disappears from PFDs 4 seconds after selecting PFD reversion 4638: phys subsystem still references rucsoundings 4639: Incorrect LPV vertical path construction 4640: Harden LTP and FPAP access functions to bad data 2452: FIX page symbology not showing on MFD when SEC FPLN showing on MFD 4650: NAV LTS breaker has the wrong rating 4651: Stop hard-depending on stock X-Plane commands existing 3938: Updating DIRECT-TO NEAREST AIRPORTS's MIN RWY does not require UPDATE AIRPORTS to be selected 4118: Existing waypoints should be dropped when changing flight plan via Direct-To NEAREST AIRPORTS 4369: XP11 version of ACF is missing instrument label and CB collar OBJs 4385: Updated hint images with all corrections to Jan 2024 4548: Change hint image loader to accept RGB formatted images 4503: Update "more info" links to use CL650/Study prefix 4434: Engaging AP while FLC is active should sync speed target to current speed 3141: Pressing Left LSK for RX fix (visual approach) should put pre-constructed PBD into scratchpad 4654: Pilot-defined waypoints do not properly initialize pbd.src field 4656: Stabilizer trim runaway failure cannot be interrupted by disengaging stabilizer trim 4657: Remove "CVR" failure from 24-Elec 4660: Failures.txt documentation mistakes 4570: Regression? When IF is not aligned with FAC, APPR LNV wrongly flies FAC 4661: Don't show CHECK LOC TUNING when on missed approach 4668: Attempting TTS on Arch Linux with no festival(1) binary present crashes X-Plane with SIGSEGV 4673: Along-track waypoint doesn't use the correct inbound course on direct-to leg 4674: Compute VDEV even when track angle error exceeds capture limit 4675: Retuned ISI attitude finding to produce less pitch error while in hold 4670: Avionics should default to inches of mercury rather than hPa 4684: Implement missing failures 4695: Retune XP12 cabin lighting 4696: Harden the AIRAC parser against invalid altitude constraints causing a crash 4710: Crash on XP12.4.1 due to hard limits on not querying datarefs from background threads 4711: FCC 1B/2A status study screens are mislabeled 4712: LDU channel label in failure description is incorrect 4715: X-Plane 12.4 requires instances to be created from pre-flightloop callbacks 4720: Triggering auto-FO checklists crashes on X-Plane 12.4.1 4722: X-Plane 12.4.1 breaks popup panels due to XPLMFindCommand being invoked from background thread 4778: Reloading while in a hold pattern will reset the hold pattern state and perform hold entry again, 4779: Implement a HOLD DEBUG screen, 4768: Regression: with a lot of crosswind at high altitude, hold pattern tracking gets confused on the outbound leg 4771: Add data ref to indicate shared cockpit role of user 4520: In shared cockpit throttle control is susceptible to jittering 4810: Readjust panel lighting levels to match XP12.3 and later changes 4140: Generator transfers trip off stab & mach trim Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.

Sorry I didn't see this thread until now, but when the TDS was first released for XP I made this plugin that tricks the MU-2 into thinking RXP is present and loads the TDS. Fake RXP.zip

If you hear nothing from us, assume that the project is not abandoned but no work has been done on it that would warrant us sharing any progress info. If we abandon the project, we will announce this here - so if we don´t - you know it´s not abandoned.

Model is finished. Textures are finished. Saso is doing his best to take care of minor issues with the 650, one of which is getting the weather radar added to it. Once he finishes those, he'll send me a new TBM build so I can start initial testing in X-Plane 12 with animations and making sure textures look good. To sum up, as of this post, all artwork is considered done.

Really? If any feature warranted deploying an update, this would be it.

This is absolutely NOT true. It's just their technical support team using canned responses to get rid of you. If you run the installer with --install_name="X-Plane 12.4.0-r2-9b69b91a" command line option then it will downgrade when you select "Update X-Plane."

As much as I can understand the wish for some update to this feature or that - if someone wants "a flight model update" it makes me think he just wants an update because updates are cool (and perceived as additional value). Something that is fine does not need an update.

This will serve as an official announcement that we have released the version 2.2.2 update for the SR22 G1000 Series. All customers who have purchased the SR22 G1000 Series 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 SR22 G1000 Series from today forward, your purchased download will already be updated to version 2.2.2 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 SR22 G1000 Series download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: Bug Fixes and Improvements: X-Plane 12.4 / 12.4.1 adjustments and updated dataref usage Latest physics engine Spark plugs will revert to clean status when wear/maintenance system is disabled (previously whatever state they were in before when disabling was kept) Fuel lines are primed by default when persistent systems are turned off Disabled fuel sloshing on ground Expedite priming process until fuel flow registers during engine start Adjusted turbocharger bearing drag and fluctuations near idle (SR22TN) Tuned fuselage Cd for more accurate speeds in pattern environment (SR22) Adjust positive fuel flow with low boost and engine off Replacement of deprecated datarefs Updated libraries and dependencies Adjusted prop disc behavior FMOD Volume adjustments and minor sound tuning Fix error where certain degraded networks lead to stuck loading of aircraft 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.

We can't INSTANTLY come out with an update when a new version of X-Plane comes out. As much as we want to, it's unreasonable to expect that from anyone. In the X-Plane world, many developers always recommend to keep 2 installations of X-Plane. A stable version and a beta. Regarding the Challenger update...we're currently on beta 3 within 1 week. That beta is in the hands of our testers. 3 beta's in 1 week is quite fast. There are only 2 of us on the Hot Start team. We can't work on two products at the same time, so while the Challenger is getting updated, we're going to ask people to continue to be patient for the TBM. If you expect an update in the next week or two, all I can tell you is the update will be out when it's done. We want it out as much as you do. But it doesn't make sense to put out an update that isn't ready. Whatever you think about the situation is entirely your opinion. It will have no influence on how fast the updates get done.

It's not worth doing. Laminar can instruct you on how to downgrade if you contact them. We hope to have an update out on our end within the next week or two.

I will be the one to bring it up, is the tbm900 still being worked on for release to x-plane 12, and can we get any kind of update on its progress?

Apologies for the late reply. I'm working on a large update for the DC3. I'll make a note of this and address it.

Still no new for the XP12 and specifically 12.3.1 upgrade ? at least now we can expect the new real weather wx radar ;-) For turbine fan, in addition of the XP12 EPIC1000 and PC12, a Piper M500 XP12 should be released rather soon

Tkyler, Appreciate the update on your activities with Laminar. That is good news for everyone using XP. Look forward to your future work with the B737! Thanks! Rich Boll

Man, its a shame this project never materialized into what it was supposed to become. I used to love flying the ixeg in xp11 and had high hopes it would be completed. Every now and then I check back on this forum to see if anything has changed and unfortunately still nothing. Xp12 is looking seriously good these days, I just wish the ixeg 737 was up to par because it has huge potential.

Quite some time ago, but tried it as shown in your video and good enough for me

It's not dead at all!. Before I say this, a bit of disclosure. I AM NOT involved with IXEG, and I will not discuss or mention details/plans I will let official channels do so. I met Tom at FSExpo this past year in PVD and had a good hour long discussion with him about (mostly) the 737 we all love. NO IT'S NOT DEAD. He discussed details with me that if he wishes to share one day he can, but it's not my story to tell. But it's a VERY interesting story at that!. You folks would not believe the dark side of developing that happens. Like many of you, I too have been frustrated with the 737, but after talking to Tom at Expo, I can say I heard it from the horses mouth, THE 737 IS STILL BEING WORKED ON!!! Again I won't discuss what Tom discussed with me about what's being worked on. ALso @tkyler I would like to thank you again for you time at expo, was an absolute pleasure meeting and talking!

First time I’ve tried it in XP12. Plane is ok for me in XP 12.2 beta 6. I have yet to do a long flight but I’ll report back, but so far sounds are great, controls are great, loading/fuel worlds, RXP 530 works. Lighting seems perfect so far. I’ll try some other loacations. Only things that seem amiss are to do with the aircon and possibly the de-icing but I haven’t used it in years so that might just be me. I must say, given that it is absolutely flyable and without literally any graphical glitches for me in 12.2, I cannot for the life of me understand why it hasn’t been updated. Like, how long would it reasonably take to slap a compatibility update on this thing? I’d pay for it. Others would also pay if this thread is anything to go by. It’s a unique plane in X-Plane both aesthetically and in terms of the airlines that still use it and it genuinely sucks that we still don’t have it ‘officially’. Thanks *oh I guess technically the windshield is ‘dirty’ or has permanent rain drops on it but that’s minor to the point that I don’t even know if I can be bothered fixing it.

Made up stories from a dramatic streamer. Nothing new.

@jrsaez82 I know its been a long time since i've messed with the MU-2, but I expect to come back around to it within the next 2 months and start pointing it to the future. I'll make an announcement and explain the timings and future at that time. There is a lot of really good and positive developments going on behind the scenes at Laminar, which I'm involved in....and for the better. Quite a bit has changed with regards to the flight model and electrical system models and I fully suspect that Philipp may have put some type of criteria on enabling the various AP modes based on more advanced "amp flow" and voltage models that he implemented well after I coded these systems up....so its absolutely incumbent upon me to find out what those are and bring this thing up to speed. As silent as i've been here, I honestly have never been more involved with X-Plane than I am today....and I am fortunately being able to contribute to overcoming the impediments that have historically caused delay headaches for devs forever, including me. We've been asking the questions internally, "what slows devs down and makes it hard to update and test" and are engineering solutions for that....something that has been sorely needed for a long time.

Yes.

Hi, do you guys have a timeline on the update? I'm curious if I should buy the steam version so I can go back to 12.4.0.

Thanks. We know. A beta to fix will be out soon. (See numerous other threads.)

Laminar released the current stable version of X-Plane 12.4.1 today on which the current version 1.8 of HotStart Challenger 650 crashes with the error "Threading violation calling XPLMGetDatad". Loading the TorqueSim SR-22 crashes with the same error. The release notes of X-Plane even state the issue. I hope this gets fixed soon as there is no way of getting an older X-Plane version on new installations.

https://support.x-aviation.com/knowledgebase.php?article=7

Once Laminar Research releases its new documentation for users and devs, I believe you can expect renewed activity on the IXEG.

You obviously haven't been to our discord where we answer countless questions. The 2 most common ones? When is the 650 update coming out and when is the TBM update coming out. Both questions are always politely answered. Your comment is out of line and not true.

Correct. Challenger is top priority. Saso has done some amazing work on it.

Coop updated the changelog yesterday - this is fixed in v1.1, which is currently in testing... so hopefully will be in our hands quite soon! https://c.leco.mp/EoWMWWqLdRbZfU

Unfortunately any time that X-Plane does the "loading flight" screen it resets the livery to whatever you selected on the initial flight configuration. You could consider reporting that as a bug to LR. *shrug* I would sometimes do this so I wrote a script to maintain the time at which I paused the sim when resuming. https://github.com/pilsnerish/FlyWithLua-Scripts/blob/main/PauseResume.lua

View File NAV Canada (fictional) Do not hesitate if you find glitches. Enjoy ! Submitter Christophe Submitted 12/26/2025 Category Hot Start Challenger 650  

Edited to add: disregard the question below, but I'll leave this in case it helps others. After creating a Combination 2 and quitting and restarting X-Plane, Combination 2 is now an option for a keyboard shortcut target. ----- Great add on! Is it possible to set a keyboard shortcut to any combinations other than CL650:panel_combination:Combination 1? I can add multiple combinations to access via the Challenger 650 -> Panel Combinations menu, but only Combination 1 shows up as a keyboard shortcut option. Thanks!

Would be wonderful to know if the team is working on the new 12.3 weather radar implementation for the 737. Will definitely look forward to it!

That is absolutely your prerogative. Some say minimal activity and updates indicate a lack of care by the developers, others say minimal activity and updates indicate a mature product that is not in need of them. As a developer I am partial, of course - but I personally still love playing games that have not had updates in decades, like the car I am driving, and both work fine. Ultimately I think the conclusion constant updates = high value is false, in fact some of my games that get constant updates leave me with the feeling that I "rather hold off playing them until they are done". Just my 2cts .

I respectfully disagree. The lack of any weather radar functionality in the CL650 had made me temporarily shelve the aircraft. Too many times I got torn up in some CBs because I couldn't see them at night. WXR is the feature that many of us have been eagerly waiting for. I want to fly her again in all weather conditions.

Because it has shrunk (and was publicly stated so quite a while ago).

Still things to come, and you're right, X-Plane 12 is looking great!

I've flown the B733 a few times since this conversation started back up. Even without any updates, I found the Vnav and Lnav to be incredibly stable. The aircraft, even in its current state, is a lot of fun to fly. There's no harm in giving the developer a gentle nudge requesting the status of updates. The harm here is accusing the dev of completely abandoning the project, which, in my understanding, is not true. In my years of living, and trust me, I've got many years under my belt, I've found that I can generally catch more bees with honey, rather than vinegar.

Can we therefore agree that it would be mutually beneficial if the IXEG team posted status updates from time to time? So that customers don't conclude that the aircraft has become "abandonware" and so there is awareness that issues are being worked on? It's not unreasonable to provide an update every 6 months or so - "Hi guys, the work on version 1.6 is proceeding steadily, our priorities are recoding of the FMS and recording of engine sounds. Lots of work still remains with FMS rework, we've tackled 10000 lines but there is still 600000 to go. This will address some of the VNAV issues of previous versions. We've rerecorded some of the auxilliary sounds. We're hoping to work on some improvements to the cockpit texturing but that's aimed at future updates". The amount of time it takes for a post like that to be collated and written and it'll reduce the backwards and forwards, misunderstandings, wrong assumptions, arguments and offence. People will no doubt say "is there any update" - quote the latest update and say "Our last update remains accurate - work is still ongoing. There is not much else to say"

Hi, @Cameron I’d like to clarify something. At no point was I disrespectful in my wording. Using terms like “abandoned” or “disregard” was not meant as a personal attack, but rather as an honest reflection of how the situation looks and feels from a paying customer’s perspective. I believe constructive discussion includes not only praise, but also criticism...sometimes strong criticis, especially when issues remain unresolved for years. Expecting customers to tone down their language to a point where frustration cannot even be expressed seems unreasonable. I respect the work behind the scenes, but I also ask for the same respect in allowing honest, even if firm, feedback.

That’s all very nice to hear, but as paying customers, we’ve been listening to “behind the scenes stories” for years while the aircraft remains broken, outdated, and without proper updates. Promises, secret details, or “trust me, it’s being worked on” don’t change the reality: the IXEG 733 has been in the same state since its rushed XP12 release, leaving customers with a paid product that feels abandoned. Transparency and real communication through official channels would speak louder than any private conversation.

YES! I FINALLY found the fix in the net after HOURS of search. Now I can normally exit the game and go to the settings menu WITHOUT to kill the process... Here is the solution written:https://forums.x-plane.org/forums/topic/325851-xp-1213-4-on-linux-freeze-not-ctd-on-exit/#comment-2864294 and here https://forums.x-plane.org/forums/topic/326955-x-plane-12-hangs-on-exit-linux/ I only needed to run sudo ln -s /bin/true /usr/bin/pulseaudio I am still learning linux but I think its an symbol link creation... Linux wizardry that I want to learn and thats an very good thread to start learning some things hehe Thanky to you all for trying to help me. Have an nice flight :-) EDIT: So naturally I can now access the CL650 settings :-)

I lost my faith in this XP12 project ...

Eventually, yes.

@Cameron Hello! How are you? Several of us are waiting for an update on this metal bird. Is there any way to find out about Take Command!'s future plans and its updates for X-plane 12? Thank you very much.

Hi @imemyself it has been a while for sure and a valid question and I have no real excuse. The last year has very much been a "foundational stabilization" year. I'm getting close enough to retirement to start eyeballing these next 6 years and how to best navigate them after the Covid ripples upended several things in my life. A year ago this time I had an opportunity with Laminar once again and I took it....the previous years since Covid were a bit rocky and I had some catching up to do, which I have mostly done over the last 12 months. I've spent sporadic moments in the year working on the 737 FMOD conversion and we're in final sound testing on that. The MU2 has taken a back seat during this time. I have recently integrated X-Plane's new weather radar and most of the known issues are fixed, which you guys won't see till 12.4 or 12.5 perhaps, so I have been chipping on it. An update absolutely will be available and it is still maintained and will be for years to come I suspect. I took the gig with Laminar to "stay in the X-Plane ecosphere" and some important personal things have transpired this year that should clear the way for more XP work. I know that's pretty hollow talk considering the last year, but I'll just wrap up by saying there are no plans for me to abandon the MU2 and I get reminded about it frequently...so the pressure is on and felt.

And if I may add my 2-cents worth... that is a smart policy. So many developers (including XPlane/Laminar Research) lately are issuing incomplete "beta" products, thus turning their paying customers into unpaid testers for products still in development. I much prefer to be patient and wait until all, or most, or the bugs are ironed out and the product works according to the developer's plan. There will still be tweaks and adjustments but that way the customer is assured of getting something reasonably close to what they paid for.

When the APU encounters a fault, you'll need to hop out of the plane and reset the APU ECU to clear the fault. Go to the tail of the aircraft near the cargo door, pop the latches and pull the little door open under the left engine nacelle: Inside you'll find a panel with 3 buttons. Push the "RESET" button, close it up and you should be good: