JGregory

Saab v1.5.2 will have all new manipulators, new engine modeling, and some other updates/fixes. It is being worked on as we speak and will be released "VERY SOON"®. Saab v2.0 will be a complete overhaul and is planned for the "NOT TOO DISTANT FUTURE"®.

It appears you are using some Saitek hardware, please unplug this and let us know if anything changes. Pulsating engines are not normal and are a result of new engine code from Laminar/Austin in 11.3x. We are working on an update to correct this. Thanks for the video, I will look into the hydraulic switch and the trim up condition. it's difficult to tell from the video but I can't see anything wrong as it relates to the left banking tendency. Again, check your hardware.

Due to the number of plugins that you have, I suggest you do the usual test as follows: 1. Remove all the plugins except for Gizmo. 2. Load the Saab and see if the problem still exists. 3. Add the plugins back in one-by-one and re-load the Saab to see which plugin may be causing the issue.

You might want to remove any plugins that are drawing environment effects and see if that helps.

This has already been fixed and will be included in the 1.5.2 update. And, before you ask, we do not have a definite release date for the update.

Hi Guys, I ran into a similar problem yesterday in my work for Laminar. A user reported that the de-ice gauge in the default Baron was not working. Philipp (from Laminar) reworked the ice systems for 11.30. I spoke to him yesterday and here is the story... In the past the "boot" dataref was aliased to the wing_heat command. X-Plane didn't really model boot de-icing at all. That has all changed in 11.30. We now have true boot de-icing as a separate system. This will require updates to aircraft that relied on the the old wing_heat command to trigger the boots. We will incorporate a fix for this in the 1.5.2 update. Sorry for the inconvenience.

The Saab does spot have an auto-updater as you describe. Are you maybe talking about the update for the sim itself?

That should work !!

There is no command for the prop sync at this time. We may be able to include this in v1.5.2.

I am using this override without any problems.

Whoa, hold on guys. I am not aware of any Saab A or B the has LCD EADI/EHSI displays. Secondly, a "B" version would definitely not be free. And, while I appreciate your interest, 2 votes for a "B" version is FAR from what would be needed to make it a good business decision.

I like the "idea" of doing the "B" version, but I'm not convinced this would be a good business decision.

That video appears to be of a Saab 340B, which has longer wings. Longer wings = more flex. And even then, the flex in the video is barely visible. Not sure it would be worth it but we will look at this again when we get to v2.0.

Sound like you may have some personal experience. Any chance you could provide some video of this ?

The Saab wing is very rigid so I doubt there is much, if any, wing flex. As such we have not modeled any wing flex as of v1.5.1. This will be reviewed for v2.0.

1. Bank Angle: I have made several posts indicating that this has been fixed, so it's a non-issue at this point. 2. Engine/Prop Behavior: This is a much more complicated subject. And, we didn't change the engine model in 1.5.1. You haven't indicated which version of the sim you are running, which makes a considerable difference. During the 11.30 beta run, and now in full release, Austin made several significant changes to turboprop behavior at various stages. So, what you experience will be a combination of the version of X-Plane AND the version of the Saab. Now that 11.30 is final and the turboprop engine model is mostly "stable", we are reviewing the engine and prop behavior and MAY make changes depending on what we find. Keep in mind the Saab engine code is extremely complex and changes can have unexpected consequences so we have been very careful about what we do. So for me, the engine issues, while significant enough for us to look into at this point, were not "created"' by 1.5.1 but were instead caused by changes to the turborprop engine model in 11.30. My entire point is that you should be careful what you state in the forums as existing and potential customers may be negatively influenced by your comments. We can tolerate "harsh" criticism, but it needs to be "accurate".

I would be interested in a list of problems that you feel were created by the 1.5.1 release.

The 530 in the Saab is stock/default. If you truly believe something has changed in 11.30 you should file a bug with Laminar.

I spoke with Laminar and we have discovered where the problem is. We will need to publish an update to the Saab after we make some changes to the code. Stay tuned for an announcement of the update in the near future. In the meantime you can workaround this by making sure that your com radio volume slider is more than 50% for the radio you are communicating on.

This is a side affect of the new engine modeling that Austin introduced in the sim recently. Due to the complexity of the customized Saab engine code, trying to "fix" this would be very time consuming and most likely introduce a cascade of other issues. In addition, since the condition is momentary/temporary, it is not categorized as a"high priority" bug. I appreciate that the is not "normal" engine behavior, but messing with the engine code at this point could easily make it much worse. We will be addressing this in Saab v2.0.

you can always do a re-install to see if that changes anything. The screenshot you posted does not look like "...I almost slam my face into the panels", but it does look like the center of the view is too high (the black knob should be just below center). Are you running in full screen or windowed mode? Does changing that fix the problem? Also check your FOV setting. If you are using a wide-screen monitor in full screen mode, then that will alter the views. Nothing we can do about that now. If you are using windowed mode, adjusting the aspect ratio will change the checklist views. We may provide user defined views for Saab v2.0.

Please don't hijack a Saab thread with questions about the DC3. As far as when the DC3 will be released, i have no idea.

The checklist views are hard coded, so each time you load the aircraft the default values are set and they cannot be changed. I just tested the checklist views in 11.30 and did not see any changes. Has anything else changed in your installation... new plugins perhaps?

contact X-Aviation for support

Based on some other reports, it looks like 11.30 may be causing this issue. I will be discussing this with Laminar. Please post your Log.txt and GizmoLog.txt files.