Goran_M

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

This is the concerning part. This is what happened just prior to your crash. XLF file not exist: C:\Users\Ralph\Desktop\X-Plane 11\Resources\plugins\FM\Airports/KFCI.xlf DAT file not exist: C:\Users\Ralph\Desktop\X-Plane 11\Resources\plugins\FM\Airports/KFCI.dat OPEN scenery_packs.ini FILE OK DAT file not exist: FlyWithLua Info: Searching for Lua quarantined script files FlyWithLua Info: The folder /Resources/plugins/FlyWithLua/Scripts (Quarantine)/ does not exist or it is empty. G64: 196.632: Boot Count: 4 G64: 196.826: Run: OnKickStart.. Looks like some kind of plug in at 2 of your airport sceneries is missing some files, which led to your CTD.

You'll have to assign left and right rudder to 2 individual keys on your keyboard.

Can you post your log file?

Check your maintenance manager to see if there is any engine damage. My guess is exactly the same as yours. Calibrating the throttle with the engine off. And this WILL destroy parts of the engine, resulting in an overheat and engine fire.

Just saw the last few posts. Good to see you've sorted it out. Here's the discord link. https://discord.gg/295eqn

In future, could you please post in our support forum. We don't normally check in here too often. As for your problems with the TBM, try creating a new airframe. This should fix it.

Could you try with AI turned off? (We're still working with Laminar to try to figure out why the crashes are happening with AI)

Is it the same circumstances as this post?

Happy to see you solved the issue. Enjoy.

Ok, then you have now confirmed the problem is isolated to that 1 installation. It all comes down to a process of elimination now. There is something in your assignments on the non-beta that is interfering with the landing gear. You could try removing/deleting the files in your preferences folder, but you will have to re-assign everything.

Shut the sim down, disconnect all hardware, restart the sim and post back if it happens again. I'm suspecting it has something to do with your hardware.

The problem is a bug we have in this release. In short, it's happening when you switch from GPS to NAV1 if an ILS is tuned in and we don't have a CDI deflection yet (too far from the ILS centerline). You can work around it until the next update is out by delaying switching from GPS to ILS until you are flying the intercept leg to the ILS.

lol, let's not jump to any conclusions. There may be a chance, we just don't have anything planned. But anything is possible.

This is not implemented at this time.

https://discord.gg/rK9k6F