Jump to content

Pils

Members
  • Posts

    2,150
  • Joined

  • Days Won

    49

Everything posted by Pils

  1. Please provided Log.txt from X-Plane
  2. As discussed on Discord, this is due to OMAR not having any instrument procedures and therefore being excluded from the FMS's database. A fix for this will be in a forthcoming update.
  3. As promised (in case anyone still cares), here's links to the profiles I developed while beta testing this aircraft. These were my personal choices, and you're free to do with them what you will. For example, I really only use Xsaitekpanels for the radio panel and the trim wheel on the multi panel, everything else is on the Bravo. Edit 2022-01-21: I’ve added the AP buttons (not lights!) to the Xsaitekpanels by request. Edit 2022-01-22: Added AP lights and knobs to Xsaitekpanels. Displays are not possible at this time. https://github.com/pilsnerish/Xsaitekpanels-Configurations/blob/main/CL650_xsaitekpanels.ini https://github.com/pilsnerish/Honeycomb-Profiles/blob/main/CL-650.json However, I suggest referring to the following thread for a much more complete Honeycomb profile kindly provided by @Goodfixins.
  4. Try a 10% sensitivity setting in the control profile? I’ve been using 0% fine on Honeycomb, but it’s all going to be down to individual hardware and personal preferences.
  5. Request has been passed to developer, will update if/when there’s implementation.
  6. D-ATIS only sources from https://datis.clowd.io/. And I believe SIGMETs are only available from the FAA also, but don't quote me on that.
  7. Was the original post after changing from 150% to 100% with the plane loaded?
  8. Good request in general. However, does your hardware hold a command when in position? Because “hold brakes max” works fine for me.
  9. No-one will be able to tell you how this addon will perform on your hardware unfortunately. 500Mhz isn’t a huge amount but performance will also depend how many cores you have, what their boost speeds are, etc. The risk is yours if you choose to purchase.
  10. Firstly, please don’t post to unrelated threads. Secondly, I don’t see anything in your screen shot showing a bind to the red button. Please post the bindings as tested. Thanks.
  11. @N330CT Are you using native X-Plane multi-monitor or something like Nvidia’s virtual desktop feature? Please provide your Log.txt also.
  12. Yes the AIRAC must match between Simbrief and the FMS. @mraviator
  13. Have you fully loaded into the plane before setting up the controls? You can use Non-persistent mode.
  14. Thanks for all the feedback. I’ve mentioned this thread to the developers and when they’re ready to tackle some VR improvements they will review!
  15. Can you take a screenshot of your binding so I can replicate exactly please?
  16. I’ll be honest with you all, I always considered this curve modifier as only applicable to prop planes, I never thought to use it for jets. Hence, I have no idea what it actually does behind the scenes. Are you saying that every addon you own has custom support for the TCA? Because I only know of the FlightFactor and ToLiss Airbuses that do. So, if you want this supported in the CL-650, it would help if you can describe to me what exactly needs to change in the addon? thanks.
  17. It won’t go past 50% on the ground; are you on the ground?
  18. That would be the (currently hidden) FBO.
  19. Can you check your Log.txt for faa.gov log lines please?
  20. This panel
  21. Sounds like maybe VRAM related? Might have to drop to Medium quality. Also, Medium objects for general single thread CPU bottleneck reasons.
  22. Try dragging the plane back a bit in the X-Plane map.
  23. Manual entry format here. Not confirmed the Simbrief format is the root cause as stated in the post above, which will be revised, so please still provide the full route and .FMS file.
×
×
  • Create New...