Goran_M

Need the log.txt from the root X-Plane folder after the CTD

The problems were limited to the AMD 560. It's proving a bit of a chore to work the problem, but the 580 doesn't have any issues.

Unfortunately, there's nothing we can do to work around that. Call it an X-Plane shader limitation.

The 930's major difference is the Avionics suite. People have been asking for it, but there are no plans for an upgrade at the moment.

No crash is good news. Hope you enjoy, and thank you for the compliment.

This is the first I’ve heard of this. The TBM is separate from any other activation system from other vendors. It uses a completely different method. Could you have upgraded any hardware that could trigger an activation? CPU, graphics card, ram...?

Try adding your plugins one at a time, while testing each time until it crashes. That’ll help us determine what’s causing the crash and if it can be fixed on our end.

I think I see the problem. Windows 7. I know some people might not like upgrading, and we don't tell people to do so, but running the TBM on anything under Windows 10 could be unpredictable. Even though the system specs for X-Plane are Windows 7 or higher. I'll link Saso to this post, as he's the programmer who knows all about this stuff, and he'll give you a more comprehensive response with probably even a way to stop this from happening.

How much system RAM do you have? Also, can you post a log file?

Can you post a screenshot of your x plane render settings AND your Skymaxx settings. As I suspected, your VRAM is quite low, and the TBM coupled with Skymaxx might be causing the flickering. Although it's not recommended, you could also try scaling down the textures for the TBM. But only do this if you know your way around Photoshop. And ALWAYS make backups.

Well that’s interesting. Just sitting there? We’ll investigate this one further.

How much vram do you have? We think this is linked to either notebook GPUs or not enough vram.

You have a few plugins installed. Can you try removing them, except Gizmo, and try again.

Please try that. That’s not normal, and could indicate a deeper problem like corrupted windows or X-Plane files. Nothing serious, but serious enough to cause a freeze with the TBM code.

Sorry, just saw your 2nd last post. In any case, glad to see you got it working. (Been kinda hectic around here)

First thing I want you to try is removing webFMC. DO NOT disable it. You need to literally move it out of the plugins folder. Next, restart your PC. Restart the sim and post back what happens.

If you're still getting them, can you post a new log file so we can see what's happening.

Your right wing beacon light is broken. It shouldn't be crashing from this, but fix it in the maintenance manager and I'll pass your log on to Saso. After fixing it, you shouldn't be crashing anymore.

I always looked forward to reading documentation when I bought a new game or add on.

The 580 will run the TBM fine. It's the 560 that was causing problems. However, I think those problems are sorted out.

The way the TBM is working, is if a plugin is working WITH the TBM, the TBM will reveal a bug or bugs in that plugin by "exploiting" (for want of a better word) any holes it may have. There is a ton of customization in the TBM, that will even test X-Plane itself. In a perfect sim world, everything will work with everything and not cause a crash. I think I mentioned in an earlier post the dilemma we had with the Saab crashing when xEnviro was running. Well it turned out it wasn't the Saab crashing. It was xEnviro crashing due to something the Saab was doing with xEnviro. Naturally, because this was only happening with the Saab, everyone assumed it was the Saab's fault. No other add on was crashing with xEnviro. After some poking at the XE devs, Andrey reluctantly agreed to look into it and found it was definitely XE crashing due to a bug in his code that the Saab was exploiting. That's why we ask people to remove all plugins and then replace them one at a time, so we can see what plugin is doing it, then we can investigate further. Anyway, I'm rambling on. Bottom line, it's not always the aircraft crashing. Most of the time, it's something a plugin is doing with the aircraft and the aircraft is causing the plugin to crash. We'll nail all the issues eventually. But sometimes it's the other devs who need to make the fixes.

That's my fault. I changed the prop covers to align with the prop adjustment, and exported them, but didn't export the static covers. Problem is already fixed and we'll see what we can do to get the fix out to everyone.

Is WT3 a plug in that loads through the plugins folder of X-Plane? If it is, it doesnt matter if you have it turned on or not, it will load with the sim, since everything that is in the plugins folder loads when X-Plane loads. Disabling it doesn't prevent it from loading. If all the above is what is happening, it's likely this is the cause of your AI flickering on the MFD. I don't have this issue as I don't have WT3 installed. Regarding the CTD, other people have reported CTD's when running the TBM with WT3. The only thing I can think of is to mention it to the WT3 devs. Regarding the *sigh*...I said that every.single.time someone said they were getting CTD's on load up of the sim, only for me to reply to countless people to update their grossly outdated GPU drivers. It got so bad, I had to make a separate post on it. We're doing our best with the support, Greg. But the CTD's are not always the TBM's fault. Even though it may appear that way. The TBM will run flawlessly on a clean install of X-Plane. I know this because one of my X-Plane installs is bare X-Plane with default scenery, that is used as a test bed for early builds. The more plugins a user installs, the greater the risk of a crash. I apologize if it's frustrating for you, but like I said, we're doing our best to get these issues straightened out. Even though it's a small percentage of people getting them

Have you ever sent us a log file? A lot of the time, it’s a conflict with another plugin. We’d love to help you, but can’t if you don’t help us with more information.