JGregory

Do you have "Use Auto Latch" checked or unchecked in the User Preferences ?

**************** 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.

We DO NOT recommend or condone changing any files associated with the Saab!!!!

No.

Yes

Just download the Saab again, that should fix the issue.

Just download the Saab again, that should fix the issue.

Window ice effects should be working.

You're going to have to be more specific than that. If you're referring to..... "FLIGHT: LFBO AFRI5B BRUS6T LFMT ILS 30R - FL120", then , as I already stated, that bug was identified in 1.6.1 and we explained that we were looking into the problem in the release notes of EVERY update we made after that. Why would you keep flying in an area that we told you would be a problem and then complain when you get a crash??? It's the SAME bug that has been there all along!!!!! And, as I ALSO already stated, that bug has now been fixed and will be in the next update (1.6.5).

This is NOT NEW. We have made everyone aware that we were working on this with every update we did. It is now fixed and will be included in the next update (v1.6.5). I'm not sure what that means. I have not had any reports about problems with reverse. I told you this was fixed in another forum post. The fix will be available in the next update (v1.6.5) I have no idea what that means!

I can confirm there is a bug here. However, this was totally unrelated to the previous "No deviation G / S" bug Prosco mentioned above in the OP. I won't bore you with the details but this was related to the unique situation where Rwy 10R and Rwy 28L use the same frequency but 10R is an ILS and 28L is just a localizer. And just an FYI... videos are helpful but most times they are not enough to help diagnose a problem. We always first ask for a log.txt. When we do that it's not because we are "not taking you seriously", it's because we want all the information that is available in order to diagnose and solve the problem. Sending a log.txt AND a vide/screenshot is usually the best way to show us what the problem is. In any event, the bug fix will be part of the next update.

Always attach your log.txt file when reporting a problem.

probably/maybe ?

The engines are NOT operating outside the AOM parameters.

Thanks for the video, I'll check it out.

Huh ??

The engine speed is NOT beyond the limits. What you are seeing is partially due to viewing angle.

I hope most of what you said is a "translator problem", otherwise it's simply insulting.

I cannot recreate this problem. Auto-Start is NOT changing the Auto Latch Preference. You will need to send me a video showing the TQ Viewer and the User Pref window when you are experiencing this problem (including using Auto-Start). Until then I am considering this a non-bug.

OK guys, I think I found the problem. Should be a fix in the next update

Why is the trim at max up in the first picture with A/P disengaged? Did you move the trim to that position before takeoff? We do not manipulate the ap and trim interaction in any way. If it is different from 1.5 then it might be changes that Austin or Philipp have introduced over the last couple of years. However, since most users are not reporting this I tend to think there is something else going on here.

Then my guess is there is something odd in that custom scenery.

We are aware and have logged this issue in our bug reports.

Your trim is indicating significant nose-up in ALL of these screenshots ! Try trimming for neutral prior to engaging the autopilot.

That's probably a bug. I will look into it.