Goran_M

This is the X-Aviation Saab. I'm not sure where you got the one you posted, but it wasn't from X-Aviation.

Darran. That’s not our Saab.

https://discord.gg/8RbKgW

In your images, I can see you have some kind of "Map" utility running. Has that always been there?

Woah. You have something very strange going on there. Do you have some kind of avionics hardware?

Press the red button on the Audio Panel.

You could always go for this. https://www2.razer.com/au-en/gaming-systems/razer-core-x

The first problem is you are using an on board GPU. You are getting an error for the librain droplets (our custom rain effects) because the onboard GPU cannot process them. On board GPU's are not recommended to run any graphically intensive software, such as X-Plane, and certainly not any 3rd prty add ons. The drivers are not reliable, and they are only capable of the most basic graphics operations. So my first suggestion is that you get a standalone Nvidia or AMD graphics card with an absolute minimum of 4GB of VRAM. Regarding the towbar, I'm not sure why it's always visible. Once you are done with it, clicking on the towbar icon in the tool tray found on the lower left will get rid of it. If it doesn't, you may need to reinstall the TBM. Hope this helps.

I'm not really sure why it would be catching fire mid air, unless you're seriously over stressing the engine. The failures happen due to neglect. They are never random. If you could link a video, I would be happy to take a look.

Can you post your log.txt file (found in the root folder) after using the TBM.

1. Yes and yes. 2. Yes, but depending on how you treat it. For example: Overtorque the engine for too long, you will get an engine fire. with damaged components that you will need to repair on the ground via the maintenance manager.

We're trying to figure this out, and after further testing with Saso, I found the C172 (my small, default aircraft of choice) and the 747 (my large, default aircraft of choice), both have identical spikes and stuttering to the TBM. I'm not really certain why the default C172 is not giving you stuttering, but see my images below of each aircraft. Just an FYI, I'm aware of the locking at 30fps reason. But for me, I obviously don't place as much importance on it as you may. Different strokes for different folks, I guess. I'll leave this to Saso to continue to diagnose, because this seems like a sim issue to me. TBM Default C172 Default 747

If you have locked yourself out of 1 of your own TBM installations, you should have no problem with the TBM working in any of the other PC's. I don't have access to the activation server, so your only other option is to wait for X-Aviation to get back to you. Make sure you check your junk mail, also.

Your Machine ID would be blocked under one or more of the following circumstances. You tried to activate it on a new computer you own, but you locked yourself out of it by deactivating the wrong computer. You have shared your X-Aviation account details with another person. You have sent the installer or the TBM folder to another person who does not own a legal copy. You have uploaded the TBM to a piracy website.

Just out of curiosity, why are you limiting fps to 30??

I'm not prepared to go into a TBM vs (insert add on here) debate and which is better/more complex/etc... There is a lot going on under the hood of the TBM, and although I do see the spikes in your graph, you haven't mentioned the variation in fps. I just tested this myself, and the spikes in my graph represent a variance of no more than 2fps on an average of 40fps on X-Plane 11.41. This variation is more than acceptable for me. Why are the graphs smoother in the 172 and FF A320? I have no idea. I don't know how the A320 is coded, and it's likely I never will. I do know what the TBM has that the A320 doesn't, and this may have an effect on the fps. But again, I don't know. Of course, we COULD take some features out, and it would reduce the stuttering dramatically, but that would defeat the purpose of what we're trying to accomplish with the TBM.

Happy to see the problem seems to have been found. Enjoy the upcoming update.

The way around windowed mode taking away a lot of the immersion is to have another window open behind X-Plane. Then you should be able to fly full screen. This is just the way AMD drivers work, and it is completely out of our control.

Your log reflects what I suspected. You have a lot of scenery plugins running that, combined with the TBM's own systems, could be causing the stuttering. Custom scenery is very rarely flawless. Couple it with ground traffic, and the potential for problems multiplies exponentially. I realize you compared the TBM to the default C172, but that is a very polarizing comparison. You're comparing a default add on, that contains a small handful of LUA code to something with over 300 000 lines of C++ code. I'm not saying there will be absolutely no stutters. The more customization there is, the more the CPU needs to work. there really is no way around that with an add on as complex as the TBM. But steps have been taken to minimize any stuttering issues. A true test would be to test the TBM in a completely bare bones installation with no custom scenery (particularly with no scenery plugins).

As a first test, can you make sure AI traffic is turned off. Also, if you normally operate the sim in full screen mode, can you try in Windowed mode?

And if you're flying, you'll see the fuel leak out of the filler opening, as well as it being mathematically accurate using the bernoulli principle. So the slower you go, the slower the leak. And vice versa.

Go into your keyboard settings and try to assign an axis to "nosewheel steering" command. Make sure this is separate to the rudder axis. Post back if this works.

Does this happen at different airports or just EHAM?

Unfortunately, neither Saso or myself have access to a touchpad, but if the touchpad can use any kind of axis, I don't see why it wouldn't work. There really is nothing special with the way the TBM steers or uses the rudder.

You're welcome. Enjoy