Jump to content

CaptCrash

Members
  • Posts

    198
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by CaptCrash

  1. Can you please attach your log file from the crash? Thank you
  2. Thanks for the report, can you please attach the full log? Thank you
  3. Please do not use the weight and balance menu of x-plane, the aircraft is not designed to be interacted with in this manner. Please use the fuel truck fuel loader or the FBO and fuel request to manage weight and balance. if you experience another crash using the appropriate methods for payload and fuel please post that log here. If you still experience a crash please follow these steps: Thank you
  4. Please remove all plugins except gizmo from the plugins folder of x-plane and scenery, then please try to reload the aircraft. If you experience a crash please post the log
  5. please remove all other plugins except gizmo and add-on scenery. if you still receive a crash please post the log.
  6. please remove all addon plugins except gizmo and retest if the crash occurs, please post the log again if it does.
  7. If on the ground, do not attempt takeoff with the cas message present.
  8. Not a problem, we want to make sure it is correct. The behavior stems from the different kinds of guidance the FD offers, when in a normal (non angular guidance FD mode) but we will have our subject matter expert validate the behaviors in the coming weeks.
  9. We will be validating the FD behavior in a CL650 level D simulator in the coming weeks. Thanks for the feedback!
  10. Please update your plugin to the latest version.
  11. Was there any impact to the operation of the aircraft?
  12. Please see the FMS primer document. Thank you
  13. This is expected behavior and working as intended, the actual unit only loads into the SEC flight plan to protect the primary in the event of an inadvertent upload. It would be bad to accidentally upload the wrong flight plan over the ocean.
  14. Users with AMD graphics cards may experience flicker in some situations to varying degrees, this is not an issue with the aircraft and until AMD address this issue there is nothing we can do. If the issue is the flicker of the tail number the best solution is to edit the appearance of the airframe and disable the custom registration rendering.
  15. We will investigate this issue, thank you for the video!
  16. If you are using the virtual FO we recommend navigating the checklist using the keybinds for the virtual fo to advance the checklist. Please do not use the DCP to navigate the checklist when using the virtual FO. It is hoped that the virtual fo checklist system can be improved over the life of the product. There currently is no roadmap for it but we are aware of this behavior.
  17. Thank you for the feedback. Currently the textures match our reference photos from the aircraft we have access to.
  18. Logged and marked as open. We will investigate. Thank you!
  19. It currently appears that this is not gizmo or the CL650 but rather task saturation is occurring on your processor and the high execution times you see are a function of the task scheduling in the flight loop being delayed. @robbietp1 what processor do you have currently installed? additionally can you try removing all addon plugins except gizmo and seeing if that helps with execution time.
  20. There is no method to defuel the aircraft. Defueling is primarily a maintenance operation.
  21. Please remove your sceneries to a different folder and try again. please make sure the gizmo plugin is still in the plugins folder too.
  22. Different SOPs use different values. One operator uses a flat 90.2 in TGT and others select the TAKE OFF thrust limit for go around. Either method is appropriate.
  23. @dipperdolphinplease isolate all of your custom sceneries and remove all plugins except gizmo and try again please
×
×
  • Create New...