Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/16/2020 in all areas

  1. Jan is right, we have not touched the AP or VNAV code at all since 1.21, so if something is worse, we need to know exactly what it is that "makes it worse". Debugging is quite tough business, not so much the fix, but the amount of diligence it takes to quantify what the issue is and put it into words. Good VNAV starts with good routes to make calculations from, and that is where we currently are as of this instant, fixing the STAR / APP route building code as these procedures are selected...since they are clearly resulting in 'funny routes' where VNAV calculations make no sense. That '470' bug is a pain for all of us and I'm super sorry about that one, but its fixed for the upcoming update and we are also now trying as many route editing combinations as we reasonbly can to test the robustness of entries. We will have an update in relatively short order with several fixes for sure and I for one, will be interested in seeing how the FMS handles "in air edits on descent" for all the situations folks will try that we did not get to. VNAV complaints are heavily biased toward the descent calcs and revisiting my code, its not hard to see why....which is a good thing...as it paints a clearer path for repairing the code. We are now working on FMS code and VNAV with priority, so any patience / feedback as these updates come out will be appreciated and help us improve. Bug reports regarding VNAV after this next update will be quite valuable as we are focused on that work at this time. -tkyler
    2 points
  2. Found the issue with the Localizers. X-Plane 11.50b10 changed one element of the localizer nav data encoding (bearing), which broke the custom localizer simulation code in the TBM. Compatibility workaround will be included in the next TBM update.
    2 points
  3. Yeah, recently got hooked with stevo youtube videos,
    1 point
  4. I had this issue a few times, it is easy to fix, just switch to manual for a while and select the tank having more fuel
    1 point
  5. The 2020 SDK is completely different from X-PLANE and will be a model from scratch. If IXEG was for p3d, you might think. Rather, it is the x-PLANE 12 version. Now another developer is developing a full line of 737 classics for 2020 and p3d. Probably the best and most realistic 737CL in XP, better than the near default 737 in 2020
    1 point
  6. This is really looking good. Great fps, accurate weather and better clouds. Just thought I would share...
    1 point
×
×
  • Create New...