Joshua Che.

Staff
  • Content Count

    275
  • Joined

  • Last visited

Community Reputation

42 Excellent

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Does this happen to all or specific approaches in 1813? Has these approaches changed compared to 1812 (where it worked)?
  2. Did you enter different gross weight/zero fuel weight (into fmc) from what is actually loaded?
  3. Joshua Che.

    MCDU plus AP

    On Windows 10, Xbox Game DVR is good enough. On Windows 7, OBS, but you need a bit of setup to get it right. If you have Nvidia Graphics Card, GeForce Experience has a built in recorder. I usually expect users to post screenshots of the issue as its way easier for them to print screen than type out everything in detail. However, in this case, this issue requires a certain number of specific steps in order to replicate the issue - ie, direct at a particular distance from waypoint etc. Henceforth, I would prefer multiple screenshots or screen recording.
  4. Joshua Che.

    MCDU plus AP

    The reason why I request step by step is because the information give is not sufficient to show what EXACT steps you took. I do not know when exactly you executed the flight plan change during your flight (which waypoint were you travelling to? at what altitude? what was the prior entry before? any discons inserted before that is cleared? any waypoint in the approach deleted? etc etc). Its also why I request screenshots as much as possible, or even better a video of the flight from the start to the event as that way you dont have to list each individual step you took.
  5. Joshua Che.

    MCDU plus AP

    I need more information on this; the exact step by step to replicate. Also screenshots to show the before direct, after direct path drawing would be good.
  6. Wow. Thanks for the effort to write a clear report. I will investigate this asap.
  7. I understand your frustration. However, I will be very blunt. If you not going to submit a proper report, I would prefer you not stay on the COB branch. Reports like this are not helpful at all.
  8. Trying to capture the localizer too close (Less than 1000ft AGL) will always cause issues for approach. The AP LOC algorithm is completely different from LNAV algorithm. WIth LOC, you get a triangle beam that is way less sensitive 5 miles out when compared to being 1 mile out. With LNAV, its a cross track error that is does not vary in sensitivity.
  9. Cannot replicate using your case scenario of KSLC I16R. Are you using any airport addons there? Did you apply any magnetic variation database update? If no, grab it from here: https://www.aero.sors.fr/navaids.html
  10. Known issue, however, its is low on the list of items - and it may not be what you want to hear. However, we want to get rid of the stability issues first before working on AP/FD refinement.
  11. All, We have identified certain methods to mitigate this effect. @turbofandude will be working on it and updating you as it goes along.
  12. Did you mean you set the engines to idle? It does not make sense to shut down the engine in flight, and its not fully simulated.
  13. When you save a flight and load it up again, the engines take a while to spool up (approx 30 sec). This is because the saved flight doesnt include current engine parameter, only throttle. So technically, the engine is "starting up again" and running to the required level of power. If you have a 100% replicable CTD after performing a certain fixed action, please report it in our bug tracker on how to reproduce it. Attach any extra saved flight files you may have used.