Goran_M

This is not a usual occurrence, and there is nothing that should be causing a random, spontaneous Master Caution. Try moving the contents of the Output/TBM900/state folder to a safe place (Desktop is the usual recommended place), then reload X-Plane and the TBM. It will rebuild the contents of the state folder, and hopefully get rid of the Caution.

In all honesty, it all depends on schedules. The mesh is, for the most part, done. Still some details to add, and then texturing needs to be done. It certainly CAN be done before the end of 2022, but definitely not earlier than the first half.

It's up to you. 12 flights without a crash is pretty good, in my opinion. Something must have been added or done to trigger this latest crash. However, please know that these crashes represent less than 1% of our customer base. In the vast majority of those cases, a crash is due to a plug in that doesn't play nice with the TBM (due to possibly having some kind of feature the TBM already has) or it is just poorly coded. Of course, we don't expect every plugin author to purchase a copy of the TBM, and we shouldn't be expected to purchase every single plugin that is available. The only thing we can offer is a series of steps to minimize or eliminate the problem. This is one of the reasons for the log.txt file. If you feel like looking into this again, feel free to make another post and we can investigate further.

Please attach the entire log.txt file.

You have quite a lot going on in the plugins folder. Have you integrated the GTN 750 and/or UFMC into the TBM? Also, disable or remove the skunkcraft updater.

Can you please include the entire log.txt file? We need to see everything.

Thanks for the comments. The FOV of the SVS is 53° laterally and 39.75° vertically. Don't concern yourself too much with trying to match it. Just find a comfortable FOV for yourself, and treat the SVS as a separate pair of eyes.

You'll need to contact X-Aviation support. Activations are handled on that end. All the developers do is create the product.

Normally, a large Windows update will change the OS so much, that it's seen as a different PC. You should be able to just create a new "Computer" in the activation. If not, or if you have any issues with this, please contact X-Aviation support at support@x-aviation.com Or go here.

Thinking about it, it's do-able. And isn't too difficult. We might look at something in a future update.

It's incredibly unlikely the scenery is causing this (Unless the scenery has plugins...which...some do). This is almost definitely down to your hardware and/or plugins. Just start adding plugins and re-testing as you add. Eventually, you will find the culprit.

The instruments pop out when you click in a specific location. If you go into the View menu, you will see a "Show clickable regions" option. Enable this to show where the click spots are, then just try to avoid clicking in those areas when you turn off the clickspots again.

I've made Saso aware of this issue. In the meantime, I recommend installing a separate clean copy of X-Plane with no scenery. Install the TBM. Disconnect all hardware, except the mouse and keyboard, prior to loading the TBM. Post back results.

The files that get created go into the X-Plane/Output/TBM900/state folder

It all comes down to what people want. Personally, I don't know why they want to make a DC3 with 2 other payware versions (ours included) and also a freeware version already out there. But anyway...

If you've followed the checklist correctly, and made sure procedures are followed, the only 2 reasons there would be no pressure is if the entry doors are not closed and locked, or you have a broken pressure vessel. Seeing as you have created new airframes, it may be the scenery you're loading at. If the aircraft "drops" onto scenery, it will break the pressure vessel. This is due to mismatched scenery tiles and elevation. Try loading at a different location at the airport.

@StefanH75 "Very soon" is a very loose term used in development circles. In saying that, a lot more is going into it than we originally planned. Which we think is good for everyone.

If it needs updating, we will definitely update it. And very likely, it'll be a free update.

Unfortunately, we don't officially support the integration of any 3rd party mods to the Saab. This is something that you would have to get help from RSG for, or someone else who may have had better luck with the integration.

I see quite a few plugins that have me questioning whether or not one or some of them may have something to do with this. Please temporarily remove the following plugins (move them to your desktop or any other safe place so you can restore them later) and then shut down and restart X-Plane. Load the TBM at SCIP and re-test to see what happens. XPrealWX 124thATC Autogate AOS Terrain Radar Therm-X stkpconnector If it does the same thing, please send another series of logs. Plugins and enhancements can make the sim better, but sometimes too many plugins can cause conflicts with aircraft add ons that have plugins already added.

If the problem persist, please post a log.txt file as well as a TBM900_log.txt If it is needed, we will indeed update it.

It could very easily be ortho scenery also causing problem. At least now you completed a full flight without issue, so that narrows it down, somewhat.

This could be anything from a de-activated aircraft, external avionics hardware to an issue with the avionics in the TBM that needs to be addressed in the maintenance manager. Fixing it by reloading the plane in the developers section is a little unusual. I'll pass this on to Saso and see what he makes of it.

There's no reason to be hesitant about asking for help. You're our customer, and we will help as much as we can. Unfortunately, there are other developers who make other add ons, and sometimes, those other add ons, and the TBM (Not just the TBM, but any aircraft add on) will conflict. This happened with the Saab and XEnviro. We received many complaints from people telling us to fix the Saab and make it run well with XENviro. Even when we went through everything, and determined that the fault lies with XEnviro, people still demanded we fix the Saab. Eventually, I was able to get a hold of Sergey (XEnviro developer), and after asking him to look into it, even he wasn't convinced. I pleaded with him just to check, so he gathered some users together who also owned the Saab and ran some tests. After less than a day of testing and debugging, he did indeed find a problem with XEnviro. An update was issued soon after, and the incompatibility was resolved. If the fault lies with the TBM, we will be more than happy to look into it and fix it. However, in many cases, the fault lies with other add ons. Whether it's buggy code or another feature that the TBM already has (An example would be the terrain radar). All we ask is that people provide log files and go through any steps we ask them to go through. Again, please don't be nervous/scared/hesitant about asking for help.

There are certainly some abnormal procedures that are in our Saab, but it's not something that is fully comprehensive. You can set some systems to fail through the X-Plane failures module. When we get around to the next major version of the Saab, we'll look more into getting more features implemented, including a fully customized failures module.