Cameron

I'm not being defensive. I'm setting the record straight for something you said was incorrect. Your assessment of what should be removed is incorrect. State files are to be left intact for a reason. The whole simulation is based on the perpetual state of the aircraft. The installer does not uninstall these for reason, and it never will. This is not my baby. It is Saso and Goran's baby. No, it really does not. Any core files that were installed with the product and are pertinent to making any of the code the aircraft uses are entirely removed minus the state of aircraft files. That is not something I'm going to be able to assist you with. Goran and Saso will do so. Only advice I can provide to you is to remove all plugins minus Gizmo and see how you go. Since you seem to be unfamiliar, please do familiarize yourself with our refund policy. I'm sure Goran and Saso will do whatever they can to help you. FPS are not a guaranteed quantity, however. You already know my feelings on your GTX 970's.

The Uninstaller is NOT supposed to remove or touch the state folder by design. You are incorrect with that statement.

SLI configs like that can actually do more harm than good when it comes to X-Plane. It was never really optimized to take advantage of it and when SLI was the big thing it wasn't uncommon to see single cards beating out performance of dual cards. Trying to compare other aircraft to another really isn't a valid comparison. No two 3D models are alike, and the TBM obviously goes the extra mile in the programming department, which in turn is going to put more load on even the GPU. Given your description of when your fps hit starts, I'd say it's pretty clear what's likely going on.

I would venture to say that running the GTX 970 could be a big contributing bottleneck here. That's a pretty old card by today's standards when coupled with the demands of X-Plane 11. My guess would be some kind of fill rate happening on the card.

A discount was available for two months for all v3 owners when it released. There is no longer a discounted upgrade path from v3 to 4.

@BillM You're using an old installer.

It's towering cumulus and can only appear when FSGRW is instructing it to in the SkyMaxx Pro specific integration.

Because a single case does not solve this type of problem. We need a greater pool to leverage chasing down the rabbit hole and finding the common denominator. I'm glad DreamFoil was able to help you do whatever it was you needed help with remotely. That won't solve this problem, unfortunately.

No, we don't. That's pretty much useless in all honesty. As of now we don't have further answers to this. Thus far it was tested on multiple machines who had the issue and could concur that it did fix the problem. Until we get more people claiming the same as you that it has not we can't do much to diagnose.

Hello All, This will serve as a formal forum announcement that we have released the version 1.1.4 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.4 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: Added HUD circuit breaker. Deepened manipulators and fixed cabin pressure manipulator. Fuel indicator lines were misrendered and showing too low to the actual tank state. Fuel gauge lines should use a gradianted pattern, instead of a flat color. Added GPU exhaust particle effect. Added remap from X-Plane's TOGA_power to trigger our takeoff guidance and kill X-Plane's tendency to give full power as if we had A/THR. Added propeller tip vortices at high power and high humidity. Added FUEL SEL AUTO checklist item into the engine start checklist. Removed superflous AUX BP AUTO checklist item from the after start checklist. Implemented new airspeed and altitude tapes with better annunciator mode management. Implemented custom VS tape. Changed G1000 fuel units to gallons - should now show correct units in FPL fuel predictions. Fixed broken AP/TRIMS disconnect and AP off buttons in XP11.30. Switched to using tags for version IDs for more readable version strings. Use XPLMNavRef to avoid airports with inconsistent ICAOs in the X-Plane nav database confusing us. Implemented maximum climb torque and optimum cruise torque marks on the torque gauge. Squashed more marching ants. Added directly settable datarefs for all switches, so integration with external controllers and cockpits is simpler. Added direct set commands for all toggle controls to simplify integration for cockpit builders. Fixed broken alternate static port manipulator. Implemented DIMMER light switch on the overhead. Fixed missing approach pathways on ILS approaches. Adjusted rear seats so armrests are touching. Adjusted manipulators to reflect armrest changes. Fixed Nav/Strobe lights to be closer to the real thing. Chocks were sometimes misaligned. Added a vertical deflection dataref to align chocks to landing gear. EDM should be using the GASC-computed cabin altitude, not true cabin altitude. Bad fx_lin_multi field array could cause an assertion failure. Obstacle database was broken because FAA had switched to HTTPs and we weren't expecting that. XP11.30 reordered how the airport loading message is sent at start, leading to a double aircraft system init/deinit on aircraft reload via the Developer menu. Indicated airspeed computation was affected by pitot covers, yielding broken behavior for engine driftdown in windy conditions. Documented all custom switch datarefs + commands for cockpit builders. Can be found under Documentation/DataRefs+Commands.txt. Cockpit manipulator on MFD keypad for digit 0 has incorrect command assigned Fixed TerraMax license conflict causing TerraMax to sometimes deactivate momentarily. Fixed misaligned LOC with runway centerline. Added manual vertical realignment of GS transmitters with actual sim terrain elevation. 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.

Right, but temperature alone is not good enough to say "hey, there's snow here!" Even Florida can get below freezing a couple of days throughout the year on occasion, but it doesn't mean there's actual snow falling from the sky. I would say TerraMaxx likely saw the temperature, but dismissed the plausibility of snow because it's not a constant common in the region you were flying for the boundaries setup within the plugin.

I don't believe we advertise anywhere that weather is taken into account. It's a matter of best plausibility for the latitude and longitude you're in for a given time of year. Frank can respond further, but I want to clear that air.

I'll bet you it's not. I just taxied (in real life) and flew a Piper Saratoga the other day. I am mostly used to standard GA Cessna's and Arrows. The Saratoga was NOTHING like I was used to in my normal GA flying. Taxiing was much different and a surprising challenge because of how heavy an aircraft it is. The TBM is even heavier.

What do you mean how? We have a lot of customers at X-Aviation.

I bet it doesn't, and I've got over 100,000 Gizmo installations to make that bet with you on. X-Plane is a continuously updated app. For all we know it could be related to core code changes.

That's correct.

I'm assuming you're on windows. That would be OS settings from Microsoft on that folder. This is not an IXEG or even X-Plane issue, but a personal computer permission issue.

What gives is that you have improper permission settings on the folder it's supposed to be installed in. Make it writable.

I do not have it but it should work fine.

What happens if you make the day slightly later or earlier?

Then something is preventing any kind of license data from being written on your computer, and that's the problem. So, either permissions on the X-Plane and X-Aviation folder are not writable, or a firewall/anit-virus as I already stated. Either way, our server is issuing you a license, and your computer is for some reason not writing the file to disk because something isn't allowing it to.

Yes, it is. Something is happening on your end. What files do you see in you X-Plane/X-Aviation folder?

If I'm not mistaken there is an upgrade offer of 20 euros from the FSGRW website.

You have successful activation with the products on our server, so this indicates you either have permission issues in your X-Plane folder not being writable, or more likely some kind of an antivirus/firewall blocking the license from getting downloaded to your computer properly.

You will need to upgrade to the new version. Yes.