Goran_M

Need the log.txt file from the X-Plane root folder.

Another idea. Check the maintenance manager to see you haven't got accelerated wear checked. Check all circuit breakers. (I'm just trying to cover all bases here) Make sure you follow the checklists in the G1000 to make sure everything that's supposed to be on, IS on and everything that's supposed to be off, IS off. To see it fly smoothly with no problems, and then suddenly things go haywire, tells me something is going on mid flight.

A bit of a drastic idea would be to delete your preferences and then restart X-Plane. Downside is you would have to recalibrate everything.

Please do. I'm racking my brain here trying to duplicate what's going on, and it's just not happening for me.

Question: Is your experimental flight model turned on?

You can actually set the reflection detail to low and the blinking should stop. So you can still use the AoA HUD. Experimental model is NOT recommended. So please don't use it as it might have unpredictable results. Particularly on takeoff. And thank you for the comments.

We found a bug that causes problems with the TBM and AMD drivers. A fix is in the works. Apologies for this. It'll be fixed as soon as possible.

Unfortunately, it IS something to do with AMD drivers. Sometimes, when bugs get fixed, we take 2 steps forward, but then take 1 step back. Saso is working on an update for the AMD users and should be out very soon. Many apologies for this, but it's not something we thought would happen.

I’ll forward your log to Saso and see what can be done. It’s very unusual, and the only thing I can think of is something with amd.

I know a number of our testers had Vatsim, XPUIPC, Ortho and HD Mesh. Especially the streamers. I don't think I've seen any testers with SAM or MoveVR. The problem is, the more plugins that are added, the bigger the chance is for a crash or some other kind of issue. Not ideal, but there's always that small percentage of people that get the problems. I can assure you, though...the number of people with these problems represent less than 3% of TBM users. But we do understand that ANYONE with problems needs to be helped if any problems arise. So far, in the last 5 months since the TBM was released, most of our time was dedicated to testing and fixing bugs as well as adding new features.

Don't uninstall. Leave your original copy. Install a clean copy somewhere else on your PC. No scenery and no plugins. Then try again. If it works, please post back.

The reason we ask people to remove plugins is to find out which one is causing the CTD. That's just the first step. Once we find out which plugin is the problem, Saso then tries to figure out a way to create a "workaround" to the problem, if he can, from the TBM side...so in the next update, the conflicts will hopefully stop. If he cannot find the problem in the TBM, then we ask the person with the problem to make contact with the developer of the plugin so THEY can take a look and see if they can find the problem. The same thing happened with the Saab. People were getting crashes when they ran the Saab with xEnviro, and they were absolutely sure it was the Saab that was at fault. Jim (Saab programmer) and Ben (Gizmo programmer) went through every single bit of code to see if they could find the problem. They never did, and determined it was indeed, xEnviro. Andrey at xEnviro denied there was any problems. I pleaded with him to check, and he reluctantly checked, expecting to find nothing. He added some debug code and asked a small group of people to test it. After testing, he found the problem was indeed with xEnviro and proceeded to implement an update. This update, however, from my understanding, won't be available until version 1.10. We certainly don't want anyone to permanently remove their plugins. It's just a way for us to determine what is causing the problem so we can go about fixing it. In saying all that, most of the issues people are experiencing are isolated to a very small group of people, but we still try to help as many people as we can.

There is a LOT going on in your plugins folder. I am particularly concerned about this line: Loaded: C:\Spiele/X-Plane 11/Resources/plugins/TerrainRadar/64/win.xpl (drgluck.plugins.terrain_radar). The G1000 in the TBM has it's own terrain radar, and the one you have installed could be conflicting with the one in the TBM. Can you remove it and try the TBM again?

I've forwarded this post to Saso.

Your crash is pointing to LiveTraffic crashing the sim while the TBM is running. Can you try removing LiveTraffic and trying it again?

Your graphics card drivers are very out of date. Current drivers are 419.35, and you're running 388.13. This TBM update takes advantage of new features in the current drivers. I agree, constant problems are a nuisance, but if your graphics card drivers are not up to date, that's not something we can help with, other than to advise you to update them. Just a small edit. Comparing the TBM to other add ons is not something someone can do easily. The TBM is, in my opinion, more advanced than most, if not all add ons in the community. It is pushing the X-Plane API to it's limits, and conflicts can arise with other plugins, corrupt ortho scenery tiles (by way of terrain radar), AI traffic, weather, old drivers, etc... Add ons are designed to run on a bare installation of X-Plane. If problems arise, we try to fix them, if we can, on our end. If we can't, we ask the devs of the conflicting add on to see if they can fix it on their end.

Sweet. Glad you have it finally sorted

Looks like XSB weather crashed the sim while it was doing a push.

The walk around is mainly for the VR guys.

Treated by Armorall in the factory. Thanks for the compliment. Hope you enjoy.

The light is just not being occluded by the mesh. I'll see what I can do about it for a future update

The 20 hours is "delivery hours"

The oxygen switch is for the oxygen masks. The whole cabin is pressurized. So if you're getting an oxygen warning, 1 of your doors definitely is NOT closed. The doors are a 2 step mechanism. Front door, you click the bottom edge of the door to bring it in, but then click the handle to lock. Same with the rear door. If you have done all this, and still not getting a pressurized cabin, then you have a ruptured pressure vessel, which, from memory, needs a new airframe. You can create a new airframe from the maintenance manager.

You need to assign that to "toggle reverse thrust". This will bring it back past the stop and you can go to taxi mode and reverse thrust mode.

We'll get you sorted out. It definitely looks like an isolated case. Perhaps in the morning, try a scandisk or error check and see if Windows has some corrupt files. There are posts about that in here where people were having problems, then after running the scandisk, everything worked. We'll try and pick it up tomorrow