Jump to content

Leaderboard


Popular Content

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

  1. 1 point
    Oh my goodness, were you able to save your data?? Sorry that happened to you!
  2. 1 point
    Well done both of you. Finger trouble during start up!!! Never too old to learn and re-learn
  3. 1 point
    @ColSig As @marpilot stated the big gotcha is not flipping the AP/TRIMS switch to ON. If the AP/TRIMS switch is positioned to On and the elevator trim is still in-op, then take a glance at the Circuit Breaker panel on the right side of the cockpit and make sure the 7 1/2 AMP AP SERVOS circuit breaker is not tripped as this breaker does effect elevator electric trim. Also, if the above is not the issue take a look at your Saitek X56 and make sure the control/s you are using for elevator trim are still assigned. Hope it helps! Dwight
  4. 1 point
    Maximum cruise speed of 330 knots dictated by the manufacturer is TAS not GS (Ground speed). Si, if you were getting 314 knots of GS under a 14 knots headwind component your TAS was actually 328 knots. Pretty much exactly what the manufacturer says. So i would think the TBM 900 performance simulatiom from this guys is SPOT ON. Also note the manufacturer states 330 knots under ISA conditions at FL280. So if you are flying higher or lower, and ISA conditions also doesn't match (temperature) it will also impact performance
  5. 1 point
    ...or move to SWIFT https://datastore.swift-project.org/page/about.php
  6. 1 point
    A fine addition, thanks for your work on this! Again, we (besides having so much else on our plate that we need to do first) don´t want to really model any of this aspect, because I as an airline employee am under special scrutiny for divulging any security aspects. But if someone else provides something like this, hey, what can I do about it? Thanks, Jan
  7. 1 point
  8. 1 point
  9. 1 point
  10. 1 point
    then you can code like : if joytsick_x > |0.95| then "no trim" end If you look carefull is not a layer order problem for the FD : the FD in the real aircraft are 0.80% to 0.90% opaque. Not 100%. That's the deal. I'd like to draw 'n add a custom 3D object with static texture for the TV monitor. That would be cosmetic, not functional, (so not simulating security-related functions) but fun to design.
  11. 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
  12. 1 point
    Turn off the option "show vertices" in the IXEG side-bar menu. Cheers, Jan
×