JGregory

I am the person who came up with this "idea". And I'm pretty sure I will not be getting "sacked" any time soon, but thanks for the suggestion. It's always amazing to find how some people think they know more about how something should be done than the actual developers of the product. There are many reasons for the path we chose. And I'm sure glad you were not part of the process. Despite thinking that you know "everything" there is about aircraft development for X-Plane, you are apparently blissfully unaware of the fact that Austin is still updating the engine model, more specifically the turboprop physics. We, on the other hand, are acutely aware of what is going on and will release our products at the exact right time based on all the factors involved, not just some uninformed customer's opinion. You have no clue what goes on behind the scenes with our development process, so stop posting garbage here as if you do There are some developers who have "rushed" their releases for XP11 just so they can say they did it. That's not how we operate, and nothing you say will change that. Go troll somewhere else.

The functionally of the heading knob and the turn knob are currently similar, they strictly set the heading for the autopilot. This will be reviewed for accuracy in the process of development for v2.0.

There is a bug in 1.4.1, which has been fixed and will be part of the next update.

That would not account for a discrepancy of 7000 ft. between altimeters.

That has always been the case. Due to X-Plane replay structure the custom sound engine used in the Saab does not play back sound in replay mode.

Yes, the hydraulics for the nose wheel steering are turned off automatically after takeoff. Therefore, the hydraulics will be disabled upon landing requiring you to turn them on. There is currently no command to do this. I have added a new command to do this, which will be part of the next update. Be aware that attempting to turn the hydraulics on while in flight will not work, you will still be required to turn on the hydraulics after landing. No, you cannot map the condition levers to a button. This can, and should, only be controlled by an axis controller, not an on-off button or switch. I'm not even sure how you are getting that to work with the throttle levers.

We just aspire to reach such lofty levels as the IXEG team... so we "borrowed" their name of the license agreement.

Ummm... Q400? I'll assume you just mistakenly wrote that. Your frame rates are far too low to guarantee that anything will work right. The autopilot input is modified in the Saab, but the output is mostly X-Plane.

Alex, This has been discussed elsewhere on the forums. The problem has been fixed and will be in the next update. See here.

According to the GizmoLog.txt an error occurred in one of the scripts, which could account for some of the odd behavior, but I can't guarantee it. The cause of the script error will be researched and fixed asap.

You need to tun the hydraulics on for steering, using the tiller (push-pull).

Wait for the update.

@stayup There were some bugs in the EHSI pointer code as well as the course selector code, which I have adjusted. I'm fairly certain this is now working as it should. However, just to be clear, in your screenshot the course pointer is simply not set to the gps course. As you can see the gps MSG field is highlighted in yellow and, if you selected the MSG button, you would see a message telling you to tune the proper course. So, the needle will be where you set it. It does not automatically adjust to the gps course.

@Pontus The bug has been confirmed and fixed. Will be part of the next update.

Both wipers should work. We will check the animation.

Nothing obvious, but you are running a lot of scenery and plugins. How are your frame rates? You may try removing other plugins and see if that does anything. Other than that, and without any further info (ie. airspeed, weight, vvi, cg, etc.), I'm not sure I can offer any other help. As of right now no one else is reporting this type of problem. There are really no significant flight model changes in this update that would account for this type of behavior.

@stayup Thanks for the file and the screenshot. This may take some time to investigate, but I will check it out.

This is a known bug (see other forum posts), which has been fixed and will been the next update.

Please post your log.txt and GizmoLog.txt files.

Thanks for the screenshot. This issue can be easily "fixed" for v11. However, It is more likely this will be part of Saab v2.0, rather than v1.5.

Please post your log.txt file and GizmoLog.txt file from immediately after a sim session in which this problem occurred.

My quick guess is yes, you were probably too slow. However, in order to provide proper support, please post your log.txt file and GizmoLog.txt file from immediately after a sim session in which this problem occurred.

Pontus, You attached an incomplete log.txt file. Please send the ENTIRE file from immediately after a session in which the problem occurred. However, I'm not sure if this is the problem, but you have misspelled the commands (type maybe?) that you listed above. They should be "knob", not "knop".

Do you have a link to where you reported this problem in the previous version

Post your GizmoLog.txt and log.txt files please.