Jump to content

Pils

Members
  • Posts

    2,229
  • Joined

  • Days Won

    51

Everything posted by Pils

  1. Yes, the NOAA interface does appear to be working again. But I think this "un-solved" zombie state might have to stay for now.
  2. A demo is available to test this, for what it's worth.
  3. It's possible I misunderstood the motivation behind this design decision for this particular button, however we are talking a matter of milliseconds in the sim so it wouldn't necessarily correspond to irl physical input. I'm hopeful that Mobiflight will improve their integration in the future, most other tools figured this out and provide their own X-Plane plugin for full access to the sim. No promises, but I might be able to come up with this if I get permission from Avionique.
  4. Sadly, the issue at NOAA has returned.
  5. There are several buttons in the real aircraft that need to be helm down to activate, I assume as a safety measure, and these are replicated in the simulation. Personally I wouldn’t touch this software, it’s a hack and known to cause issues in XP. I don’t know those other tools. The developer of other fine CL650 hardware had a similar issue with their DCP/CCP, and was able to work around it with this script https://www.avioniquesimulation.com/wp-content/uploads/products/DCP_CCP/DCP-CCP_panel_lua_script.zip, you can look at it for inspiration.
  6. Its very simple, as I’ve explained elsewhere, the “AP engage” command must be held “active” for multiple frames, however MobiFlight is incapable of doing this as long as it uses X-Plane’s UDP interface.
  7. From the dev: So, I'm afraid the XP11 just flat out broke because of that bad GFS data and there's no trivial workaround. The only way is to use the XP12 version. The XP11 version always pokes at the GFS data and NOAA is returning some bunk that's crashing the plane. You will need to use XP12 until either NOAA fix their data service, or we get a new beta build out with a fix.
  8. This error specifically is a bug in XP’s flight model. You’ll need to report to Laminar. Please post Log.txt from XP regardless.
  9. https://discord.gg/hXM9HzWt
  10. I look forward to the fruits of this labour, because the current set of documentation is woeful.
  11. https://discord.gg/csypV2JR
  12. Negative.
  13. Define “work”.
  14. What driver?
  15. Arc GPUs are not officially supported by XP, and unlikely to be supported by TBM any time soon.
  16. Please post Log.txt
  17. I recommend 11 on 8-core HT/SMT processors as there’s resources to spare. The original advice was more for processors with 8 or less threads.
  18. Not been reported by others. Can you record and publish your own video of the issue by chance?
  19. As Ben hinted at, make sure you start X-Plane with --num_workers=11. Also, look at the frame profiler, it'll help point at a particular part of the frame rendering that's being slow.
  20. Download the installer again?
  21. These are not related. Your problem is elsewhere.
×
×
  • Create New...