Goran_M

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

There's a lot going on in that crash. You have quite a few plugins, and at least 1 of which may be conflicting with the TBM. Can you remove your 3rd party terrain rdar and see if the crash happens again. The TBM has its own terrain radar.

Make sure you don't have anything else overriding the TBM's load manager. Including the default X-Plane load screen.

This is most definitely an issue you need to take up with the corresponding developers of those plugins. They'll need to add some kind of exception to the TBM.

In cases like this, the TBM900_log.txt is the file we need.

https://discord.gg/yUrUf5

Shouldn't do either of those things. Can you replicate the problems, and if so, please post a log.txt file afterwards.

Might have to contact X-Aviation support for this one.

Make sure Windows Defender is also not running.

Are you using an older installer? Make sure you download the current installer from your account.

The AOA indicator runs on OpenGL. 11.50 uses Vulkan, and the AO indicator is not yet compatible with Vulkan. As for the lighting, make sure you have HDR enabled in your Graphics settings in X-Plane.

Yes

I'm not sure what to tell you, then. The log that you posted should indicate that Gizmo is loaded and running. It does not. See for yourself. Open up the log.txt file you uploaded in your previous post and do a search for Gizmo. There is no trace of it. Do you perhaps have some kind of anti virus that is preventing Gizmo from running?

No, it's definitely personnel. Personal is when something is "personal" to you. Personnel, is authorized "persons".

I just looked through your log. There is no mention of Gizmo anywhere in there. Can you double check it's in your Resources/plugins folder?

The fact you're getting serious stuttering tells me you either have incompatible plugins installed on X-Plane Vulkan, or your hardware may need upgrading. Without a log file, we can't determine what the problem is. The TBM works fine on vanilla X-Plane.

https://discord.gg/WUe5qT

Happy to help.

You have a lot going on here. Can you try an airport with no plugins. A good test airport we like to use is SCIP. Try that airport and see if it crashes again. My guess is, looking from the log file and the crash, that the ground handling plugin is causing issues, so also remove that plugin from the plugins folder and see if that also fixes the problem. Post back results.

Windows updates, if big enough, will change the OS, causing Gizmo to "see" the OS as a new one.

Your log shows no indication of a crash and no indication of the TBM being loaded.