Leaderboard

Hello All, This will serve as a formal forum announcement that we have released the version 1.5 update for the Take Command! Saab 340A. All customers who have purchased the Saab 340A up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the Saab 340A from today forward, your purchased download will already be updated to version 1.5 for you. This update brings official compatibility for X-Plane 11. It is also applicable to X-Plane 10 for those still running that platform. What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php 2. Find your original Saab 340A download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: What's New / Changed: X-Plane 11 now supported Fixed a bug with CRS 2 Dial Re-coded the CRS1 logic to better handle the GPS course adjustment Fixed a bug in the pump timer logic to test if timer is active prior to initialization New tiller hydraulic on/off button command added Fixed a bug within the sound code Fixed autopilot from oscillating in X-Plane 11 Reduced take off trim Changed radius of gyration for X-Plane 11 Adjusted engine PID logic Adjusted ITT Temperatures Aileron trim adjustments for X-Plane 11 Added PBR and new normal maps for X-Plane 11 Adjustments to glass objects and textures for X-Plane 11 As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support! Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.

I don't want to cause a ruckus, but it looks like V1.5 is now available. I'm installing as I speak.

Already downloaded Thanks to the whole development team.

TerraMaxx has been released and is now available for purchase.

Finaly, it's released!! Thanks god and Cameron <3

It's plain economics. Most vendors in the sim world (especially XP- specific I would think) are very small operations (often only 1 person) creating products for a relatively small marketplace (not really a lot of money in it). They don't usually have personnel available whose only job is to communicate to the public. Virtually nobody is getting rich in this industry and probably most don't make a full-time living at it. For the most part it is a labor of love for these creators. And anyone who has any experience with software development knows things almost always go wrong at the last minute and delays are practically inevitable. This happens with big software companies as well, but as you can imagine the smaller the company, the less resources are available to get the product out in time AND communicate with the public efficiently. This is a very simplified explanation but the moral of the story is to be patient or you'll always be frustrated. Just goes with the territory. It'll be out when it's out. Take a deep breath and enjoy all the stuff you already have! No amount of nagging on the forums is going to make the release any sooner.

like that

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

Of course, if they for compatability first checks if the file is in sounds/, report it missing and then find it in sound/system/ I would suppose it would look like this... Haven't really experienced missing sounds, but haven't really listened for them either... :-) Well,, trying to keep the logfile clean is also a virtue, so I still think it should be fixed :-)) This is maybe not the place to "request" that, but some developer might be following these threads... Back to flying :-))

Hahah, here you go! The time of crash was 12:26. I will try to remove some more plugins. debug.log GizmoLog.txt Log.txt METAR.rwx OPENGL32.log stack_trace.txt xEnviroLog.txt

Wow - fantastic news (and the Saab updated too!). Waiting for it to up on the site to purchase.

Well, please check that the documentation of your own aircraft is up-to-date before criticizing the users.

Maps you might have and the nav data you have installed in XP do not always match! Check in XP's in-sim map that you are using the correct frequency for the VOR.

KSLE to KRBG.

Flies great too!

It looks gorgeous!

Thank you Goran for the update ! This is my favourite turboprop - the most complete one. Cheers PS.If only I could hear engines at replay

Come on Chris737, don't be so meticulous For me this the only plane in XP10 that was finished product. Waiting for XP11 update....so long.

For what it's worth I personally _hate_ that this "Defender exclusion" is the solution we have to recommend. The main reasons we recommend this are; 1. The FMC code is still a work in progress. Tom is mostly responsible for this part of the project. It's a complicated beast and subject to major reworks as he learns more and fixes bugs. I could get in there and optimize all this away, breaking the code down from something an engineer has created to be "as correct as possible" into something that would run "as fast as possible". This might take me a few days or weeks depending on how long it takes me to understand the system and then re-verify that it works correctly through either automated tests or team playtesting. Then Tom might decide that the FMC code is all wrong and throw it away so that he can add more features or correct some critical flaw. ('cause lets be honest, the FMC has had more than its fair share of "Gizmo Errors" over the last year or so...) The end result is that we'd be back to another "engineers version" that's correct but probably slow again. Teaching Tom the depth of knowledge required to understand the requirements of a fast gaming loop and how to shard the work is also not really an option for either of us at this time. We have other commitments meaning that our time is genuinely better spent elsewhere. So, for now, I have to sit back and let him focus on the "as correct as possible" unti the point that the IXEG team decides that it's functionally complete. If they were to make this call tomorrow I would look at optimization immediately as this issue stinks from both a user experience perspective and a system security(placing an exclusion on the X-Plane folder means other plugins for other products will be ignored by Defender*) perspective. 2. Lua JIT. We use Lua JIT to run our systems code as fast as possible. The JIT engine marks a large block of RAM as write+exec.... it _must_ do this to be able to do it's job, that of translating Script into Machine Code on the fly. We could move to straight Lua and this issue would go away but frame rates would likely plummet. Something no one wants. Sometime in the future this will no longer be an issue. Thanks for using our products.

Can You sent me this 777 , since i updated to xplane 11 , i really really miss the pmdg aircraft , ahoyhuman10@gmail.com =))

So, I installed Gizmo and the Saab 340. I now get frequent crashes in X-Plane 11 when flying the Saab, I do not see any major hints in the logs, but I have a suspicion what the culprit is. I think there may be incompatibility between Gizmo and xEnviro, either Gizmo or xEnviro makes X-Plane crash. Looking at the log of xEnviro, I do see at the time of crash it is polling for weather data. Reason I am posting here in the forum is that this Saab version is new, and it may not be a incompatibility between xEnviro and Gizmo, it can instead be a bug in the Saab, or it can be incompatibility between Saab and xEnviro.