Jump to content
Goran_M

Saab V1.5 Status

Recommended Posts

3 minutes ago, JGregory said:

This (sound) bug was fixed in v1.4.1.  Please make sure you have the correct version installed.  The GizmoLog.txt file should be showing this....

LES: Load Saab 340A Scripts - v1.5
LES: Load Saab 340A Hot Fix - (None)

Your log file does NOT show that.

 

Hmmm... I downloaded the latest and greatest Saab_340A_1.5.zip (containing a S340A-windows-installer.exe dated 2018-03-16 22:08) this morning and ran the installer. It stated that it was uninstalling the previous version, then installed the new one... Really followed the instructions "to the letter" AFAIK/can remember... I can certainly redo it and explicitely uninstall the previous/now current, version before running the installer...

10 minutes later - Cleaned out the old version "by hand", also removing the old GizmoLog.txt. Reran the same installer. Now, as you say, the problem is gone and "all is fine" - I do see the two "LES: Load Saab 340A..." lines in the log.

But, that does give a possibility that the general upgrade path isn't always working as expected... But, since my initial installation was (partly?) removed by my first try, it's hard to regenerate the behaviour...

One observation though - With the latest installation I'm unable to get the Gizmo Console to show... There is a GizmoLog.txt file and it says "Called: Console_OnShow", but nothing visible happens when I trigger the Console (top button on the right edge Gizmo menu). The other entries work, but the console is gone...

Share this post


Link to post
Share on other sites
6 minutes ago, JAdata said:

One observation though - With the latest installation I'm unable to get the Gizmo Console to show... There is a GizmoLog.txt file and it says "Called: Console_OnShow", but nothing visible happens when I trigger the Console (top button on the right edge Gizmo menu). The other entries work, but the console is gone...

It could be that the window is "off screen".  Go to Plugins > Gizmo64 > Gather Windows, and see if that corrects the problem. 

Glad to hear the other issue is resolved.

Share this post


Link to post
Share on other sites
7 hours ago, marpilot said:

Besides, when you open another aircraft after SAAB you have broken steering....

Can we avoid this?

The only solution seems to reload X-plane 11.

This is a bug and has been fixed.  We will advise on how to get an update.

  • Upvote 1

Share this post


Link to post
Share on other sites

I fixed my sound issue by un/reinstalling.

Apparently, (for me anyway) checking the Cargo version of the aircraft (not the Cargo liveries) resolved my "no engine sound" issue. Whatever, it works now.

Thanks.

Share this post


Link to post
Share on other sites
5 minutes ago, Lorenzo.D said:

ctd at my first flight.

Log.txt

Try without xEnviro just to be sure. More often than not the reports we see with CTD's are resolved with this removed for some reason.

Share this post


Link to post
Share on other sites

Just a note here regarding installing 1.5.  For me, allowing the installer to do the uninstall ended with a non-upgraded version of the Saab.  I had to manually start the X-Aviation uninstaller (windows control panel | uinstall)...after it completes I still had over 500MB of files in the still remaining folders), then delete the entire saab folder.  Running the installer after that corrected the problem I was having.  Prior to this manual deletion step and after running the 1.5 installer, I was, apparently, running all or partially v1.3.  

Cheers.

Share this post


Link to post
Share on other sites
1 minute ago, gpb500 said:

I still had over 500MB of files in the still remaining folders

This would likely be liveries, especially third party one's, or any you downloaded with the Livery Manager after initial first install of 1.3.

1 minute ago, gpb500 said:

For me, allowing the installer to do the uninstall ended with a non-upgraded version of the Saab.

Actually, what you got was fully upgraded and installed. What we've seen on some machines though is that in addition to the new code files, some installs will retain new and old, and the old get loaded before new. I'm looking at ways to work around this appropriately.

Share this post


Link to post
Share on other sites

There were some liveries, but it left the cargo and other option in full.  I had not selected to install those but they were not uninstalled.  Could that be the issue?

1 minute ago, Cameron said:

Actually, what you got was fully upgraded and installed. What we've seen on some machines though is that in addition to the new code files, some installs will retain new and old, and the old get loaded before new. I'm looking at ways to work around this appropriately.

Yeah, certainly not "fully upgraded and installed" but it seems to be now.  Thx.

Share this post


Link to post
Share on other sites
2 minutes ago, gpb500 said:

There were some liveries, but it left the cargo and other option in full.  I had not selected to install those but they were not uninstalled.  Could that be the issue?

No, but it definitely should not have left them in full, and I'll take a look into the code as to why that may happen. Some of these OS's are very finicky about deleting files properly when commanded, so a small battle.

2 minutes ago, gpb500 said:

Yeah, certainly not "fully upgraded and installed" but it seems to be now.  Thx.

In a technical sense, yes, it was fully upgraded and installed. What it was not was fully upgraded and loading the newest code because of old lingering code files that should have been deleted.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×