Jump to content

JGregory

JGX-Designs
  • Posts

    2,242
  • Joined

  • Days Won

    20

Everything posted by JGregory

  1. There are many changes in XP12 that need to be incorporated into the Saab. Whether that happens in the Saab v1 or v2 remains a question, but it will happen at some point.
  2. Your log.txt is being flooded with data from 124thATC, which is NOT GOOD. Although this makes it harder to read the log.txt file, I don't think it is related to your AP disco issue. I don't see anything else obvious in the log.txt file. It's possible something else is interfering with the Saab. I would try removing your 3rd party plugins (except Gizmo, do several test flights, and let us know how it goes. No one else is reporting this as a problem so it must be isolated to your system ( plugins, hardware, etc.) or pilot input.
  3. Not enough info. What is your bravo switch bound to? Also, please attach your log.txt file.
  4. The physics model (created in PM) is the ONLY thing that will determine whether it flies or not. The visual model is exactly that, JUST visual.
  5. You can bind the following to engage/disengage the autopilot. Note that in order to silence the disco alarm you will need to use the red button on the yoke.
  6. JGregory

    TQ Viewer

    Try to bind to this command... "JGX/SAAB/POPUP/TQ_viewer/CMD/showPopUp"
  7. There is no way to know this for certain. So far the plane loads and flys in v12. But, Austin has made engine model changes that we do not have yet. I am hoping that any changes will be minor and be part of a free update if necessary.
  8. Animation datarefs in the Saab are not writable. You will need to use the commands as mentioned above. In addition to setting the animation value, those commands will set the sim dataref "sim/cockpit2/autopilot/airspeed_dial_kts".
  9. If you want the DH to be 600, then set it to 600, not 6. The DH will stop working below 5. Set it to 600 when you are descending to land and your altitude is below 2500 ft.
  10. There are three minutes between cycles when using "CONT". Turn on the "BOOT IND" and observe the annunciators as they cycle between the diff boots, then extinguish for 3 minutes, then cycle again. I have no other reports of this not working.
  11. That's news to me! Do you have the latest release?
  12. The clock(s) in the current version of the Saab only indicate local time. And, the second hand in the current version of the Saab is not animated for sweep, rather it is discrete seconds.
  13. It is unlikely that this will get solved by you waiting for another user with a "magic" solution. if you are unwilling to download the trial versions of XP, then at least remove ALL of your plugins, remove ALL of your custom scenery, and unplug all of your hardware from your current install and then test. If the problem persists at that point post another log.txt file from that session. Diagnosing problems is a process, please follow the suggestions of those who are trying to help.
  14. The Saab does have rain effects, although they are not the "modern" version.
  15. JGregory

    Weather radar

    I tested this not that long ago and it worked as expected. Did you have the weather set for clouds/rain ?
  16. Your throttles need to be in sync with the cockpit manipulators. Use the TQ Viewer pop-up to view the position of your hardware and the manipulators. In addition, there is a Flight Idle Latch that will prevent you from moving the throttles below FI under certain conditions. The user preferences allow you to choose how to handle this. There are several posts on these forums that describe this in more detail.
  17. You should upgrade to the latest version of the Saab.
  18. Please post your entire log.txt file immediately after the error occurs.
  19. This is a known issue. At this time we cannot give you a date as to when this will get fixed.
  20. A search of these forums would have gotten you the answers you need! Regarding the Throttles.... **************** IMPORTANT: MAKE SURE YOU READ THIS !!! **************** NOTES: (Power Lever Auto-Latch / Flight Idle Stop) We have partially implemented the Saab Flight Idle Stop System. The logic for the system is complete. The annunciator is not modeled. The Override Knob is not modeled. This new feature should provide much better functionality during the landing phase. This feature provides an automated "safety stop", which prevents inadvertent movement of the Power Levers below flight idle when in flight. This is separate from the Power Lever Latch. As a part of this new feature we have redesigned how you use the Power Lever Latches. You now have two options: 1. Use the Power Lever Latches exactly the way they are used in the real world Saab. 2. Have the Power Lever Latches "automated" in sync with the above described new Flight Idle Stop feature. If you choose to NOT use the Auto-Latch then you will need to manually engage the latches on the Power Levers in order to move them below the Flight Idle position. You will only be able to do this when the Flight Idle Stop is Open If you choose to use the Automated-Latch then you will not need to use the latches at all, they will be automated in sync with the Flight Idle Stop. Just remember, this does not eliminate the Flight Idle Gate, you will still need to wait for the Flight Idle Stop to open in order to move your levers below the Flight Idle position. You can choose which option you want to use in the User Preferences Window. When you load v1.6.4 the option should be set to "unchecked", which means you want to use the latches as they work in the real world Saab. If you want this to be automated you will need to check the option for "Use PL Auto Latch". In addition, all other preferences will be reset when you install v1.6.4 and you will need to set them accordingly. The red line for the Power Levers, visible in the TQ viewer, now indicates the status of the Flight Idle Stop. In v2.0 you will be able to see the status of the Flight Idle Stop as an annunciator on the FSP. You will still need to keep your hardware in sync with the cockpit manipulators. Use the TQ viewer in the menu to see if your hardware controls are in sync with the cockpit manipulators. ______________________________________________________________________________________ Regarding the nosewheel steering.... NOSE WHEEL STEERING: 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)
  21. Sal, All the variants are affected by the plugins. Follow the instructions I posted above to test the plugins. The variant you use for the test does not matter.
  22. OK. So now you will need to to some testing. Remove all the plugins from your plugins folder (except Gizmo). You can't just turn the plugins off, you need to remove them. Launch X-Plane and re-load the Saab and test. If you still have problems then post your log.txt from that session. If everything is working as expected then put the plugins back in the folder one-at-a-time, reload the Saab, and test again. If, after you've put back a plugin, the problem returns, then that plugin is causing a conflict.
×
×
  • Create New...