JGregory

Steering, flaps, and brakes are the main hydraulic consumers. With the plane sitting on the ramp and not moving, the pump SHOULD NOT cycle every 65 seconds. Re-installing the aircraft would not change this. What version are you using?

No.

In the real aircraft there is a _SLIGHT_ delay, which we had modeled. What some users are reporting is a _SIGNIFICANT_ delay, which is NOT CORRECT and certainly NOT A FEATURE!

Which feature? If some users are seeing a significant delay in going from reverse to beta, that is not a feature!

Wait! You were hoping we wouldn't fix it, but you think it is awesome that we did? Am I reading that right?

Goran and I have both tested this, with hardware and with just the mouse and keyboard. Neither of us have any problem taxiing after landing, whether we used reverse or not. However, this was done with the latest dev version, which is not out to the public yet. My guess is that this issue has been resolved as part of some of the other updates/fixes we have done. I'm not inclined to consider this a problem (bug) until you guys have the next update and can try it. No release date yet... stay tuned.

My point was that you shouldn't need a "workaround". If this is a wide-spread issue we will certainly look into it.

This is exactly how we programmed the Saab. It does NOT matter what position the Condition Levers are in, as long as they are between MIN and MAX, when the Power Levers are in BETA. The prop pitch is controlled by the Power Levers while in beta and the "computer" will attempt to maintain prop rpm at a constant speed. You should not see any difference in ground handling with the Condition Levers at MIN or MAX.

Settings > Joystick & Equipment > Buttons: Adv (click box in upper right corner for custom commands)

You should assign your button to the Saab AP command.

You sure about that 5-10 seconds? There is a delay while the prop pitch changes, but I don't think it takes that long.

The engine fire issue was already reported, has been fixed, and will be in the next update. Did this happen after you restarted X-Plane? or did you try to fly the Saab after the crash without restarting the sim?

You are running an old version of the Saab. Please update and try again.

There is no mention of any attempt to load the Saab anywhere in those logs.

Ahhh... so that clears things up a bit. (ILS is not omnidirectional). Try using this.... sim/cockpit2/radios/indicators/nav1_relative_heading_AHARS_deg_pilot

Maybe someone else is using the same hardware you have and can help out. Since we have had no other reports of this issue, I can't really offer any other suggestions. The good news is that the CL assignment has been eliminated for the next update. Can't give you an exact release date at this point.

I believe that is part of a third-party add-on for handling hardware assignments, which I am not familiar with.

The CL joystick assignment simply looks for the "slot" that your hardware is assigned to. It DOES NOT do anything to the axis. So, there should be no change in behavior after assigning the CL. No.

The Saab simply takes the input values (0.0 to 1.0) from the joystick DataRef and uses it to determine the position of the condition levers. If the status bars are showing full range but the levers are not animating properly, something is not calibrated correctly. Maybe try reversing the levers from throttle to condition lever and vice versa and see what happens.

When you look at the status bar in the joystick and settings window, does it travel the full range?

Is the MFD built with generic instruments?, or is that a default instrument? In any event, I would really need to have the aircraft to diagnose the situation. However, I still believe that the "sim/cockpit2/radios/indicators/nav1_relative_bearing_deg" is the correct one.

I suggested the use of the DataRef with "relative" because it is "in relation to the current heading" or HSI compass rose. You second screenshot shows the pointer at 90 degrees, which I believes is the default position when there is no signal to the radio. Make sure you have a NavAid tuned in that is in range.

You should probably be using this... sim/cockpit2/radios/indicators/nav1_relative_bearing_deg

This is a known issue that has been fixed and will be in the next update. As a workaround you can open any other aircraft that has an altitude selector and change the altitude ( to something below the Saab maximum) ... then re-open the Saab and it should be fine.

Did you even read the thread that I linked to? It clearly states that this was a bug, it has been fixed, and will be in the next update. So, no, the fire extinguisher DOES NOT always fail in X-Plane.