Jump to content

Pils

Members
  • Posts

    2,015
  • Joined

  • Days Won

    45

Everything posted by Pils

  1. How long is “a bit”? Please post your Log.txt
  2. One possible issue I can see, not that I’ve seen this cause the crash you’ve seen specifically, is the VRAM heap allocated to X-Plane is being exhausted. If you’re running Maximum texture quality then then it down to High.
  3. We are all convinced this is an Laminar crash, and there’s nothing in the data provided for the developer to investigate, so I’m not sure what else we can do, unfortunately.
  4. Suggest disabling XPRealistic as it has been known to interfere to the CL-650’s systems logic and cause crashes.
  5. WAAS API error is a red herring, post more detail of what you were doing when this crash happened, please.
  6. Please provide the contents of cycle_info.txt in Custom Data directory.
  7. What exactly are you typing into the scratchpad to change the restriction?
  8. That’s how the real FCU works, turn the knobs faster the increment increases.
  9. Can you capture a video of the behaviour while showing the flight control synoptic page, please.
  10. Good news! This has been implemented and should be in the next update. Watch here for confirmation upon release.
  11. No response from OP so assuming all is well. For previous topic refer to
  12. No need to press ATS button and A/T disconnect, one or the other is sufficient. When you see the “ghost throttles” graphic, as we call them, you need to sync up your physical hardware (the outlined boxes) with the position in the sim (the ATS boxes) before your physics hardware are “reconnected” to the virtual cockpit throttle levers. Hope that helps.
  13. I agree with Goran’s advice. Fresh install across the board.
  14. Suggest you backup and then delete your …/Output/CL650 directory from X-Plane then start a fresh airframe.
  15. Still seemed to risky to me so haven’t done it yet! How many times have you accidentally shut off an engine on the runway, be honest? Edit: Oh I see from the PDF you aren’t actually doing this. Misunderstood.
  16. I’m pretty sure AviTab was specifically written to be good for VR users.
  17. We believe the cause of this has been identified and fixed for the next update. Thank you for helping improve the product!
  18. At MLW anything below around 0.9 G would be considered “normal”.
  19. Ok, search for “fuel_selector_none” default commands.
  20. Note quite. It shows “delta G”, i.e. difference between gravity and the G load on the aircraft at touchdown, which is determined in a slightly complicated manner. It’s used to determine when an inspection of the landing gear is required. But we know how simmers love to chase butters…
  21. Try N4810W040. Also, the Pilot Defined Waypoints page in the FMS is an option, and will guide you to the correct formats.
×
×
  • Create New...