Jump to content

Pils

Members
  • Posts

    2,388
  • Joined

  • Days Won

    57

Everything posted by Pils

  1. Not at this time.
  2. You must set your display scaling to 100%, and also text size to lowest/normal under accessibility settings.
  3. It’s still a 900.
  4. Pils

    Activation

    https://support.x-aviation.com/index.php?a=add
  5. https://discord.gg/mQyr2dbZc
  6. I'm not really interested in speaking to an LLM. However, for the record, the site is down for maintenance, and will return as soon as possible.
  7. There is no "upper menu" for the EICAS display. Its visibility is mandatory, however it can be moved to a different screen using the selector on the rear of the pedastal.
  8. Can you post a screenshot and/or video of your main instrument panel, please?
  9. You need to change the display scaling (and/or text size) back to 100%. You're missing the password field from the GUI.
  10. https://discord.gg/mQyr2dbZc
  11. You already have this option. You setup the airframe in any way you like, once, and use the Airframe Manager to save the state as a preset. This can later be loaded at your convenience.
  12. Pils

    Nose door Cl60

    Is the nose gear door safety pin still in place?
  13. https://discord.gg/H2KgxSAnX
  14. Not at this time.
  15. No forward slash between waypoint and bearing.
  16. https://discord.gg/H2KgxSAnX
  17. A temporary authorisation issue that's now resolved.
  18. It’s the texture for ice. (It can appear when no ice is present, which is a bug.)
  19. Flight model crashes need to also be reported to Laminar Research. Thanks!
  20. The route on the plane's map isn't like an Airbus where it'll fly exactly along the line, so some deviations are expected. Looking at attempt 3 again (at 4x speed???), I see it did draw a turn to the right, but when it sequenced it took the shorter path to the left. That's maybe a corner case that the developer needs to address. But, I think to get you passed this issue, an adjustment to flying technique will put it inline with what's expected (and demonstrated by us).
  21. You're flying the climbs in PTCH mode (and at a pitch less than 10 degrees in some cases), while not accelerating past 185 kts (as per the chart). From what I can tell the plane flew exactly as you commanded it to, at low pitch and low thrust (due to low speed target), with attempt one being the lowest (zero climb rate/VS at times, should be something you're monitoring). After initial take off phase you should be switching vertical mode to VS or FLC. The plane is capable of climbing at several thousand FPM, not hundreds. Obviously in hot weather (like ISA+19 you have) and with a heavy fuel load that will be lower. FWIW the chart may show this, as that's what's expected, but it's not enforced in the database coding. If you leave the PFD ROSE in HSI mode and the CDU on the LEGS page you'd have shown what exactly it was flying more clearly. The popup makes it easier to see the DTK, it was flying to course 331, which is a "shorter" turn by going to the left. I think it all comes down your procedures, and the plane is flying exactly what the database tells it to. Hope this helps. P.S. X-Plane's default video capture is terrible, I suggest using OBS Studio. Also uploading to YouTube or Streamable.
  22. I think it starts to go “wrong” (it flew what the coding was in the database but not what was depicted/expected) when it turns inside the Navigraph estimate and reaching the 10500’ restriction too soon. Were you flying at 185 kts max as charted the whole time?
  23. Change display scaling and text size back to 100% https://support.microsoft.com/en-us/windows/change-the-size-of-text-in-windows-1d5830c3-eee3-8eaa-836b-abcc37d99b9a
  24. A bug triggered by noisy hardware. Will be resolved in next update. Workaround is to add a dead zone to Yaw axis.
×
×
  • Create New...