Goran_M

Why do you have ASXP and Skymaxx installed? I could be mistaken, but having 2 weather engines will almost definitely cause problems.

Ok! Good day to you, too!

You want me to not publicly try to claim that you did not provide the information that we asked, yet you publicly state the above comment? You were asked to provide a Log.txt after you reported your problem. We did not ask for any other files. After looking at that 1 file, I saw no indication that the sim crashed. As I said, it even states the TBM had a clean exit, followed by the sim shutting down with no issue. I don't know what else you would like me to do after seeing that. You're claiming one thing. The log is telling me something totally opposite. The log file records exactly what is going on. So, as I said earlier, there is something happening that is unique to your system, causing a clean shut down, but resulting in a crash. Something I haven't seen in the 11 years I've been doing this. Of course there are more avenues we could explore, but you decided to quit after my last suggestion to you. Plugins are not without flaws. Could the TBM be causing you problems? Going by your logs, unlikely, but a slight possibility. Could it be another plugin? Highly likely. Could it be scenery? Highly likely. Could it be your internal hardware? Definitely likely. Others came in and offered to help, suspecting your scenery was the cause of the problem. You're accusing the TBM of randomly crashing in some cases, but not in others, while at the same time, dismissing the scenery or any other plugins as being the possible cause. The TBM is not coded with some uber code that spontaneously crashes your sim. Going by what you have provided, the chances of finding out what is going on is near impossible. We can only do so much from our end, short of actually sitting at your terminal and finding out what is going on. In saying all this, despite your decision to, for some reason, publicly announce your intention to switch to FS2020 in a thread that has nothing to do with that, and then trying to discredit a product I was involved in, I am still willing to help you find out what the problem is. But all I can do is make suggestions to try to eliminate all possible issues until your sim stops crashing. Short of that, the choice is yours.

SCIP is the preferred airport for testing among developers. Very little scenery, faster loading time and it's so small that the chance of any corrupted scenery is low to non existent.

So, after checking your post history, of which all of them are in this thread, I have not seen a single log file from you that shows a crash. The only log you posted shows a clean exit from the TBM and a clean shut down of the sim. So either the crashes you are experiencing are absolutely unique to your system, where the log shows no crash, but the sim crashes anyway, or something else is going on. But I'm not one to speculate without evidence. Either way, we can't help you if you can't provide what we need for us to help you. I'll consider your issue closed until you provide what we ask for.

De-activating plugins will not solve the problem. You need to remove them completely. If you keep them in the plugins folder, they still get loaded. Enjoy FS2020.

The very first concern I have is your GPU drivers are very out of date. This could, very well, be causing the crashes. I see in your log file in here that you've updated them, so try loading it again and see if the crashes persist. Failing that, try loading the TBM at SCIP, and doing a few circuits. If it doesn't crash, I would put it down to the 3rd party scenery causing the crash. If it still crashes, post back with another log file.

The wear and tear we've implemented involves the day to day running of a TBM. The X-Plane failures module is there should you wish to set things like, for example, the engine to fail at a particular time, so you can practise engine out procedures.

You'll need to reproduce the problem you were having that caused the crash. It seems you reloaded X-Plane since then and in doing so, you've overwritten the previous log file. The Log.txt is what gives us the details of the crash.

You can certainly set your own failures in X-Plane if you want to practise procedures.

Where is the log file? There is nothing attached in your post.

So far, the answers to your questions can be found in the Quickstart guide.

Just a quick FYI, there is a documentation folder with manuals that will answer all your questions. It'll save you from posting in here and waiting for a response.

We have it working in the beta for the next update, but there are some issues in VR with it. Still being worked on.

Try this. Made by the same person who coded the TBM. https://github.com/skiselkov/StopZoomingDammit

An update is in the works, and there are many fixes that have gone into it, including the pathway in the sky. The biggest issue is getting librain to work in Vulkan/Metal. A beta build of the update has been in the hands of testers, and librain integration, while making progress, is still being worked on, due to some VR issues.

Check Aircraft/X-Aviation/TBM-900/Documentation

I'll need to see your entire log file.. I may know what is causing it, but what I'm looking for is earlier in the log.

Very vague, but usually when there's some kind of warning, it's accompanied by a flashing light on the Master Caution or Master Warning. Also, a CAS message should state the problem.

In your case, you have a lot going on in your plugins folder, and my thinking is there is something in there, combined with the TBM, causing the crash. This is a case of removing all 3rd party plugins, with the exception of Gizmo, and then reloading. If it runs normally without a crash, replace the plugins 1 at a time (shutting the sim down each time) and reloading the sim until the crash occurs. The TBM runs without crashing in vanilla X-Plane.

Have a look at cockpit_builder.cfg in the TBM folder. It explains how to get bezel-less pop-ups going.

Orlando You are blowing this out of proportion. And after answering the same comments about the same problem, numerous times, I'm going to tell you our position on this whole thing. We pride ourselves on the support we give our customers/clients. During the first week of release, we worked constantly to publish 1 update PER DAY for the first week, based on customer feedback. That's 7 updates in 1 week. No other developer in the history of gaming or flight simming has done this. In those cases, you would be lucky to get a first update after a few months. The following week, we published 1 update every 2nd or 3rd day, until the majority of the problems in the TBM were solved. We welcome anyone to post problems they are having with the TBM, or anything we make. We always have, and we have no issue with this at all. What we do have an issue with is people comparing an add on, such as the TBM, to another add on, and then stating "this doesn't happen with this other aircraft". This doesn't help us in any way, whatsoever. We don't have other add ons to do comparison testing, basically because we don't have time to test against every single add on in the community. Every add on is coded and created differently. When you tell me "Hopefully, you don't continue to justify this problem by using Xplane 11 and Vulkan / Metal version 11.50 b17", you are insinuating that I am lying to, not just you, but all our customers, by shifting the blame on to Laminar. We will never do this, unless we are absolutely 100% positive that the blame lies with Laminar, and I find it rather insulting that anyone would suggest that we lie about these things. If we have done something wrong to the TBM, (once we verify that it is our fault) we will whole heartedly apologize, admit our mistake, and work as quickly as possible to fix it. In the case of the ILS, I have posted several responses to several posts stating that something in the X-Plane ILS code was changed from within X-Plane in Beta 10. After contacting Laminar, this has been verified. If other add ons work, then that's because they did something that is not affected by that part of the sim. We utilized every bit of the sim that we could to create a highly detailed representation of the TBM. As I mentioned, in the case of the Torquesim developers, who I consider friends of mine, the SR22 was specifically made for 11.50 betaXX. So during development, they were aware of what was made available to them, and developed around that. I have no idea where you came up with this statement. Going through this very section of the forums, you will find countless responses by me helping people with their support questions by offering solutions or stating that fixes will be coming in past and future updates. I even included a link to a previous post about the ILS problem right here and here. And if you go back and read my last statement in this post, you'll see I posted a workaround, which verifies the problem lies with X-Plane 11.50. If you still choose to not believe what I'm telling you, feel free to email X-Plane support and verify the problem with them. In closing, after several replies to people reporting the exact same issue, both in private messages and these forums, I'm considering this matter answered in full and closed, with a statement informing people of a workaround, and an official word from me that the problem will be fixed in the next update, along with some other minor fixes and hopefully a fix for the rain and icing effects, along with the AoA indicator.

We're not "justifying" anything. We're giving you a legitimate reason. X-Plane 11.50 B10 broke the ILS. This is simply fact. Try the TBM in 11.41 or any beta builds prior to 11.50 B10, and the ILS will work perfectly. The SR22 was made for 11.50, and the X-Plane change in beta 10 was there while they were working on it. If you try flying the SR22 it in 11.41, you won't get very far. We have no reason to lie, and we never have lied about how something broke. It WILL be fixed, but it will be part of a larger update. A work-around is if you have navigraph data. Don't use the 11.50 format. Using the X-Plane 11 format will make the ILS work perfectly.

I understand, Igor. But I can only go by what the backtrace is telling me. And it's telling me the TBM is not the cause. The reason your other add ons are working is because no 2 add ons are coded the same, and something in X-Plane is causing it to crash. It could be the TBM, or it could be a combination of the TBM and your plugins. It could even be a plugin not liking something in the TBM, and as a result, X-Plane is crashing because of the conflict. In cases like this, where the backtrace lists X-Plane.exe crashing, the best thing to do is to send the log to Laminar. This may very well be a bug in X-Plane that the TBM found, and needs to be addressed. If it was the TBM that caused this, the backtrace would have at least 1 mention of the TBM.

Above is the backtrace from your log file, which is what tells us what caused the crash. I see no reference to the TBM causing the crash. This is X-Plane crashing from something within the sim. Not the TBM. This is something for Laminar to look into. I'll need the log.txt. Not the TBM900_Log.txt