Jump to content


Popular Content

Showing content with the highest reputation on 06/01/2019 in all areas

  1. 1 point
    N449MA Hot Start TBM "sandy blue" View File Here is a livery I am very familiar with. I deal with this aircraft at my airport a few times a month. N449MA. Enjoy! Submitter Attitude Submitted 10/25/2018 Category General Aviation Livery For http://www.x-aviation.com/catalog/product_info.php/take-command-hot-start-tbm-900-p-158?osCsid=20d43cf99c669d4273528e465564e9d7 X-Plane Version(s) X-Plane 11  
  2. 1 point
    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
  3. 1 point
    Hi there, I can't find how to map the beta range to my throttle. I'm using a Saitek X55. I'm using the same button and mapping I use for the Kodiak (Thranda) and TBM 900 (Hot Start) but it does not reverse the axis response (pushing the X55 throttle does not pull the PR throttle backwards into beta range). I'm pretty sure I'm doing something wrong as I didn't see any issue about this and it would have been reported way before release anyway. Using the reversers command instead just make the handle jump to the max reverse position then instantaneously back to its initial position - so it's not completely stuck and seems to be a control issue on my end. I also mapped only one axis to the throttle (no conflict there). If anyone has any idea, I'd be happy to test whatever might work.
  4. 1 point

    Version 1.0.0


    Here is a livery I am very familiar with. I deal with this aircraft at my airport a few times a month. N449MA. Enjoy!