Leaderboard

Hello All. This post will be locked as its only intended for public statement. While many people are aware of the IXEG Development status, many others will not and so this post is intended to provide clarifying information. For a while now, IXEG development has sat relatively idle. The reasons for this are multiple and have been stated in other forums; however, two significant factors contributing to that idleness have since wained and IXEG are looking at how to best move forward with IXEG updates again. There are two areas we are looking at for updates, 3D cabin/doors/animations and the FMS. Regarding the FMS, IXEG are looking at transitioning to the XP1100 Navdata format, which is derived from the ARINC 424 standard. Moving to this dataset format would yield increased accuracy in the representation of procedures and more practical data with which to improve LNAV / VNAV / performance caclulations. If it turns out that porting our code to the new XP1100 format is too cumbersome in the short term, then we will seek to patch what we have now and transition at a later time. The important thing is that IXEG are moving again to improve the FMS. Regarding the 3D, this will be a bit more of a undertaking. The development tools IXEG used for 3D development are nearly fully deprecated and there has been a major transition to newer tools and methods. This necessitates IXEG reconfigure our source material to the new formats and we have a LOT of 3D material to translate. This means that the 3D updates will be longer in coming than the FMS updates. Once the 3D is ported to the new tools though, any updates we implement thereafter would come much quicker, simliar to what was done shortly after our release for those that recall. We apologize for the idle time and appreciate all our customers and any patience you've exercised. We are sincerely committed to making the most immersive and accurate simulation of this aircraft as we can and will continue to push towards that goal, no matter where its end may be. -Tom Kyler

Hello All, This will serve as a formal forum announcement that we have released the version 1.1.9 update for the TBM 900. All customers who have purchased the TBM 900 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 TBM 900 from today forward, your purchased download will already be updated to version 1.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 TBM 900 download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: What's New / Changed: Improvements / New Features: New ground steering model to put an end to the unstable takeoffs & landings. Implemented GPU rental costs. Added hand-towing option to the sidebar drawer. XP11.30 engine changes during startup to produce a lower startup ITT spike. Added inertial separator transition sounds. Pressing TIMER on the yoke automatically brings up the TMR/REF page. AviTab support integrated into yoke-mounted tablet. Tablet now stows in the door pocket. You can still use the USB ports to summon it, but this will be removed in a future update. Reworked pressurization schedule. The system will now gradually change the cabin pressure target as we are nearing the destination, instead of going to it immediately on takeoff. Pressurization won't fling open the OFV fully on landing, but modulate until equalization has been achieved. Corrected high-altitude performance to be within +-2 knots of POH tablets. Implemented configuration-dependent KIAS errors to match POH values. Implemented sidebar drawer smooth animation. AOA sensor failure separated out from AHRS and now individually settable in "Edit Failures" window. Visual configurations window now includes option to use older custom heatblur effect. Expired databases show in amber on MFD splash screen. Replaced G1000 manual link with one for the TBM850 & TBM900. Bugfixes: Battery recharge button in maintenance manager was incorrectly disabled. Restructured battery voltage drop with load to give more realistic red battery voltage indications during start. Fixed CAS message pixel alignment issues. GPH indication on EICAS should properly respond when moving into or out of CUTOFF. Electronic checklist was asking for "FUEL SEL" to OFF in a few places, when it should have called for MAN instead. Gear wear was using incorrect sideslip computation. Rudder propwash force correction could end up taking reverse thrust into account, when it shouldn't. Fixed missing pitot & static covers Low-fuel instability wasn't powerful enough. Fixed prop overspeed on reverse with slow forward motion. Workaround for ReShade bug causing hang in its OpenGL hooks DLL. ODB was missing minimum download speed clamp to abort if the download is slow. Don't try removing the odb directory if it didn't exist to avoid a spurious error log message. glutils drawing wasn't properly disabling vertex arrays, leading to potential crash. 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.

I would also like to see that feature.

mmerelles Thankyou

The aileron flutter issue will be pushed in the next update, once we get the full synth fix, it will be pushed out to everyone. That is an interesting issue with the airspeed, that sounds like it is either caused by the pitot cover being on or your pitot tube being clogged (check the sidebar maintenance manager - the maintenance system can be fully disabled from the sidebar menus as well)

Or you could just fly the plane like a normal human would do in the real world looking out the cockpit window? That is what we're simulating, after all.

Hello again. I'd like to give another update. During our investigation into updating our NavData to the XP1100 format, it became apparent that this must be the way to go for long-term future compatibility and more reliable route calculations, including holds, but would require a significant rewrite of the FMS base architecture to do so. So over the last 4 weeks, we have done exactly that. We now have the beginnings of a 2nd FMS running in parallel with... but independently of.... our original FMS. We are running 'newFMS' on CDU1 and 'oldFMS' on CDU2. We will NOT be simulating dual FMCs though. This old/new arrangement only exists so we can compare the new with the old while developing the new. It is much like building a new bridge alongside an old bridge...and when the new one is ready, we will remove the old. Much of the challenges we have faced with regards to drawing routes / vnav have been related to the limited nature of the navData format we have used since we began the project. Moving to a format which have been designed expressly for "navigation processing" will go a long way towards easing our algorithm development. The image below shows the two CDUs, both on the "IDENT" page, but clearly displaying differing data as they use differing algorithms/databases....and for those curious, the pilot CDU displays 'odd' formatting simply because we were testing our new display drawing code. We are very excited moving to this new XP1100 format. We have, in 4 weeks, accomplished what took us over 24 months to accomplish originally. Of course we have the benefit of experience, but the elegance and efficiency of the new navData format and architecture allow us to focus on the FMS functionality by orders of magnitude more than before. With the new infrastructure complete, we will begin working on the route editing. The current navData set only supports about 8 different waypoint types. Arcs are not supported, as is common in today's RNAV procedures, but the new format contains all path/terminator types typical in today's procedures. As usual, we thank you for any patience you have managed to muster as we work to improve the IXEG 733. P.S. Jan and myself will be at Flight Sim Expo in Orlando, FL/USA in a few weeks if anyone wants to talk shop. -Tom Kyler