Goran_M

Assuming you have current GPU drivers installed, including OpenGL drivers, the code for the icing does what X-Plane tells it to do. If X-Plane says "add ice to the wings", the ice will start forming. In your case, the conditions, for whatever reason, simply weren't there. I know it seems like ice SHOULD have formed, but this comes down to the sim. Post your log.txt file, just for curiosities sake so I can see what's happening.

That error only occurs when X-Plane is running or hasn't been properly shut down. http://forums.x-pilot.com/forums/topic/15014-ctd/?do=findComment&comment=142406

Yours is different. IN your case, try removing flywithlua and reload. If the crashes stop, go through flywithlua and make sure it isn't doing anything to the systems of the TBM.

When reinstalling, make sure X-Plane is not running.

You can safely ignore these errors.

Many thanks for digging into this, and for the kind comments. Hope you enjoy.

The only thing I can guess is that you don't have some kind of sound plugin installed, like OpenAL. But I'm stabbing in the dark.

The malformed data lines are nothing to be concerned about. We're still trying to nail down what is reinstalling the exception handler. X-Plane, for whatever reason, is not giving us a clue to what it is in the log file, so it comes down to a process of elimination. In the meantime, can you try turning off all AI and re-test. This is just to help us isolate what is causing the exception handler issue. In some cases it's AI.

That's one of the best ways to iron out problems. Once you have tested, add your plugins one at a time and test X-Plane each time. The main concern I have is the size of your log files. They are enormous, to the point of being "what the hell???"

Just saw this. A corrupt scenery file can easily conflict with the terrain radar in the TBM. Try removing the scenery and reload.

I've been involved in X-Plane for over 10 years. This is, easily, the longest log file I have ever seen. Just looking at the beginning of where the TBM is being loaded, there is a lot going wrong with the sounds. As a first step, can you try re-installing the TBM, and then removing all plugins, except Gizmo, and then try again. The VR/left eye bug was fixed for this latest version, and this is the first instance of a problem showing up in the latest update. So it it is definitely something on your end.

It looks like your graphics drivers crashed. Can you try reinstalling them and see if the problem continues.

If you have traffic turned on, can you turn it off and try again?

Please post log.txt

Actually, can you try loading a default aircraft, and then the TBM after that? Please post back with results.

Can you post your log.txt file as well as a screenshot of your render settings? That kind of jump in fps is not normal, and I suspect something else is going on.

Known issue and not common. It’s being worked on.

The TBM uses a lot of OpenGL which other add ons don’t use. You may find that add ons that use “Librain”, which was authored by Saso (who coded the TBM) may also have issues on your pc, as it uses the same extensive use of OpenGL as the TBM uses. The only things I can recommend are make sure your on board GPU drivers are up to date or install a dedicated graphics card.

It looks like you’re using an on board GPU. Do you have a stand-alone graphics card?

The co-owner of Foreflight, who owns a TBM 900, worked very closely with us throughout the development of this add on. To see his YouTube videos, just do a search for “Jason Miller TBM 900”. He has videos of the add on and his real world aircraft.

@skiselkov

Everything to do with maintenance is done via code. Saso has gone to great lengths to make sure all wear and tear in the engine is affected several factors. He's delved quite extensively into the intricacies of engine maintenance. Personally, I just let him work his magic. If you really want to know... @skiselkov , feel free to jump in.

You can, but I'd rather respond in the DC3 thread under the LES forums.

When you remove other plugins, and it's still crashing, we still need to see the new log file. The log file tells us everything about any crashes that occur.

Disabling plugins doesn’t stop them from loading. They need to be removed completely. I’m not 100% sure, but it looks like x-life is crashing. Try removing that first and see if it still crashes.