Jump to content

JGregory

JGX-Designs
  • Posts

    2,256
  • Joined

  • Days Won

    23

Everything posted by JGregory

  1. The issue with the right condition lever @ "start" is a known issue and it is being worked on for the next release.
  2. The "hold" brake issue has nothing to do with Gizmo. We simply didn't include the commands in the 1.6.0 release. This will be fixed for the next release. The "v" and "b" keys (commands) work for braking in 1.6.0.
  3. The beta lights have no bearing on whether or not you can move from flight idle to ground idle. My guess is (if your using hardware) that your hardware levers are out of sync with the manipulators. We will look into the door problem. The overhead panel door annunciators are a known issue and are being worked on.
  4. This is a know issue and we are discussing it with Laminar.
  5. Your hardware is out of sync with the manipulators.
  6. That doesn't sound right. It should only blink when you change autopilot modes. If you can provide the EXACT steps to recreate this we will look into it.
  7. Right, as I said vertical movement of the camera could put you outside the prefill object, which is what causes this. The you shouldn't have this problem as your head (camera) won't move with acceleration/deceleration.
  8. Tim... when I replied to you and said this was "confirmed by our Saab pilot beta testers" that was a confirmation that the switch should be in the "ON" position when the aircraft is loaded. We will not be changing this. I have edited my previous post to be more clear.
  9. I tested it and movement of the camera was the problem, and yes it can occur vertically as well. Perhaps you have a plugin that is managing head movement on its own?
  10. Exactly! Your hardware is NOT in sync with the manipulators. Move them so that the green boxes (your hardware) align with the yellow lines (the manipulators).. at which point they will sync and move together.
  11. No, it was confirmed by our Saab Pilot beta testers that the switch should be in the "ON" position on aircraft load.
  12. Correct... there is a bug in the climb function and we are working on it.
  13. That means your hardware is out of sync with the manipulators. You can observe this using the TQ Viewer.
  14. The reason the "blue" is appearing is because you have moved the camera behind the rear wall of the cockpit. If you want to see more of the cockpit laterally adjust your FOV, not the camera position.
  15. All of the datarefs and commands associated with manipulators have been changed for this release. You will need to re-assign your keys, buttons, switches, joysticks, etc.
  16. EXPERIMENTAL FLIGHT MODEL: We suggest you do not use the EFM. We never know when Austin will add new things to the EFM, which may cause issues. Therefore, it is our recommendation that you do not use the EFM and only use the current stable release of X-Plane. That being said, you are free to experiment and try it as you wish. --------------------------------------------------------------------------------- NOSE WHEEL STEERING: There seems to be some confusion on how this is implemented. We have provided two (2) options (selectable in user preferences). 1) Use Tiller Checked (ON) - This allows you to use the in-cockpit tiller (manipulator) to steer. 2) Use Tiller Unchecked (OFF) - This allows for mouse/hardware steering. In addition... steering is only available when the following criteria are met: • On the ground (WOW) • Hydraulic PSI >= 1500 • Aircraft is moving • Tiller is engaged (depressed) --------------------------------------------------------------------------------- HDG/SLAVE BUTTON:. This was incorrectly modeled in previous versions of the Saab. It is not meant to "sync" the A/P bug with the aircraft heading. The actual functionality is as follows : "The system contains a quick heading slave function, which by means of a push button, slaves the magnetic heading related to present flux detector readout." Since X-Plane now accurately simulates gyroscopic drift and flux_detector errors, that functionality is now modeled correctly. ---------------------------------------------------------------------------------
      • 3
      • Upvote
      • Like
  17. It's a know issue and we are working on it.
  18. NOSE WHEEL STEERING: There seems to be some confusion on how this is implemented. We have provided two (2) options (selectable in user preferences). 1) Use Tiller Checked (ON) - This allows you to use the in-cockpit tiller (manipulator) to steer. 2) Use Tiller Unchecked (OFF) - This allows for mouse/hardware steering. In addition... steering is only available when the following criteria are met: • On the ground (WOW) • Hydraulic PSI >= 1500 • Aircraft is moving • Tiller is engaged (depressed) This is a known issue we are working on. Make sure your right condition lever is in the start "detent" using the manipulators in the cockpit, that should get you going for now.
  19. Will look into this.
  20. If you map the condition levers to "PROP" then the default keys for prop adjust will work.
  21. No. We will consider this for v2.0.
  22. 1. Heading/Slave button is working as expected. It is NOT a Heading Sync button. It is for gyro/flux-detector error correction. 2. The airspeed bug is a known issue and will be fixed for the next update.
  23. Hold commands are not currently implemented, will be available in the next update. The "v" key and "b" key do currently work. The pitch wheel is controlled by a dataref manipulator which requires a drag. We may include some commands in the next update to manage this.
  24. The next update will fix your issues.
×
×
  • Create New...