Jump to content

Pils

Members
  • Posts

    1,778
  • Joined

  • Days Won

    35

Everything posted by Pils

  1. It's because this specific command needs to be "held" active for more than 1 frame, and XSaitekPanels is actuating commands in X-Plane incorrectly, so this can never happen or work without custom integration.
  2. Yes we’ll need to find and use new URLs in a software update.
  3. You must use time dilation NOT ground speed acceleration.
  4. The only “clever” part is setting up Discord to have a “push-to-mute” keybind that matches the xPilot PTT button to avoid echo if you’re using Vatsim. Vatsim Audio is not smart enough to not play your partner’s audio back at you over the radios.
  5. I’m sorry I don’t understand the question.
  6. That’s up to you to organise outside of the sim. I use Discord or FaceTime.
  7. Make sure your X-Plane audio sliders aren’t at zero. Also post your Log.txt
  8. You haven’t installed the XP12 nav data properly it looks like. Look at the contents of the Custom Data directory.
  9. You’ll have better luck getting in contact with Just Flight, this forum has nothing to do with them or Air Hauler. https://www.justflight.com/support
  10. There is no difference in the log, regardless my request hasn’t changed. Simply disabling the plugins is not sufficient, they must be completely removed. There is nothing to debug with regards to the Challenger’s systems.
  11. It wasn’t supported then either, and isn’t now, for reasons I can’t go into. No. It’s been there since day 1.
  12. Hi, Sorry you're having issues, however in the future please attach the full Log.txt, rather than posting a snippet. Secondly, Hot Start does not support using the beta Gizmo with the Challenger. This may or may not be the cause but to eliminate it, please revert to using the stable release of Gizmo (as provided with the installer) and use Rosetta. Thirdly, the log snippet you provided shows this is as an X-Plane core sim crash, not caused by the Challenger's plugins. Alongside reverting Gizmo, please remove all other third party plugins and scenery. Thanks.
  13. https://support.torquesim.com/hc/en-us/articles/360057635413-How-to-find-the-X-Plane-log-txt-file-
  14. Producing an FMOD pack for 737 will likely take months not weeks, but let’s hope it’s not too long.
  15. I think all the custom stuff like that was disabled for now, but don't quote me on that.
  16. Feel free to develop something and post it back to the forum. In general we encourage a more thorough "read-and-do"-style checklist strategy for simmers, this is more in line with real world operations in the corporate aviation world, vs. the "flow"-based style from airlines. So that's what's presented in the documentation. Do with that what you will.
  17. There’s some guidance to get started in the included operations reference document under shared cockpit section. Also at
  18. There's no crash information in this log unfortunately, but there are some other concerning errors. You may want to exclude C:\X-Plane 12 from anti-virus scanning, and also delete C:\X-Plane 12\Output\CL650 as there appears to be some access issues (from what I can translate). However this will remove all your airframes and saved states.
  19. The same as you attempted before, using DISK ROUTE LIST.
  20. Indeed there is. Described in their EXTENSIVE documentation if one bothers to read it. Just drop that into FMS Plans like any other.
  21. Quite the opposite. You've added an network proxy with some nonsense value. Remove it then try again.
×
×
  • Create New...