Goran_M

Understood. But it will help with diagnosing the problem.

Is this log from immediately after the crash? Because X-Plane is not recognizing this as a crash. But anyway, I see some potential issues. "Loaded: C:\Games/X-Plane 11/Resources/plugins/TerrainRadar/64/win.xpl (drgluck.plugins.terrain_radar)." This may potentially conflict with the terrain radar that has been added to the G1000 And this... "Loaded: C:\Games/X-Plane 11/Resources/plugins/xswiftbus/64/win.xpl (org.swift-project.xswiftbus)." I've heard this can cause problems. Try removing these 2 plugins first, and see if the crashes persist.

Nothing secretive going on. It's just that there isn't much to show yet.

Still a few things to do before we continue with the Citation. Saab update is being worked on for now.

There are no plans to add a ferry tank to this version. The real thing never had it. It IS possible, though. With careful planning and favourable winds, it can be done from France to the US. In an 850, no less.

What key bind are you using the engage beta and what is the command you are using? Can you post a screenshot of the key bind (keys and buttons section in the sim) that engages beta?

First guess is something in FlywithLUA is preventing your autopilot from engaging. Can you remove flywithlua for now, and then try again? Remember, in case you haven't done it, turn on AP Trims. Please post back if this works.

log.txt. Not TBM900_log.txt

Ok, we need to get a little more drastic now. Could you please go through your plugins folder and remove all plugins except Gizmo, and then try again. If no crash happens, replace each plugin, reloading the sim each time, to see which plugins causes the crash. Then we can decide where we can go from there. The TBM will run without issue on a bare installation of X-Plane, but some plugins can cause conflicts. I f we find out what is causing it, we can decide whether or not it's the TBM's fault, or another plugin.

Now it looks like Livetraffic is causing the crash. Quite a big one, too.

Please attach a log.txt file so I can take a look what's going on. Found in your root x-plane folder.

Is this a heading on a flight plan or a manually selected heading?

In the TBM menu, under plugins, there is an option to turn off warnings. Enjoy the challenge.

Not sure about the first one, but I'm guessing Saso coded some kind of EWS (early warning system) for the end user. In the realm of flight simming, there are very few of us who are actually type rated on a TBM 900, so we've added a few things to help prevent destroying the aircraft or the engine. No doubt, people who are type rated will have no problems knowing how the real aircraft works, and what could cause it to "break". For a $4 million aircraft, they'd better. Hot brakes can eventually boil brake fluid, and that causes the brakes to go spongy. Again, there are probably guidelines on how to tell if the brakes have overheated. Something like "Do not apply brake pressure for more than 5 seconds" or something to that effect, followed by "Do not operate aircraft for at least 15 minutes after overheating brakes." (I just modelled the thing, so I'm hazarding a few guesses. Systems are Saso's domain) I remember going for my PPL in a Beech C23, and even that was more study than I ever expected. I can only imagine what getting to know a TBM entails.

I think this is definitely one for the Laminar guys to look into. The Garmin is meant to be reading the frequencies from the apt.dat file, which we have no control over. Can you try contacting Laminar and asking them what could be a possible solution? Show them the same image you posted here, as well as the log file.

Can you try re-installing your GPU drivers. The backtrace is showing the drivers are causing X-Plane to go crazy, and then crashing. That's usually a sign of more than 2 monitors running, but in this case, it's unusual.

Running more than 2 monitors?

La razón por la que quiero que intentes eliminarlo es para que podamos confirmar que es la causa de flywithlua. Si es así, es cuando reinstala flywithlua y luego encuentra el script que está interfiriendo con su aviónica y mostrando las X rojas.

Can you eliminate flywithlua and see if this solves it? If you do, you should check it and make sure that nothing in flywithlua is doing anything with any avionics.

Archivo incorrecto. Necesito log.txt encontrado en la carpeta raíz del plano x

If you're getting single digits, then I would definitely try turning down the settings. That's when resources are being pushed to their limits. Try turning down reflection detail and Anti Aliasing first. See where that takes you.

¿Puede publicar su archivo de registro, que se encuentra en su raíz X-Plane?

When it displayed frequencies before, was it prior to the last X-Plane update? Does this happen at any other airport?

Why should we have to defend it in the first place? I actually find THAT unacceptable. The customer already disclosed, untruthfully, that he paid full price. Cameron corrected him. Cameron never brought up the topic of how much someone paid. If it's an untrue statement, it WILL be corrected. And I'm glad he did make the correction. I actually had a discussion with "Haskell" earlier, and everything is now straightened out. There is no bad blood whatsoever, and we just want to move on. Our final stance is...the update will be ready when it's ready. We don't announce ETA's, because if we miss that ETA by 1 day, it's "LES said the update will be out by yesterday and it's not out. They're unprofessional!" I promise you, it HAS happened to at least 2 products I have worked on. Lesson learned. We don't announce future projects, because if it takes longer than expected, the word "vaporware" or "abandoned" starts to circulate. As you can see a few posts above. If we decided to abandon it, we would tell everyone, almost immediately. Being slow, and making large changes to the product are 2 very different things.

We never intended to make the Saab compatible for XP11. It was made for XP10, and we were firm in that decision. Then people started asking for it to be made compatible (ie. make it work) in X-Plane 11. We did that. We warned people that there is a completely new engine model in X-Plane 11, but it WILL work with a few small issues. To be fair about it, we also dropped the price after the XP11 update came out. So it was a free update for existing customers, and a lower price for new customers. Even if they wanted to keep XP10. "I wonder if it takes that long because it's simply very old code with a lot of custom systems. Version 2.0 was supposed to make it a great contender again, but it's kind of an excuse now for 2 years to not do anything more significant on this plane." The above quote is exactly why we will never announce ETA's and very rarely publish updates. Too much speculation. Making aircraft for X-Plane, as complex as we want to make them, takes time. Carenado/Thranda have made it clear that they will charge you full price for a compatibility update for a new X-Plane version. How profitable is it? We wouldn't be working on a free update if we didn't think it was worth our time and effort.