Jump to content

JGregory

JGX-Designs
  • Posts

    2,256
  • Joined

  • Days Won

    23

Everything posted by JGregory

  1. We don't support use of the GTN 750. Maybe another user can assist. Known issue, being worked on. Known issue, being worked on. No. This would interfere with the Saab logic.
  2. There is a preference to turn the menu on and off.. you probably have it set to not show the menu.
  3. The G530 in the Saab is the default unit from Laminar. I would try to enter the same data using a dafault Laminar airfcraft (Baron or King Air) and see if the same thing occurs. If it does, you may have a plugin conflict or it may be a bug in the 530. To test a plugin conflict remove all your plugins and retest. Put them back in one-by-one until the problem occurs again.
  4. Need more info... how are you applying the brakes? Do the "V" and "B" keys work for you?
  5. We will look into it.
  6. Please be as specific as possible. Fast movement of throttle hardware can get out of sync with the manipulators. You can use the TQ viewer to see if you are out of sync. CTOT was tested and working fine. Again, please be more specific.
  7. You can certainly fly in VR, but the yoke is not useable, would require hardware.
  8. The pop-up is covering the G530 in your screenshots so I cannot see what you are describing. Or, are you referring to the pop-up itself ??
  9. This is a known issue. We currently do not have an estimate of when this will get fixed.
  10. The Saab has been tested in 11.52 without any problems. Please try to load the Saab again and post your log.txt file here after that.
  11. We will look into this, but can you explain what you mean by ... "I upgraded to version 1.6 and it initially started without a problem. I then upgraded X plane to version 1.6 and now i get the attached message." You're referring to the same version ???
  12. you can search for these commands in X-Plane.
  13. We are looking into it
  14. les/sf34a/acft/aplt/mnp/cw_ap_disco_button_pilot les/sf34a/acft/aplt/mnp/cw_vert_sync_button_pilot
  15. Known issue... should be fixed for the next update. I assume you did not exceed the weight limits, correct ? We will check into this otherwise. Known issue... should be fixed for the next update. No. We are modeling the Saab to match the real world aircraft. Have you seen any Saab gauges with Units of Measure other than Kg ??
  16. You probably have a plugin that is trying to control the camera and overriding the Saab logic.
  17. No.
  18. JGregory

    Vulkan API

  19. Yes, Vulkan is fully supported.
  20. Disabling them will not work, they need to be removed from the plugins folder.
  21. The log files do not indicate any crash. You do have several plugins, any on of which could be causing a problem...propwash specifically as it was the last thing that was running. Also, it would be helpful to know what you were doing specifically when you were "tinkering around". If you want to help diagnose the problem you should remove all your plugins and then re-test the Saab. If everything is OK then start putting the plugins back in one-at-a-time. If you get a crash after one of theplugin re-installs, that plugin is probably the problem.
  22. What you are experiencing is a known issue. The custom engine code for the Saab is "fighting" with changes that Austin made to the turboprop engine model in X-Plane. This has all been fixed and will be available in the next update, which will be free for you.
  23. The logs show a licensing issue. Please contact the X-Aviation store for support.
  24. You can assign the power levers to the default throttle axes, and you can assign the condition levers to the default prop axes.
×
×
  • Create New...