Jump to content

Pils

Members
  • Posts

    2,239
  • Joined

  • Days Won

    52

Everything posted by Pils

  1. Thanks for clarifying. I didn’t follow before. The “X” prefix is used in Gateway for anything that doesn’t have an ICAO code, basically, so that it can be globally unique.
  2. Just a note for the future (and possibly here), the plane will look back in time for METARs to see if it cold enough to frost, or if there was rain/snow, etc. On the flip side it'll also account for melting due to temperature. Best to double check the wings and icing data output when having odd performance issues like you did, who knows what X-Plane might also be applying. No; they'll appear once the bleed air has been transitioned from APU to engines.
  3. How did you determine they were helipads? Because I checked all three on Gateway/Google Maps and they're just little GA grass airstrips.
  4. Yes, but what did you select to display on the MFD map, exactly? As the name suggestions "MIN RWY" only applies to "NEAREST APTS" not "APTS".
  5. What set of symbols, “nearest apts” or “apts”?
  6. Hi Rich, I would love to say definitively one way or the other, but it's just not possible, there's too many variables. My guess is that your current CPU will be the limiting factor for your framerate, not the GPU processor itself, and as such more GPU performance would be "surplus" (I can only speak for X-Plane here mind, MSFS might be different). However, more VRAM can always be used regardless of your CPU performance, if that makes sense. On the flip side, if you intend to later upgrade the CPU/motherboard and/or monitor (4K), but keep the same GPU then investing in a more powerful GPU now may make more sense. Either way, it's just guesswork as I don't have personal experience with any of the cards you've mentioned, unfortunately.
  7. Whatever is in the X-Plane airport dataset is displayed, subject to filtering. You can look for yourself on https://gateway.x-plane.com/airports
  8. The numbers from task manager are far from the full story, but that does suggest you are closer to the GPU limit on your system.
  9. User Settings.
  10. The question is, are you limited by the CPU? Most people are.
  11. For that you need to move your camera view. Your feedback is noted, thanks.
  12. Oh yes, they are well aware of what's needed.
  13. There’s still a bunch of third party plugins loading, and any one of them could be the source of the issue. We need to eliminate them by removing them from the sim completely.
  14. No. The sim still does not provide access to the required raw data. We continue to wait for Laminar.
  15. Please provide the full log file again. Thanks.
  16. I understand it’s a lot to figure out. If you do come back to it for another try, I’ve seen several people receive one-on-one instruction from our gracious Discord community members: https://discord.gg/YXEyF7CY
  17. Leaving the beacon light on?
  18. Yes.
  19. Yup, this’ll have to go to Laminar. Sorry.
  20. These are all simulator crashes that will need to be addressed to Laminar Research, but if you upload your Log.txt maybe we can give some pointers. https://www.x-plane.com/support/
  21. There’s no real outage or NOTAM.
  22. That's how it works. Have you read the FMS Primer document that comes in the aircraft directory?
  23. Works as in moves the stabilizer? It's a two channel system so either being on will be enough. There are definitely STAB TRIM CAS messages when appropriate, e.g. STAB CH 1 INOP, etc. On the back of the control wheels.
  24. Hot Start Discord: https://discord.gg/x3PghQ8m
  25. It won't engage if you're putting too much pressure on the flight controls, for example.
×
×
  • Create New...