Goran_M

Do you have anything assigned in some weird way to fuel cutoff in any kind of scripting add on or through the hardware set up screen. It's a little tricky to figure this out, because you are, literally, the only person experiencing this. This leads me to believe it's something connected to your hardware or your set up.

Can you post a screenshot of your Windows sound settings? Specifically, the window that tells us where the sound is coming from (hardware)

I've brought this to toto's attention. Have you had a good look at all areas of the maintenance manager. He said you may have a blocked fuel line. Please check all areas of the maintenance manager and make sure they all say "As New".

toto's trying to nail this one down. We've seen a few cases of this error.

1 more thing you can try before going to drastic measures. Check Circuit breakers, and make sure they're all in. If that doesn't work, exit X-Plane, remove all plug ins not tied to the TBM, then try again. Leave Gizmo in there as well.

Can you try going into Output/TBM900/state and delete the ".airframe" file there. Then reload. You'll lose your airframe, but it will likely fix the problem. This is down to how Windows timestamps its files.

Please post Log.txt

Just a couple of things. Can you post a screenshot of your sound settings? And also, do you get this problem with any other aircraft? Would prefer you to check any 3rd party add on. The TBM doesn't use anything special with regards to sound, so the problem is very odd.

Generator running? If it is visually on (indicated on the overhead and the MFD), can you check the maintenance manager to see if it's damaged?

Just a couple of points. 1. Can you please post your log.txt. 2. The TBM is not supported in any beta version of X-Plane. It's strictly a "Fly it in the beta at your own risk." But, again, post your log and we can take a look.

Many thanks for your comment. The TBM has proven more successful than we had expected, so that, coupled with how well we worked together, I'd say we'll be doing something again. For now, toto is busy making a few more minor fixes to the code, while I make some more cosmetic changes. Then we need to work on the next big update, which will have a few more extras, which will be followed by a long overdue vacation for me and my family. Then we'll see where things take us. One step at a time.

@skiselkov ^^

It's a known issue. Should be fixed for the next update. Apologies for the frustration.

You're welcome. It still bugs me that some people are experiencing this, so we'll look into it some more. But it's definitely not common.

I haven't seen this happening too often. I've been watching streamers have consistent fps as they stream flights lasting several hours. So I'm thinking this might be something else causing the fps drop.

Very happy to see people, like yourself, thoroughly enjoying it. And many thanks for the positive comments.

Your reflections are turned down to zero. Turn your glass reflections up.

Please, please please don't add other 3rd party plugins that can interfere with the navigation of the TBM and the G1000. We're using the default G1000 base model, but there is a lot of code running inside it, that is also linked to the autopilot. We haven't tested this in any way with the GTN650, and using the GTN can have unpredictable results, along with voiding all support. We can't help people if another developers product is trying to work with ours, and we haven't tested it. If you want us to diagnose it further, you will need to completely remove all traces of the GTN from the TBM, try the FMC again, and then, if it still doesn't work, send us a log.txt file. Keep in mind, the TBM is still not supported in 11.3. Only 11.26.

Did you check the maintenance manager to see if it's damaged?

The de-icing system, in some cases, won't "cure" your icing problem. It's more intended as a preventative. So if ice has already accumulated enough, it'll be very hard to get rid of. But, if you do have problems with altitude readouts, you could pull the alternate static handle, and that'll give you standby functionality. The handle for the alternate static system is directly under the right seat yoke.

Well, sure....the final line tells us, most of the time, the cause of the crash. I've seen that error before, but it could be a combination of things, or 1 thing. It's not a common error, and, from what I know, is tied to the TBM, but it could be coupled with X-Plane. That's where my coding skills (none) have to take a rest and leave the rest up to toto.

The white layers are ice build up. We saw it in early alpha's of 11.3. As the flight progresses, the ice sheds. But because the shaders have been changed in 11.3, it's having an effect on the ice toto added for 11.26. It'll be fixed, but not until 11.3 is out of beta.

You're braver than I am. I helped make the thing, and I choose to leave the deciphering to toto. There's an insane amount of code in the TBM, and unless you have the source code, making sense of the log, in most cases, would be an exercise in futility.

If you choose to run the TBM in 11.3, while it's still in beta, it's a "run at your own risk" situation. The TBM is not supported in x-plane beta. Things will change as the beta builds progress. If you want trouble free TBMing, revert back to 11.26.

11.3 is unsupported because it's a beta. When it's a release candidate, then things will start getting fixed.