Cameron

This will serve as an official announcement that we have released the version 2.0.1 update for the SR22 G1000 Series. All customers who have purchased the SR22 G1000 Series 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 SR22 G1000 Series from today forward, your purchased download will already be updated to version 2.0.1 for you. 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 SR22 G1000 Series download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: New Features: Newly recorded sounds for the FMOD sound pack with new engine sounds and other accessory sounds improved! Recorded from a local G3 SR22. Further X-Plane 12 tuning and improvements! REMINDER!: ARM64 support prepped for future. (Note: For ARM64 Mac (M1+ processors) users, ensure you are running Rosetta for now. Important Note Currently, the Synthetic Vision System (SVS) is known to cause issues on some configurations when Zink is enabled. It is highly recommended to not use Zink with this version, with SVS enabled. Additionally, sporadic crashes during load have been seen on Mac. SVS is enabled by default, but it can be disabled via a config file without the sim loaded. If you are experiencing crashes with the SR2X aircraft, disable SVS by navigating to X-Plane 12/Aircraft/X-Aviation/SR22 Series/{Aircraft Type}/plugins/sr_systems/settings/. Open the file settings.cfg in a text editor and make the change to the svs line: To disable SVS: svs = 0 To enable SVS: svs = 1 Bug Fixes and Improvements: Revamped all wing and gear textures to remove unnecessary ambient occlusion Fixed gear height and operation Adjusted chock position Missing Cirrus logo fixed T-1879 Disabling aircraft doesn't reset G1000 engine bar override Icing improvements Fixed invalid dataref reference in physics plugin Livery fixes Wing open seam closed Updated libacfutils version to improve rendering of non-svs components with Zink and Mac Engine loops refined to rid the soundpack of all popping between loops Prime Pump sound refined to blend more naturally between intro and loop Engine start sound refined volume curve to allow for a smoother transition to engine sound from ignition Adjust aircraft lighting Livery fix for improper normal metal 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.

Hi Doug, This forum is for the Leading Edge Simulations Saab 340. You'll need to seek out support for the Carenado one in their proper support area.

Thanks! Keep me updated. One thing that we should eliminate is the double X-Plane 12 folder structure: X-Plane 12/X-Plane 12 It's just cleaner that way.

Hi @Herbert, Thanks for the info. Can you confirm that your SR22 retail version loads fine?

Hi there, when you're saying this, are you saying you had installed the beta X-Aviation plugin after the MU-2 install? This log seems pretty incomplete. Is X-Plane crashing, or what's happening here? It doesn't show that you're quitting it.

There shouldn't need to be one, no. The exterior UV remains the same.

We only wish it were as simple as this! In all seriousness, this has been a fairly huge undertaking. Every day is a little closer though!

I can't speak for every dev in the world, but I can tell you that the 8-12 hour day you mentioned is pretty much what's going on for devs under the X-Aviation umbrella. I would assume there's a number of the same from other stores. I'll just add that I found the v10 to v11 transition to be quite a bit less cumbersome. PBR was the biggest hurdle for most of us, but that was manageable. OBJ lighting changes was another. v12 seems to be incredibly more involved, but I do believe that to also be due to things @daemotron outlined. Devs are getting more and more comfortable writing plugins and pushing boundaries. It's great, but when we have major version changes like v12, it's a heck of an effort to get things functioning properly. I don't think a lot of customers realize this, and I know Laminar didn't help that cause when they tried to sell v12 as having backwards compatibility for v11 stuff.

3rd party devs had no say in this at all. Updating aircraft for X-Plane 12 is a huge effort, and one with which devs wish wasn't so involved. It's more productive to work on new products than to update old.

Correct. The Zink issues are related to a bug in the AMD drivers.

I'm not sure where you got that information, but no such release has occurred.

It's a major re-write of code to get it properly working in 12, and that work continues. We will e-mail all customers once this has been released.

Not yet.

The TBM is a persistent state aircraft. You will need to properly shut it down to be able to launch it the next time where you started off systems status wise. No. This functionality in X-Plane is quite basic and the TBM has too advanced a custom engine model for X-Plane to handle this properly. This is not true at all. The TBM is in constant update development at the moment.

Attila, I'm sorry you found this impolite. It's not intended that way. It is matter of fact, and while that may be something you don't like, lying to you about the situation would be worse. We don't have any intentions of going back to spend resources on a dying platform like X-Plane 11. 13% is a small amount of customers to put resources into, and that number will continue to get smaller and smaller as people transition to XP 12. The update will always be available to you and free for X-Plane 12 whenever you decide to make that move.

X-Plane 11 now represents 13% of the MU-2 user base, and that number continues to dwindle. For obvious reasons, we won't be spending time on X-Plane 11 from here on out, but will continue to make available the last working version for it.

You didn't do anything wrong. v2.1.0 only installs if you select X-Plane 12. It is not compatible with XP 11.

See here about APR mode and the GPSS button: https://www.togasim.com/mu2docs/supplements/spz500.html#fd-mode-control-panel-mcp

Please read through the docs with the link @tADEUS73 posted above. A few things for you... 1. Instead of assigning your throttle axis to throttle 1, assign it to throttle 5. This is in the pull down selection for your throttle assignment in X-Plane. 2. Read the docs in the above posted link about the detent. You'll want to pay attention to the lift command information. This will be how you get into reverse thrust.

Unfortunately a log file is not going to do anything for what you're describing. Shooting a video of what your sequence is would be good though.

I've read of a similar issue happening in a different addon. It seemed to be an issue related to Zinc. Can you try disabling that to see if the problem goes away?

https://www.togasim.com/mu2docs/setup/hardware_setup.html#honeycomb-bravo Pay attention to the lift command.

It was a direct link to all CL650 manuals. There was no ocean of information to wade through.

@jmg225 This is your third topic about this subject in just over a weeks time. Please know there is not going to be some kind of rapid change on this, and we will let you know when it happens. No need to keep asking.