Goran_M

Sorry for not seeing this one. Posts like this should usually be posted in the support section. This looks like your anti virus is interfering with the TBM. Can you try disabling it and try again.

Try removing Skuncrafts updater. Don't just disable it. You'll need to remove it completely. Then try loading the TBM again. Please post back with results.

This is definitely LiveTraffic conflicting with the TBM and it's TCAS. There is a workaround for this in this thread. Currently, we can't say for sure what is at fault (TBM or LiveTraffic), but I do know the TBM is simply reading AI traffic data.

If you increase power to takeoff power, with the brakes on, the nose will slightly tip up. This, as far as I know, is normal for the TBM

As Cameron mentioned, the G1000 will be looked at in a future update, but for now, unfortunately, there is no way to adjust the brightness as it uses the default G1000 as a foundation for what we added to it. And, as of the TBM's release date (Last October), there is no brightness adjustment for it. Just a sidenote, please don't take our comments as being "How dare you criticize us!". When I read that you were getting 55fps, and you wanted more, I have to admit, I had a headshaking moment, also. We wanted to really push the limits of detail and systems, while still getting acceptable performance on the average PC. I actually managed to cut half a million polys from the mesh during the first few weeks of release. Our benchmark was Saso's PC. I think he's running some ancient i5 CPU with a GTX 950 on a Linux OS, when most other users have something around the 1080ti level GPU and an i7 CPU. But he runs it with no scenery and very little to no plugins. With that, he can get 25+ fps on the ground. In any case, happy to see your tweaks are giving you what you want. Enjoy.

The TBM uses a custom terrain radar which, if it flies over some kind of corrupt scenery tile, COULD cause a crash. But if you're crashing over default scenery, then something else is wrong. I'm seeing the GTN 750 getting loaded. Are you running the GTN with the TBM?

Just to add, are you running XVision? It's been known to make the G1000 colors blow out all contrast and color. I won't get into a discussion on what add on is more complex, because I don't have any of the airliners you mentioned, but I'm going to echo Cameron's comments on that. Also, the TBM is the first add on to use synthetic vision. Have you cycled through the different pages on the MFD to see what else is there? Traffic, weather radar, terrain radar, etc...

Getting more and more certain on what is causing the crashes. Are you running any ortho or custom scenery in the areas where you are experiencing crashes?

Between the flight yesterday and the flight today, were they in different locations? The second log file looks to me like the sim wasn't even finished with loading.

I'll wait for your log file.

Please post your log.txt file from the root X-Plane folder after a crash.

Can you tell me exactly what happened this time, because this log file you posted doesn't show a crash at all. But it also doesn't show a clean shutdown. This is almost always a symptom of some kind of rogue plugin or conflict between 2 or more plugins.

Oh my God. Where have you been @MrScott. You are the answer to my support prayers!

You would have to contact X-aviation support for that question.

The resolution depends on the resolution of a file called "Panel.png". When we were in the middle of making the TBM, we were limited to a 2K texture on which we could draw the TBM displays. X-Plane is now able to use a 4K texture resolution (as of 11.30), which makes displays clearer. We will likely revisit this when Vulkan comes out.

@Jota Please, just be patient. I can understand your frustration, but as I mentioned, when you upgrade your hardware, you will get your products back. If you are ever confused about anything to do with your add ons, we're all always around to help. It's part of what we do. If not us, there is a whole community who, as I have seen in the past, are willing to help also. @oldflyguy If you have any confusion, you can always come back here or contact support, and we're more than happy to help. @RobW05 Glad to know it all makes sense...and thank you for the compliment!

Thanks @oldflyguy. Just a couple of things. When you first install an add on, you are asked for your account details (email and password). That is your first activation. So no need to worry about a 4th PC yet. You are allowed 3 of those. It's just a number we thought was acceptable to our customers (2 PC's and a laptop for travelling is an example). When a 4th PC is getting activated, this is when things go past what is allowed, so another PC must be de-activated permanently. This is for our own protection, and yours. An example is you sell your PC, unaware your X-Aviation products are still on that PC. If someone tries to run one of your add ons, on a PC they bought from you, then it's you who will be questioned. The way we have it set up now is great for you to de-activate your old PC, remotely, should you remember and think "Oh damn...I left my old copy of the TBM on the PC I sold." Then all you need to do is go into X-Plane, find the PC you want to de-activate, and go through the steps. Now you're safe. Re-authorizing a computer, after de-authorizing it could leave gaps open for people who want to share their add ons so their friends could test them to see if they like them. This goes against X-Aviations EULA. This is why the activation system makes it very clear the user needs to type FREEZE in upper case letters, and then asks for a final click to confirm they want to de-authorize. And, as always, if people are not sure what to do, they can contact support or ask us directly and we'll be happy to help out.

Jota, I took a lot of time out and tried to help you in Facebook. If you are going to make these kinds of posts, in gigantic text, with false accusations and lies, at least be a man about it and have the courtesy to admit that you blocked YOURSELF out of your own product, after at least 3 messages came up telling you it would be locked forever if you continued. I already told you that a hardware change or a large Windows update would likely give you the opportunity to activate a new machine. YOU are in control of YOUR OWN activations. Not X-Aviation. This is what people were screaming for when activations used to be handled by X-Aviation. For those of you curious about what Jota is ranting about, he de-activated his own products, after disregarding the messages that came up warning him that if he continues with the process, his products will be locked. For clarification, here is the video explaining how the activation system works. At 3:05 is where Jota went wrong.

It looks like we've narrowed this down to how it has something to do with the way it reads traffic on the TCAS. The TCAS only reads what's out there, so, in theory, this looks like it's an issue with LiveTraffic. We'll look into it on our end, but can you also report this to the LiveTraffic guys, also, and see what they come up with..if anything?

Regarding the windshield icing, you'll also notice, with our custom bird strike, the glass doesn't crack, either. This is due to an update that was added a few versions ago which caused some issues with the "drawing" on the windshield. No timeline yet, but we are aware of it.

This is not a remedy, but a test. Can you remove Livetraffic and try again?

Maybe when XP12 rolls around. The avionics is what will take a while. For now, both our plates are quite full.

Make sure you stay in virtual cockpit mode when pressing the one outside. It won't work if you switch to external view.

This looks like either your scenery is corrupted or the weather software. I've sent your log to Saso to take a look. Usually, the sim crashes could be attributed to a combination of add ons or the another add on could be conflicting with the TBM. Most of the time, it's the latter. Livetraffic is an example. The TBM is more than reliable, but every plugin you throw into the mix risks some kind of a crash. It's no ones fault. It's just the nature of the beast. We can all only try to fix the problems as they come up. Appreciate your patience.

Did you press the button on the outside, to the right of the door or button inside the cabin, also to the right of the door? You need to press this button and hold it to electrically close the door until it's down. Clicking the handle closes and locks it.