JGregory

Just did a test flight. Temps and torque are a little sensitive, but I don't think it is any different than it was in 11.26. When we get to V2 these issues will be looked at, but based on our project list and schedule it's going to be some time before V2 is available.

Is that a change from 11.30b3, or a change from 11.26 ??

The bus-tie does not close in that scenario.

No. When the left battery switch is on the right essential bus is powered through the bus-tie No. The key here is that with no external power or generators to maintain the charge in the emergency battery, the emergency battery voltage will drop to below 24V. When this happens the annunciator lights up.

You stated you had a couple of questions, but all you did was make some statements. Everything you described is correct behavior. If you have a specific question I would be happy to answer.

can't be done.

Glad you got it sorted out.

There is nothing obvious in the logs to explain what is happening. However, you are several versions behind with X-Plane and I recommend you upgrade to the latest. At this point I suggest you do the usual testing: Remove all plugins except Gizmo, unplug any hardware you are using, and try again. Best thing to do is download the XP demo and use that for the test as it is a "clean" install.

if anyone can provide exact steps that can recreate this problem, we will be happy to look into it. In addition, as is always the case when reporting problems, please include your Log.txt and GizmoLog.txt files.

Your database should be fine. The Saab 530 is simply displaying the "default" DB data, but will use the custom data if it exists.

Please explain (in more detail) what you mean by "...the G530 database can not update."

The information you have provided is far too vague for us to make any determination from.

No, not like you can with other aircraft. The "fastest" way to get the Saab running is to use "Auto-Start".

No

There should only be (1) one objects folder per aircraft variant. If that is not the case for you this could be an installer issue and I would contact X-Aviation directly through their support ticket system.

Make sure that your X-Plane sounds (NOT the Saab sounds ) check box is selected, and that the volume slider(s) are in the correct position.

X-Plane has "built-in"" video recording.

Can you describe the warning in more detail? All you have described is a "red alert". Is there a specific annunciator light that is turning on, or an aural signal. Does this occur with a manual start, or also with auto-start? Maybe you could post a short video?

It sounds to me like you are confusing two different things. Auto-Coarsen and CTOT are separate systems. Please clarify what the problem is exactly and with which system.

LES/CMD/CW/button/AP_disconnect

Ummmm, this is really confusing. You stated that the problem occurs when enabling the avionics too soon AFTER enabling external power, but your first list has "turn avionics on" BEFORE enabling external power !?!?!?!?!? Your second list has the avionics being turned on AFTER enabling external power, but that is the list that you claim is working fine!!!! In any event, I tried this both ways and my power levers NEVER moved at all. This problem sounds like an issue with your hardware or an associated plugin.

Angle of Bank is not user adjustable in the Saab. You can simply use the standard X-Plane keystrokes or assign those same commands to buttons to move the lever up and down.

The symptoms you are experiencing are almost always related to scaling of your display. Search these forums and you will find many instances of the same problem.

My only suggestion at this time is to move the condition lever(s) as described above with a pause at the unfeather position. Much of the engine model in X-Plane has changed since the original code was written for the Saab. The Saab code for the engines is very complex and quite a few lines of code. It would not be prudent to "tear this all down and rebuild it" for the current version of the Saab. These kinds of nuanced issues are something that we will be addressing for v2.0.

Yes, you should "pause" at the "unfeather" position prior to moving to the "minimum" position. However, the engine should stabilize faster than 5-10m min. What are your frame rates?