Leaderboard

Hello all. Those who have followed know that the IXEG 737 develoment has been stagnant for a long time while I've worked on my MU-2 project and stabilize it after the release. That stabilization phase is nearly done. XP12 is imminent and I'll be porting the MU2 to XP12 beginning next week...and it should not be terribly long (I hope). After that, the 733 will move back into rotation as the primary focus of development with the port to v12 being the first priority. The IXEG is minimally operable in V12, but that's all we can say. We obviously had to make it baseline flyable in order to test/develop it with all the XP12 changes, which have yet to be addressed. As such, our official position for those who wish to try the V11 IXEG in V12 is "VFR joyriding only". I expect we'll set up a 'volunteer forum' where folks can give feedback as to their V12 observations as its better to have more eyes on this stuff; however, we request that nobody report any shortcomings of the V11 733 in V12. We are keenly aware of a lot of things that have to be changed....so we'll want to wait until we believe we've caught all we can find before other folks chime in; otherwise we'll end up with a massive stack of the same reports. So, certainly keep XP11 around if you wish to fly the IXEG seriously until we get it ported over. I've always kept "old version / new versions" side by side on my computer for these transitions. Long-time XP users know that after a major release to X-Plane, there is an inevitable debug period that goes on for some time, though many other devs have begun already, we're behind. ....but nice to have the process underway.....Below screenshot shows what the cockpit looks like in V12 daytime. -TomK

I have not officially begun to test / port the MU-2 to X-Plane 12; HOWEVER, I have been testing it regularly in X-Plane 12 and the good news is that it seems at first glance....to be mostly functional....FOR.....daytime flight. I say this because the biggest change in X-Plane 12 is the new atmospheric and lighting engine..and this requires new "directive commands" for lighting that were not present in X-Plane 11. The nightlighting is practically non-existent until I make the required changes. Also I have to make some notable changes to take advantage of the rain effects....so the V11 version "in V12" will not have the new windshield effects. So....daytime and dry seems to be mostly OK using the V11 version in V12. I know there are some turbine engine changes also I have yet to test...so unsure what their effect will be. The plan is to get the next release patch, 2.0.3 out for V11 (relatively imminent), and then begin the official port / testing process for V12. Probably will begin the work next Monday. I do not expect it to be terribly long. Chances are XP12 will go through some growing pains anyhow and I'll be right there alongside the process testing/tweaking the Moo. Experienced XP users should know to keep their XP11 versions around until they're fully happy with V12. Here's a few screenshots of the Moo in V12. Not terribly bad, but I may tweak it after I get going. Things tend to look a little bit shinier in V12...but also brighter, which is good.

Thx Pils, that's a good list, will definitely give those procedures a try..

Thanks for the update! Really looking forward to the next releases, the IXEG 737 is one of my personal favourites. With the help of some of your fellow custom FMS developers, we have been curating a list of instrument procedures that are “challenging” in some way or another for GPS navigators to follow correctly. I think you would find it a useful reference if you plan to delve deep into that part of the product. I am also open to any additions you might find! https://docs.google.com/spreadsheets/d/1MubloGDNCNSqmfNcQe5PmnvsAUF_FK8zYhmuSHa-UUw/edit?usp=sharing Good luck with the ongoing development!

“The APU load control valve (LCV) controls APU bleed air supply to the 10th-stage manifold. The LCV is an electrically controlled, pneumatically operated valve which either fully opens or closes. The valve is manually controlled by the APU LCV switch/light, located on the BLEED AIR panel.”

Hang in there...fixes are closed for the next release, but the docs are taking a bit. I'm writing docs on not only the GTN integration setup, but also a more indepth "SPZ-500 autopilot supplement" for newer folks...which I think is needed given this older autopilot integrated with new GPS units, etc. Soon as the docs are done, we'll package up the next update. -TK

So finally got this figured out. Originally, I could find no indication or documentation of when the SBY button should be illuminated or extinguished with no other modes active....mostly how do you extinguish the thing at all....so in the interim I tied it to the Flight director..which is of course ON when the other modes are active, which is why the SBY light shows with other modes active (clearly wrong). But the question remained about what powers the thing? i.e. can the SBY light ever be off during normal ops? So it turns out, being part of the SPZ-500 system, it initially illuminates whenever the Radio busses are powered, so its always READY to accept a flight director mode entry. Naturally then, it extinguishes only when the radio busses are powered off or other modes are active. This can be seen in the above video at 8:11 and 8:29, where during rollout, its clearly on (but the AP servos are not)....and when he pulls in to park, its off...but so is the GPS, indicating he flipped off the radio master switches. So during nominal operation, the SBY will always be lit when no other FD mode is active. This will be implemented in the next update patch. -TK

I did not see such selectable options through the RXP plug-in (only GTN 650 and 750)....may be I'm missing something. Besides, I do not think I would implement those (the bezels and controls) anyhow. Its enough managing all the panel variants I have as it is for the time being and the 650/750 have those GPS functionalities anyhow. -TK

If it is any help for some reason I had to re calibrate my rudder pedals and toe brakes after the update. I had the opposite problem, brakes were released but still showing activated on the calibration screen. Not sure why but a quick look at the calibration screen showed that something had changed and they need to be fixed. Quick re calibration and I was up and running.