Leaderboard

Half-baked update? I flew this 737 today and even with all the X-Plane 12 updates since the IXEG's last update, it still flies nicely. Maybe a few quirks, but certainly not "half-baked". It followed my flight plan perfectly, LNAV, VNAV, Auto Throttle and Autopilot all worked as they were supposed to, landed nicely (although a little firm), but in all was a good flight and good experience.

Cannot reproduce. Here's XP12.1.2-b1 with precipitation intensity at about 10% (light), 40% (moderate) and 100% (severe). Seems to be working fine to me:

I have, unfortunately. XP11 is too long in the tooth for me now and - despite looking - I just can't find ANY other plane that appeals to me; I'd rather stick pins in my eyeballs than fly heavy jets - and available GA aircraft are either ridiculously slow or ridiculously badly designed. So at this point I've just given up simming and am using the time to get some hiking in which - truth be told - is probably better for my 63 year old health anyway ... I appreciate that the TBM authors also have other priorities, but I'd be lying if I said I wasn't disappointed in the time it's taking; I'm wanting results, not explanations. I'd happily buy it again if it sped the process up.

Hi guys, @rkuhlmann is right about communication...guilty as charged for being too quiet. The 733 isn't dead. We will continue to work on it as able, and best I can tell, probably have free updates for as long as I can foresee (whenever those may be). For my MU2 customers who have watched me keep the MU2 relevant through X-Plane versions 7, 8, 9, 10, 11, and 12 over 19 years, you know what I'm talking about. (even though its been a while since the last update and I'm literally 99% done with the next one but need to get it out There have been things beyond our control that have made update efforts challenging (shit rolling downhill kind of things)...which you guys don't see, nor will I talk about, nor should you care about, but we have to deal with just the same. Not an excuse, an explanation. I acknowledge that communicating is something we could do better and I'm sorry about that. As I've said many times, my committment has always been to keep facing forward and never sit down and that's still the case. So ....open communication time.....where's my time at the moment? I'm working for Laminar again. I am rewriting their documentation set for developers to help train and enable more developers for X-Plane. This initiative began in February at the X-Plane dev conference and I've been in the midst of a heavy 'front loaded' time effort to build the infrastructure for these docs and there's some slight pressure to "show anything at FSExpo". For consumers (rather than devs), this doesn't mean anything.... I know that doesn't make anyone here feel better or fix their concerns now, but is the road I had to take to preserve my ability to work on the IXEG in any capacity into the future. I do foresee time to work on the IXEG again after a few more milestones are reached with Laminar....indeed I'm meeting with some folks at FSExpo to discuss ways for them to assist in the effort. I am committed to maintaining the aircraft, even though I'm not sure exactly when updates will be. We have a plan, we try and stick with it, sometimes we slip, but we have never "forgotten about it". I like to say the IXEG is "perpetually in my inbox". Roadmap is the FMOD sound conversions still....and then the system updates. I am sure I'll have to repeat this later, but the "updates" period will also be quite lengthy because of the aforementioned (shit rolling downhill) situation I have to deal with. Getting through this phase is akin to the large efforts required to bring the IXEG to V12 and was unforseen, but its here on my doorstep just the same. Trudging through it, complaints and all, is the only way to ensure the IXEG survives into the future and those updates eventually come. The IXEG still has a lot of old tech and rebuilding it completely anew is a big task. I'm sorry again about the silence. -tkyler

The real aircraft is configured for Kilograms or Pounds and Feet or Meters in a device called the "Configuration and Strapping Unit". To set these options on your simulated Challenger, go into the Airframe Manager, choose Edit Options, and look at the CSU tab. The setting is per-airframe, so you can have both metric and US customary airframes. This option is available in Career Mode - the airframe in Non-persistent mode is only available as it leaves the factory, in pounds and feet.

This post should be pinned.

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: