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.