JGregory

That is correct.. there are no callouts.

Please be specific... what do you have your joystick mapped to? If you are referring to the Condition Levers, they need to be re-mapped anytime you re-start the sim or re-load the Saab. Also, the Throttle Levers need to be at Ground Idle for startup. This tells me that the scripts are not running. If the console window pops up and there is a line with red text.. that is an error and you should send us the logs immediately. The logs you attached do not have any reference to an error related to the user preferences. The GizmoLog is basically indicating that there are missing files. I don't know how that can be if you did a fresh install. Please verify that the following files are installed... Aircraft -> X-Aviation -> Saab 340A -> Passenger Variant -> resources -> files -> S340Adate.txt Aircraft -> X-Aviation -> Saab 340A -> Passenger Variant -> resources -> PLII -> -> files -> PLII_WDGT.txt Also please check the Cargo and AEW variants as well.

YES!, you are! As explained several times in this thread, to silent the AP disco warning you press the (red) button on THE YOKE. That is the ONLY way to silence the alarm. The command for this is separate from the AP engage/disengage on the center console.

The doors being open mean that the scripts are not running. Since all variants are not working and no one else is reporting the error you have, my guess is the aircraft and/or Gizmo is not installed correctly. You will probably need to uninstall and re-install. If you don't know how to do that, Cameron can direct you.

This has already been addressed and will be in the next update.

From what I can tell, you are missing a file. Are you able to load any of the other Saab variants (Cargo, AEW)? If so, do they work OK?

You have the wrong (old) scripts installed. Suggest you do a re-install. If you don't know how to do this, Cameron can help out.

To all concerned.... After further review... the drag manipulator on the pilot's altimeter will be adjusted for the next release. There is no scrollwheel capability on the altimeters. The pilot's altimeter and standby altimeter are synchronized. The copilot's altimeter is independent.

Exactly!

Again, the words you use to describe things are important. It may be hard for YOU to engage the AP on climb, but I can assure you that is not the case for others. If you find it difficult to look down to the center console to engage the AP, simply assign the custom Saab command for AP engage to a button or key... it couldn't be easier.

This issue has been addressed and will be in the next update.

Because X-Plane's logic for the baro DataRef causes it to jump when adjusted directly, we are using an intermediate custom Dataref for the baro setting. Therefore, you will not be able to use external hardware, XP commands, or other scripts to adjust the baro setting. It's the price we must pay to get the adjustment to work properly.

]This was reworked during beta and we had NO further complaints. When you say ..."almost the whole screen width", are you zoomed in to the altimeter? That would explain it. Saying " Scrollwheel operation does not seem possible." is quite vague. You will need to explain in more detail WHY it does not "seem" possible. The scroll option works very well on the pilot's altimeter... scroll to get close to the value, click to refine. Or perhaps you were referring to one of the other altimeters in the aircraft? You need to clarify.

I had explained this previously, but it may have been in the beta forums so I will do it again. The neg and pos on the commands define the physical movement of the switch, neg being "switch" down and pos being "switch" up.

Shown where? Did you intend to include a screenshot? The altimeter has no bearing on the value selected with the Altitude Selector, and vice versa. There is NO relationship between the two. Whatever you are referring to is purely coincidence. Have you tried setting the altitude selector to zero, as I suggested earlier?

No.

Martin, What you are seeing IS an error, and could affect the Collins radio pop-up. Thanks for including the log reports, they were very helpful. I will check this out further and let you know. Update: I am going to send you a file and instructions via PM.

Perhaps if you told us what you want to do, we could help.

You might try setting the value at zero and see if that re-aligns the tumblers. Are you using external hardware for the altitude selector ?

Nothing has changed in V2.0 that affects the battery switches.

Obviously it is not meant to be in the OVRD position, except for emergencies. This will override the thermal protection. Experiment at your own risk.

No promises.

if we provide a way for you to use your existing mapping, would that satisfy your needs? OK, I have added a feature where you can use the XP commands to trigger the AP disco. If you map to any of the following commands, you will get proper functionality of the Saab AP disco: "sim/autopilot/servos_fdir_off" "sim/autopilot/servos_fdir_yawd_off""sim/autopilot/servos_fdir_yawd_trim_off" Hope that helps!

Why is this is a "problem" ?

I think this is an issue. Since everything worked fine after you unmapped the CLs, I think you've answered the question as to why the problem is occurring. The CLs should NOT be mapped to prop1 or prop2.