Goran_M

Minor fixes for people who were getting crashes in certain situations.

There's no need to get to the frustrated level. If it didn't work, post in here. I certainly wouldn't wait until I reached the end of my tether to make a post. And just to clarify, the number of people having these issues represent less than 1% of our customer base. With complex aircraft comes problems on SOME PC's. There are countless PC configurations, X-Plane installations with who knows what kinds of plug ins are installed, that can be the cause of any number of bugs. Bugs happen. No software is immune to them. Not even an iphone. The latest X-Plane update crushed fps in X-Plane, but a number of people blamed the TBM. They realized it was the sim when, at my suggestion, they tried another add on. We understand you and the problems you're having. In return, we ask you to understand us. We don't know how frustrated you are. We don't know what lengths you went to. It's not our intention to make you frustrated. And most problems can be sorted out with a few seconds of work from the end user. Just ask the question and give us any files we need. As @fireone said, I'm always here. Even if I'm on vacation, I'll respond to questions within 24 hours. Usually within 12 hours.

Need the log.txt in the root x plane folder

Let's try to calm down a minute, Bill. We're on your side. Do you have any leftover files or folders from the TBM in the Aircraft/X-Aviation folder? If so, delete them, then reinstall. As for the FPS, nothing was changed that could affect the performance to the extent you're experiencing. Only minor tweaks were done to get rid of previous bugs. Can you try adjusting your settings. 11.3 has quite a few graphical updates, including a new particle system, that can affect fps.

Yes. There are a few small issues with the Mac version, but it's all but finalized.

I wish I could take credit for the coding it took to get the charts in the G1000, but that's all toto. In saying that, I can't see your idea being implemented. It would probably require a whole new programming workflow for anything external to the sim.

The poor FPS is not the TBM. It’s the new X-Plane update. Turn your threaded optimisation on in your graphics card settings. Your FPS should return.

Can you please send Laminar this Log and tell them what you posted here. It's likely there is a bug in the G1000. There were more changes in XP from R2 to R3, including autopilot changes. But it's definitely looking more and more like a scenery glitch coupled to the G1000.

Most of the CTD's I've seen appear to be scenery based. And they happen because the G1000 is reading the terrain, and if the scenery file is faulty, it crashes. Sometimes it doesn't have to be faulty. Scenery can be spread across more than 1 partition, and again, it'll crash. I've also seen a LOT of airport scenery plug ins tied to the actual scenery, outside of the resources/plugins folder. The plug ins are in the actual scenery folder. These can also, very easily, cause CTD's. So far, on my end, I haven't been able to reproduce a single CTD. But then again, I have very few plug ins. We're still investigating. Unfortunately, there is no way to roll back to a previous version of the TBM.

Your GPU driver crashed. You might have run out of VRAM. But hard to say from this.

It's actually a black panel IRL. I can appreciate you want some customization, but we have to stay true to the real thing.

Are you trying to introduce fuel too early? The NG given for an engine start is a minimum of 15%. Feel free to introduce fuel at up to 20% NG. Bringing fuel in too early, if the conditions are right, can lead to an engine fire.

I'll load up a flight and try to duplicate, then I'll post back.

Do you have any ortho scenery? If so, is it spread across 2 partitions?

150 is still too high for the ITT. You need to be at <120

Didn't even see this post. Apologies. I suspected scenery was the cause of a lot of CTD's. Mainly because the G1000 terrain radar trying to read terrain from 2 different drives.

The pilots are gender neutral

I've forwarded a similar log to toto, and he'll be looking into it. When you have time, can you check if it happens at the same airport/scenery, or is it random. Just for now, can you retry at the same area and see if it crashes again?

Strange. I'll look into it

We didn't change anything with regards to scaling or the oxygen mask. I'm guessing this was done on Laminars side.

I'm seeing a common thing in both of your logs. You both have quite a lot of errors in your custom scenery folder. The TBM looks like it's trying to read the navaid data in particular areas, can't read it due to the errors, and then crashing with the resulting error. By all means, take a look for yourselves. To help you diagnose, can either or both of you tell me where the crash occurred, and I will try to duplicate.

If they are present, delete all files and folders associated with the TBM in the Aircraft/X-Aviation folder, and try again

You can confirm you have DEFINITELY gone back into your account and downloaded the NEW installer and run it? I know you've said you've downloaded it several times, but you need to make sure the installer filename has 1.1.4b in it. Also, make sure you extract it out of the zip file before running it.

Just a guess, but did you take off the static vent covers and pitot tube covers?

I had a look at your log file and found this. "WARNING: extension missing proc glSpecializeShader. This is a problem with your video driver." The ice is using shaders, and it's almost definite there is something wrong with your drivers or the GPU itself. This is something you need to investigate on your end, as no one else is having this problem. This is a new feature that toto added. Propeller vortices under the right atmospheric conditions.