Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/20/2016 in all areas

  1. Looking forward to the IXEG 737 in XP11 with the new shaders and such. Bet it'll turn out even more spectacular as of right now
    1 point
  2. The above info is correct, but you'll probably want to use the regular installer to migrate over just to make sure the entire install goes over cleanly (there are more parts than just the aircraft folder). It will ask you to re-activate, but it will not burn one of your activations if it's on a machine which has already been activated before.
    1 point
  3. Hi fsedano, All CDU screen outputs are already available as custom datarefs. (like ixeg/733/FMC/cdu1D_line1L_t and ixeg/733/FMC/cdu1D_line1L_d) The _t is the smaller "title" line and _d is the larger detailed line. Co-pilot CDU is cdu2D... there are separate datarefs for scratchpad, page number and title lines as well as the CDU annunciators. (MSG, OFST and FAIL) Pretty much all you need to build your own "virtual CDU". Let me know if you need the complete list... (yes, I made my own) Here's a screenshot from my Android tablet virtual CDU... still very much work in progress.
    1 point
  4. I just fixed a bug from another report that I believe is related to this. Whenever you have an acute turn at a waypoint...and the next waypoint after the acute turn is too close to make (bypass)....then the plane would depart the LNAV path after teh waypoint BEFORE the acute turn. This bug is due to our "look ahead" code that tries to anticiapte turns in order to give better LNAV tracking I just enterd the route and see the waypoint combo I expected to see (OTBED > MONTY > WAL24)....and the route draws well now (it was kink'd before). So I think this is fixed for the next update. -tkyler
    1 point
×
×
  • Create New...