Leaderboard

Hello All, This will serve as an official announcement that we have released the version 1.5.2 update for the Take Command! IXEG 737 Classic Plus. All customers who have purchased the IXEG 737 Classic Plus 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 IXEG 737 Classic Plus from today forward, your purchased download will already be updated to version 1.5.2 for you. IXEG also has a new website documenting changes, so click here if you'd like to keep continually updated! 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 IXEG 737 Classic download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: Bug fixes: Wing light didn't show with winglets. Also, wing light source wasn't visible Eyebrow window preference was not getting saved Transponder was not reporting altitude (mode C). Updated to use XP12 mode enumerations Incorrect lat/lon representation on CDU Duplicates / Disambiguation CDU page No button click sound on CDU CLR keys MCP Panel Lighting Removed the DDS texture, incorporated spills and PM effect Improvements: IAS speedbug manipulators now of the rotate type. Drag mouse around the IAS bezel to move speed bugs. Much more natural. Additions: Added preference to synchronize CPT and FO speedbugs and altimeter bug setting. Added preference to set the plastic speed bugs to Vspeeds automatically (for VR users, disables manual control) Added the following new commands ixeg/733/show_settings_window ixeg/733/close_settings_window // will auto-save prefs when closing ixeg/733/toggle_settings_window sim/flight_controls/landing_gear_off // default command now moves LG lever to OFF when able (not always able) New GUI elements in the PREFLIGHT panel for fueling & flight planning As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support!

@Stephan737 It turns out that we DO override the default conditions for the arming of the RTO mode. You found a bug in the way we do that, thank you! The default RTO mode is armed when the thrust levers are > 0.5... so the default 737 will also trigger it when you reject the takeoff at 30 kts. We override this to require a speed of > 90kts (I changed this to 88 now), but we ALSO required the thrust levers to be at < 0.2! This is the mistake, because when Nils or Tom coded this, they thought that "yeah, the lever needs to be near idle for RTO to trigger...". But we do not TRIGGER the RTO mode, we just ARM it. And to TRIGGER it, X-Plane want the levers to be at >0.5. So effectively you have to "double pump" the thrust levers to get the RTO function on our model. Once back to "arm" the RTO, then forward and back to "trigger it". I never noticed because on my tests because I also immediately used max reverse like I was trained - which overrides this system and triggers the RTO mode anyway. This will be fixed in the next updat. The secondary problem of "RTO triggering again when trying to taxi" can be avoided by not pushing the thrust levers past 0.5. If you heed the maximum N1 of 40% during taxiing, this should not happen. However I need to find out together with Tom how we can avoid the RTO mode to trigger again with the selector in OFF - it should not engage, regardless of the thrust lever angle used. Cheers, Jan

Just wanted to thank everyone who acquired the application and confirm: I stand by my promise to fix the weight and balance calculations. The only reason why it is taking so long is because I decided to fix a few minor issues with flight planning and mapping and ended up... re-writing all of my previous code to fix these issues and link the app to the default navdata used by X-Plane. So, please, stand by. It is being worked on...

1. Yes 2. Yes 3. Yes (using Avitab) 4. Yes (on CPTs side, only) 5. Yes 6. No 7. For normal operation and normal failures only (not maintenance procedures)

Hi all, with the upgrade transition finished, I thought I'd report on whats planned to help set expectations for the future and into 2024. A high priority is weening off of technologies that may cause "show-stoppers" for customers or in danger of causing conflicts as XPlane and computers evolve. This means the transition to the FMOD sound engine is first up...as we've seen some issues for customers and is a sign that things aren't going to get better. This is a pretty good sized job as we have quite a few sounds we have to port and we also have a LOT of code we have to excise without breaking other things. A port to FMOD easily sets the stage for many more years of compatibility. We don't work completely linearly...so in interstitial gaps in time between FMOD work, we'll also begin integrating in the XP11 Navdata format. Users won't see this for some time as its a big under the hood change. This is necessary not only to improve the IXEG FMS, but is also necessary for two future products with FMSs and as with FMOD...ensures forward compatibility...so this move to the XP default is also quite important. Third, we'll also begin work on the FMS VNAV / holds / performance predicitions. This work depends on the XP11 navadata to some degree, but not competely so we'll be able to make strides in this department while working on the XP11 navdata format transition also. Also, we're refactoring (rewriting) an enormouse amount of code for future-proofing and developing a new graphics library along the lines of what the RSG and TorqueSim folks are using. This will open the door to more engaging graphics for GUIs and value-added interfaces such as failures and EFBs etc. and Finally, we'll work on a new, high-resolution exterior model with new paint kit. We expect this work to take most of 2024....but it very much has applicability in the other projects we're doing so the end of the road isn't just some "under the hood" stuff on the IXEG, but also new models. Thank you for your support, we'll continue to keep working. -Tom Kyler

I would like to congratulate the IXEG Team on releasing this update. Enjoyed so much flying it today! I have checked the extent to which this application is compatible with the new release. First of all, the application and the server (iGoConnect) are compatible with X-Plane 12. No issues found there. However, I have found that the application is not 100% compatible with the updated plane. Some issues identified: discrepancies in the maximum amount of fuel that can be loaded and CG values (e.g., %MAC). You may still use the application to plan for your flight and load the plane but the above discrepancies will be noted. If you notice other problems, please let me know. It is my intention to look at it some day but no firm commitment to when this will be done and in what way the fix will be available. Cheers!