Goran_M

If your maintenance manager shows all green, then it's likely user error. There IS a bug in the standby generator, which has the symptoms you're describing, but you did mention it's your main gen. So this one is a bit of a mystery. Wait for Saso to respond, and we'll take it from there.

Completely remove them. Disabling them still loads them. Also, if it was working yesterday, unless something has changed in your installation between yesterday and today, then it definitely sounds like a maintenance issue/random failure brought on by wear and tear. (Sorry for the delays in replying. Trying to manage support and helping my daughter with her homework.)

Ok, last resort. Remove all plugins, except Gizmo, and reload. There is definitely something happening on your end, whether it's user error or a rogue script or plugin. Saso is afk at the moment, but in cases like this, the best course of action is to check a bare installation of the add on without plugins installed. Then add the plugins 1 at a time until the problem returns.

You have FlywithLUA installed. Check any scripts that may be interfering with the generators.

I've also sent Saso a PM about this, so he'll jump in here shortly to see what's going on. But still post the log file. It tells us almost everything.

Log.txt found in the root X-Plane folder. But only post it after running the TBM. It overwrites each time you load X-Plane or another aircraft.

Post your log file and I'll take a look what's going on.

Try 2 more things. Check circuit breakers, make sure they're all in. Failing that, try deleting the contents of your state folder (X-Plane 11/Output/state) and then reload and try again.

Did you try resetting it?

You need to be in MAP mode, then you rotate the FMS knob until you reach the weather radar screen.

You don't aim for a climb rate, you aim for a speed. Final climb speed is typically 160 - 180 KIAS until reaching, say M.400, after which you push SPD on the autopilot panel to switch the system into constant-Mach climb and just maintain M.400 until reaching your cruise altitude. (Yeah, what @Jakob Ludwig said. )

Can you post a screenshot of your weather radar with visible cloud? It does work, so I'm guessing you're just missing something somewhere.

Known issue that was discovered about a week ago. From memory, it only happens when the crash bar is up, but the battery is off. Will be fixed in the next update.

Please check all your calibrations and assignments. If this does not work, try a reinstall. I just tested, and it's working fine.

You'll need to make an exception to the Gizmo folder in X-Plane as well.

I see a potential problem. 16GB RAM, and you have a LOT of plugins installed. Plugins chew up a lot of RAM. Removing LiveTraffic just lightened the load on the RAM and that's why you didn't get a crash until much later in the flight, likely when you may have been approaching some dense scenery. Do you have a lot of orthoscenery installed? Are your settings dialled up very high? As a test, remove half your plugins, preferably ones that you don't use very often, and then try again. Just make sure you leave Gizmo in there.

Do you have any kind of script running that can apply the park brake without you knowing.?

Could you post your entire log after the crash? My guess is your settings are too high for either your RAM or VRAM. The TBM is very graphics heavy, with over 2 million polygons and around 40 different objects and textures. But it still runs on many systems as long as the settings are configured for the type of hardware you have.

The cockpit is closed and warming up. If you flew the TBM in a previous flight and left the battery switch on, you will definitely have a flat battery now. Go to the maintenance manager and either recharge the battery or replace it.

That's not so easily done. We're looking at the problem, and a fix is in the works, but we can't just contact another developer and tell them what the problem is if we're not experiencing the same thing. This is why we ask the people having problems to also send a log to the other developers to see if it's something on their end. Saso is certain it's the GPU or something the GPU is doing with the add ons you're mentioning. The combination of add ons and the low fps is a result of the GPU architecture going a little crazy when they're all running simultaneously. Even though it doesn't happen to other add ons in your case, it's not always the aircrafts fault. Wait for the update to get sent out to testers (there are quite a few fixes included), and we'll take it from there.

This might be a case where you need to delete the files in the state folder and reload the TBM. X-Plane 11/Output/TBM900/state

I'm at a bit of a loss on this one. I've run every kind of test I could on my machine, and cannot duplicate this behaviour. Luis, try what Ch. Cole suggested and post back. The only other thing I can think of as a solution is to delete the contents of your preferences folder, and re-assign everything, but that's a last resort.

Aready that long? Yes, after a period of a few "maybe's", it is still being worked on. I'll have a lot more to say about it, if nothing goes wrong with the schedule, some time next month.

Make sure doors are closed AND locked. Make sure cabin pressure is good. No leaks. Check circuit breakers for cabin heating.

You have a bunch of LUA scripts running with the Carenado Centurion. Can you send me a log file with just the sim and the TBM installed, and the TBM loaded?