Jump to content


Popular Content

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

  1. 2 points
    Because IXEG was not about trying to sell you a product with gimmicks to make up for something else it couldn't do. Realistic cockpit simulation is and was the primary concern. To this date there are still essentially no airliners that come close to simulating the actual systems in the way IXEG does. Wing flex is so minimal on a 737-300 it's pretty much not noticeable. Yet another reason why it was senseless to put that as something to focus on rather than the incredible systems simulation that it is.
  2. 1 point
    And the fuel costs at different airports varies wildly. Small airports have it down about $4...the big fancy ones have it up in the $8 range.
  3. 1 point
    TAS, IAS, GS: this is basic PPL theory stuff, you may need to read up on it; IAS is what the airspeed indicator shows, the higher you fly, the less air density, the less airspeed is shown. TAS is IAS corrected for density and temperature. unless you fly at 0 feet, at standard temperature of 15°C, TAS will always differ from IAS. GS is TAS +- headwind/tailwind component. You may be flying at 100kts; but against a headwind of 50kts, you only make good 50kts over the ground, this matters for navigation, fuel planning etc.
  4. 1 point
  5. 1 point
    Hey Jan, I totally agree! I am a real world pilot (ppl) and even at my level I realised that 99% of the time... the human is wrong... not the machine. So it's better to have this kind of system. Thanks for that level realism! You got me from frustrated to super excited ! One note though: what could be an ehnancement for future release is to simply "block" the sliders in the preflight module when one goes above the max allowed ZFW weight. This could limit confusion... but that's just me being picky. Keep up the good work! Seb
  6. 1 point
    Yup, worked for me, and the fix removing the smudges, thank you! Still having mouse issues, and it seems that interacting with the RealityXP GTN 750 to change freqs will also make the mouse disappear.
  7. 1 point
    You are putting in a zero fuel weight of 63+ tons - that is way more than the maximum allowable weight. Change the weight to be within limits and try again. Cheers, Jan
  8. 1 point
    Love to get her out of the hangar again any thoughts when SOON will happen with the update 1.5.2, yea I know, soon.
  9. 1 point
    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
  10. 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