Cameron

Yes.

You have the latest. Said update has not yet been released. The last update was released in April. Saso's post was made in May.

Can you send me a screenshot of the white box you're talking about next time you see it? These issues sound very strange and not something I get typical reports on. It makes me think something else is amiss during activation.

Which white box is that? Also, after authorization the entire Gizmo system from which the Saab runs is rebooted. It's effectively the same as restarting the sim. Is there a hydraulic issue you really have consistently? Or, is the poster just talking about the intermittent, though persistent, sound of the hydraulics as you fly?

I'm glad you got it sorted.

Login with your username and not your email.

Nevermind, we added that recently and I forgot, so my apologies. What you're referring to is the Gizmo menu bar. You'll find that by going to the plugins menu and making the menu visible in the Gizmo64 preferences.

The MU-2 has no such menu.

The manuals definitely cover the autopilot. Sounds in replay is a known thing. They simply don't work in that mode.

Machine ID locking is the result of you locking your own machine. As is specified in the screen, once you de-authorize a machine and confirm it by typing 'FREEZE', a machine cannot be re-activated.

There will be one more update free of charge to address bugs and add a few more items. Barring any bugs caused by X-Plane 11 going forward, the next update will be considered the last prior to 2.0. We don't anticipate that release till likely sometime later in 2020. In short, it is safe to purchase now. All customers who purchase the current Saab will also receive a heavily discounted 2.0 update.

In this instance not so much. Unfortunately, in order to use the newer versions of Blender all animations must be re-done. They don't carry over from older versions that the Saab used. Long term outlook it's necessary though!

That is correct. You can, however, run the auto start function once the plane is loaded. That can be accessed by moving your mouse to the right side of your screen. A menu will pop out and you will want to select the auto start icon.

The Saab 340A is a study level simulation that cannot be started with engines running. Please read the included documentation. It should cover everything you need to know.

At the moment there really hasn't been much behind the scenes talk on other variants. For now the focus will be just perfecting the -300 and if it makes sense to do the others we will. It's definitely nowhere close to the top of the list though (as much as we would love to do them)!

Hermann, It would seem likely you were either running X-Plane during install, or X-Plane didn't properly shut down. So, you'll need to either properly quit X-Plane or restart your computer before installing the TBM.

Please note activation questions are not discussed or dealt with in forums. Typing FREEZE is a deliberate process to de-authorize a machine for good. There is no intended recourse for this. You may contact support@x-aviation for any potential correspondence on this, but not on forums.

Yes, it's for both P3D and X-Plane. PILOT'S makes the installer, not us.

Bear in mind none of the new features in FSGRW with SMP will be displayed unless running v4. Sounds like you are on v3, so you will not see the full potential in this situation.

I believe what you're seeing here (aside from the fact an iPhone captured images of it even brighter than you're seeing it in person, so makes it look even worse) is the result of 32-bit colors being portrayed best they can on a monitor vs thousands or even millions of colors and proper shading in certain scenarios in things like photos or everyday life as a whole. There's no pixel issues, just harsher gradient shading when less colors are allowed.

Have now checked on my second computer. Still do not see any kind of polygons.

Same thing in your Dropbox images. Nothing but black sky on my end, even in circled regions. Even when I zoom in.

Full brightness on an OLED I cannot see anything but the black sky in your circled areas.

Your night with SkyMaxx Pro shot shows clouds above the plane against the sky and stars. Aside from that I can't see any difference of pixelation difference between either image in the dark sky on my monitor.

FSGRW will always provide much better cloud representation when necessary compared to ASXP if SkyMaxx Pro is in use. This is because of a cooperation between the developers to add more features when the RWC+SMP+FSGRW combo is used.