JGregory

There are two different type pop-ups available. One is the "display" of the course and heading. There is also a pop-up panel that has the dials on it for adjusting the heading and course values, which makes it much easier to set these values without looking down to the center console. This pop-up panel can be displayed by assigning the appropriate command to a button or key.

Looks like a bug. Thanks for reporting. Incidentally, there is a pop-up panel available, that you can assign a button or key to, that will give you CRS1, HDG, and CRS2 adjustment capability similar to the radios. This makes it much easier to adjust when flying and you want to keep your view out the cockpit window.

Polar, It's very difficult for me to follow what you are describing. First, your views are saved with each aircraft automatically. You do not need to save a "situation" to save the views... they have nothing to do with each other. Situations are aircraft specific. So, when you switch aircraft, the "situation" is no longer applicable, and would have no bearing on the newly loaded aircraft. Therefore, the "situation" data would not be applied to the Saab. Even if it where, we override the engines and props and control them ourselves in the code, so the previous situation has no bearing on how the Saab behaves. Since I believe this issue will be resolved with the next update, I think it would just be best to wait until the update is available and see how things work with the new changes.

A condition lever (such as the Saab has) is different than a "prop pitch" lever. I was asking you to clarify because X-Plane does not have an assignment available that is named "condition lever" or "CL". In order to avoid confusion (especially when referring to the Saab) we should try to avoid using "condition lever" to describe a "prop pitch" control lever. They are two different things. Yes, I saw your previous post. Not likely, although this may be somewhat associated with what was reported here. As I stated previously, I have made some adjustments to the fuel logic (for the next update), which addresses this. Since I cannot reproduce this issue, you guys will need to report your findings after you download the next update. I'm not completely clear on what you're saying... what does "..., as well as views..." refer to? and what does ..." the saved flights remain, ..." mean? Also, when you asked... "do these settings fully get disabled?" what settings are you referring to?

Please clarify. X-Plane does not have an assignment named "CL's".

What were your lever(s) assigned to (in X-Plane) BEFORE doing this?

Yes, it is typical for most aircraft to climb at lower rates at higher altitudes.

You can't fly all the way to 25K using climb (L). When your vertical speed declines you will need to switch to "M" or "H" for the remainder of the climb.

Polar, I'm not sure what you are describing here. When you assign the CLs using the Saab pop-up, you will be told what index was assigned. It doesn't matter what the index number is, but you do need to make sure that the lever(s) are assigned to "none" in the "Joystick& Assignment" window (as described on Page 11 of the "Introduction & Settings Manual" that came with the Saab).

I can assure you that a particular airport has nothing to do with this issue. As I stated above, I believe I have a solution, it just needs to be tested. PATIENCE, please!

Guys... please see this post. I have made some adjustments in the engine model based on this feedback. However, because I have never been able to recreate this problem, I don't know whether the changes will definitely work. We will get an update out in the near future for you all to try out. Thank you for your patience.

This is a bug... thanks for the report(s). The issue has been fixed and will be in the next update.

If Gizmo didn't tell us about the "more stuff" that it wants, debugging would be much more difficult! Thanks for reporting this error, it has been fixed and will be in the next update.

Jaggo, Excellent reporting, thanks for that. I will have a look into this and let you know.

Kerry, I need reproducible steps in order to diagnose this problem (or any problem, for that matter). I appreciate the report but, without defined steps to reproduce the problem, any attempt to fix this would be like finding a needle in a haystack.

NOTHING has changed in V1.3 regarding the Course Selector(s), the GPS, or the Course pop-up display(s). As for the rest of your post... I will need to check into this. A typical HSI only displays one course pointer. However, the EHSI on the Saab has the capability of displaying 2 course pointers, which complicates the simulation. This will take some time to analyze. In the meantime... you are using the wrong commands. For now you need to use "sim/radios/obs1_up" and "sim/radios/obs1_down" for NAV1, and same except "obs2" for NAV2. At this point, when in LRN1 mode, the course pointer will show the "relative bearing" to the waypoint, although you cannot adjust the course pointer when you are in LRN1 mode. If you want to know why there is a difference between the "relative bearing" and the DTK, you should switch between VLOC and GPS while observing the GPS display of the flight path. BTW.. DTK is "Desired Track", not "Direct Track"... there is a distinction.

Kerry, As I stated previously... Auto-Start is the key to diagnosing where the problem is coming from. It has worked for you every time so far. Try it again... I'm sure it will continue to work every time. So, if Auto-Start works then the Saab is working properly and there is something on your end that is not working, which may also be causing the starter to run on endlessly. I can't diagnose your system for you. No one else is reporting engine start problems.

Kerry, Have you ever used the Auto_Start feature? I'll bet the aircraft will start correctly EVERY TIME you do! If it doesn't then something in your system is interfering with the proper operation of the Saab (hardware perhaps?, another plugin?). However, if it does start every time you use Auto-Start then what does that tell us? ... most likely user error, especially since I have not heard of this problem from anyone else. Page 125 of the manual clearly states the following... "Hold the START switch to L or R position for two seconds and release." Not doing this could certainly result in an engine not starting. In addition, if the condition lever is in the fuel cut-off position the engine will not start. Right... so the starter motor is running but it sounds like there is no fuel and/ or no ignition. It's not a blast of air, it's called "combustion", and it's a good thing. If you don't get combustion you will not get an engine start.

We need to be clear on this. First...the console will not pop-up unless an error has occured. Second...if it does pop-up you need to send us the log files from that session. Third.. If you get an error (and the console window pops up) some of the actuators in the cockpit may stop working so, when you say that something isn't working (altitude selector) you need to be specific as to whether it happened before or after an error. It could. If you are still having problems you need to follow my instructions from post #6 above.

Unplug any external hardware that you may be using (yokes, joystick, etc.). Then take ALL the non-standard plugins out of the plugin folder (except gizmo). Re-start the sim and load the Saab. If you still have problems, send us the log.txt and GizmoLog.txt files. I would also like to know what your frame rates are when you are running the Saab.

Give me a list of repeatable steps that I can take to recreate this, and I will look into it.

The overheating of batteries and lengthy cool-down is also one of the reasons they do external GPU starts whenever possible.

You may have to reset your preferences.

I love it when a simulator actually simluates real life, don't you?

That is correct.. there are no callouts.