Cameron

The fix is also not one that will come from Gizmo. Saso simply gave insight on that licensing is done via that method, but it's not where the fix will come from. It's the side that interacts with Gizmo within the TBM plugin. Gizmo has been around for ages, and @sundog as well as many other developers have made many products that all interact just fine cohesively without any issues. Since you're an active Discord user I'm sure you're aware you can further live chat with Saso about this there @Jakob Ludwig

I'm sorry you are disappointed. I refer you again to Saso's response.

Machine IDs can only get locked if you lock them yourself. As described when you do this, this is an irreversible action and why we force you to type "FREEZE" when you do this.

I think the last sentence in Saso's post above is what you need to focus on.

Gizmo is a part of the TBM install and is managed by the installer. The error indicates X-Plane is either still running or did not properly shut down and unload plugins when you last quit it. If that's the case you will want to restart your computer and run the install again.

Hello All, This will serve as a formal forum announcement that we have released the version 1.1.6 update for the TBM 900. All customers who have purchased the TBM 900 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 TBM 900 from today forward, your purchased download will already be updated to version 1.1.6 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 TBM 900 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: Improvements / New Features: Implemented new LOC guidance code to work around the need to set CDI to front course. Implemented YD phaseout with airspeed. Added multi-threaded rendering support for synthetic vision. SYN VIS should now be much cheaper on performance. New rain effects using async compute. Available only on Windows & Linux. Mac gets the old rain effect. Implemented the "Vertical track" audio message. Made SYN VIS horizon headings more readable by adding darker outline. Redesigned steering force control logic to better handle centering forces. Bugfixes: Steering had a confusing delay on it, which made for difficult directional control. Turning on NAV or STROBE lights should disable red wingtip beacons. Overspeed should come on at 269 KIAS and turn off at 268 KIAS. Reverse numbers should be 27-35 trq, 1850 rpm, Ng 85%. Gear manual extension rates were incorrect. WXR-related crash during resumption of previously interrupted flight. "FMS LFE" should be automatic upon FPL entry on the ground. Pushing Go-Around should put the HSI back into GPS mode. Replaced aural_warn_test and gear_warn recordings with cleaner samples. Implemented OVERSPEED aural message. Force the avionics_on dataref to 1. When we had the A/P override set, unset it if the CDI mode changes. SYN VIS north horizon heading should be 360 and sub-100 headings shouldn't have a leading '0'. SYN VIS airport loading could fail sporadically, resulting in missing runways. SYN VIS old method of computing airport label placement was broken. AIRAC cycle 1904 was mislabeled as 1304. Make sure GL_BLEND is enabled, because in X-Plane windowing context it sometimes isn't. Bezel drawing didn't work in popped-out windows due to X-Plane swapping in a different OpenGL context. X-Plane 11.32r2 seems to have broken our Vertex Array Object processing, so we have to work around that. 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.

We will absolutely be working to fix this, but it's not so trivial. HTTPS will take some work that's a bit more than just updating a link. I don't know when we'll finally have it done, but it certainly won't be abandoned.

The installer only grabs the very latest. All old versions are removed/deleted from the server, and the installer would stall if the wrong version were attempted. You have the latest.

The best course of action is to lower your expectations and it'll come when it comes. Neither Jan or anyone else is going to provide estimations of anything, even if a fully dedicated team is behind it working 24/7. As developers that's not a smart course of action. The reality is very simple (as much as customers hate to read it): when there is news it'll be posted. If there's no news posted, there's nothing we feel desirable to share at this time. Asking and hounding away on it will also not increase the chances of new information coming about, but it will certainty guarantee time away from the developer to tell you no news at this time and get into a few back and forth debates. And so, here is where this thread ends with as much respect as I can convey. If I leave this open it'll be more back and forth that ends up nowhere. This topic is now closed for the time being so people read this post as the last information available.

I don't understand your point here. If we charge for an update people will get a significant discount on 2.0, so combined with the 40% discount now it's pretty much a win-win. We have no idea when a 2.0 will even come. It's a concept and not even something in testing right now. No one is about to get screwed here.

When info is to be shared it will be.

Haha. "Basic." Some people never cease to amaze me with their inner keyboard warrior.

You're on it.

Move it to somewhere like desktop.

Just like Ben said it would in his last post. You should listen to people if you're going to ask them for support.

If it takes longer to experience a crash then it's not the same crash. Plenty of people flying it now without issue. We'll take a look.

The objective for this update was to get people flying again after crash to desktops. We do not have consistent TerraMaxx issues as we did before to diagnose this like we did before (and solved on test machines). That may change in the future as we gain more data. Anyways, that aside, this update had one purpose and only one purpose.

You need HDR enabled in your X-Plane rendering settings.

1.1.4c was an unscheduled plugin update. No other fixes besides crash to desktop issues were included, so what you're seeing is expected.

Yes. "Workaround for 11.31 crash when FMS returns bad airport reference from flight plan" is one in the same.

Hello All, This will serve as a formal forum announcement that we have released the version 1.1.4c update for the TBM 900. All customers who have purchased the TBM 900 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 TBM 900 from today forward, your purchased download will already be updated to version 1.1.4c 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 TBM 900 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: Workaround for 11.31 crash when FMS returns bad airport reference from flight plan. Added multi-sample anti-aliasing to synthetic vision. 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.

This looks to be Bitdefender or a similar anti virus blocking activation.

No. RWC is and will only be for use with SkyMaxx Pro.

Serial number for what?

No need. There's only one, and only for some people (TBM and TM). Still sourcing the cause.