Leaderboard

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.

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.

I found that the MU-2 GLASS (+ G500) needs BOTH the Gizmo and the X-Aviation DRM plugins installed / enabled. I use xOrganizer and had the X-Aviation plugin disabled (as the MU-2 is Gizmo still). In that case there is no error message, but the G500 simply stays dark. So, reinstall of course installs fresh (and "enabled") copies of those plugins, but it should not be needed if you just make sure both Gizmo and X-Aviation plugins are enabled at runtime.

This will serve as an official announcement that we have released the Version 1.1.0 update for the Take Command! CitationJet 525. All customers who have purchased the CitationJet 525 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 CitationJet 525 from today forward, your purchased download will already be updated to version 1.1.0 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 Take Command! CitationJet 525 download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: New Features: Integrated weather radar featuring the RDR-2000! Many thanks to Amy Parent and the Laminar team for such an amazing addition to X-Plane. Library and code adjustments throughout to fully support X-Plane 12.4 Updated and improved FMOD sound pack Improved and tweaked objects, textures, and animations throughout Bug Fixes and Improvements: Latest UNS-1 version (v1.22) Fix crash when the last airport in the flight plan is on a FM leg. Fix dates incorrectly formatted (month off by one after april, #72). Fix distance computation of arc (AF, RF) legs. Fix times displayed with 60 minutes past the hour (XX:60) in some situations. PVOR now pre-fills inbound track for runways picked from list. Fix PVOR using true runway heading rather than magnetic. Fix bad localizer front course parsing leading to off-course CF legs. Fix VOR and LOC database declination not used for CF legs computation. Fix standby resume failing to restore flight plan when using “radial/radial” custom waypoints (#76). Latest version of libradio to fix X-Plane 12.4+ compatibility Adjusted base system library with ordering fixes Replace deprecated dataref usage Adjusted particle system dynamics Migrate to new X-Plane chock system, fix rolling away on ground Fixed missing altitude minimum alerter, 500ft Improved accuracy of EHSI color schema Fix buggy DME behavior for speed/time, with improved alpha/beta filtering Transponder code, flaps, and fuel persistence Improve custom tail system handling with missing fonts Fix bus for flood light Add nose and aft cargo lights Fix handling for COM1 to be usable with EMER battery Flood light correct electrical bus 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.

Likewise, there are several other place where lower case "GTNXi" is used, which is causing the other buttons and decoder knobs on the bezel to not work. Also the counter clockwise on the outer knob of the left unit (after the above case sensitive fix) does not work. TDS/GTNXI/FMS_OUTER_CW_1 TDS/GTNXI/FMS_INNER_CCW_1 (the bold part should be OUTER)

There's a bug with the Direct-To buttons for the GTNX units in v1.1.0. Discord user Slartibart has found the fix: > `GTNXi` needs to be replaced by `GTNXI` in the file `objects/525_CLICKABLES.obj` > Looks like the commands, eg `TDS/GTNXI/DTO_1`, are case-sensitive. Pending an official update, this can be fixed by the user. Back up the file first, then open it with any good text editor e.g. Notepad++, then find and replace GTNXi with GTNXI. Any problems, replace your modified .obj with the backup and try again before asking for official support.

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.

Most expensive plane and most advanced plane i own and the only one that has not updated it's radar...lol every other developer has already a sucker born every day ya got me i fell for it

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.

It's disappointing to buy an aircraft that the developer claims to be the most complete for X-Plane 11 (possibly the most expensive as well) and see that it doesn't have a working weather radar, performance calculator and other things that ALL other aircrafts have (even the freeware ones). I'm very disappointed.

Jet manufacturers typically do not allow the AFM and QRH manuals to be published online for anyone to use. I have a copy of the real manuals through work (and no, I can't pass it along...). What has been provided by Hotstart is sufficient.

NEVER EVER EVER EVER ask a developer for ANY status on a product you spend your money on..rookie developers do not want ANY accountability to answer questions from us measly peasants that buy their product, give them your money and do not ask questions that is their attitude. they advertise the most realistic most expensive addon missing a key features . I understand xp did not have the code at the time but they do now and to not even tell or give people a roadmap or anything then give a smart ass condescending attitude when asked is unacceptable. I lose all respect for developers with Attitude it is unnecessary. I am not singling this product MANY MANY do this.