Goran_M

This is where I found Marginal Ground Traffic. Can you post your log from the crash at SCIP

I'm almost 100% positive your crash is happening because of Marginal Ground Traffic which is part of several sceneries in your installation. It's a very old plugin that is very iffy when it comes to working properly. Especially with add ons that have very complex systems. To verify, try loading the TBM at a different airport (SCIP is an airport many developers use for testing) and see if it still crashes. If it doesn't, I'm afraid you'll have to remove either just the plugin (Marginal Ground Traffic) or the scenery.

If you're reloading the aircraft, and it gets damaged again once it's finished loading, it means the aircraft is being "dropped" onto the scenery you have installed. This is a sign of corrupted scenery or some other scenery error in the elevation. Try loading it at a different location in the airport you are at. More often than not, this is a good work-around.

Try reinstalling the TBM and see if that fixes anything.

Just had a look and asked Saso about it. Looks like this one isn't included in the commands list. We may look at adding it in the future.

I was just trying to find out if this was happening on my end, and couldn't see it. Glad you found the issue.

You should be able to assign it in your custom commands tab in the sim. The command for it is tbm900/controls/engine/emerg_power Assign an axis to that command, and it should work.

Ok, here are the important points we saw. 0:05:56.379 I/OVR: User is entering the holodeck. 0:05:56.379 I/WIN: Opened window Settings 0:06:03.025 I/JOY: T.A320 Pilot Axis 0 assigned to joy_use_ptch 0:06:05.753 I/JOY: T.A320 Pilot Axis 1 assigned to joy_use_roll 0:06:08.181 I/OVR: User is leaving the holodeck. 0:06:07.221 G64: core: Run: [OnBeforeXPSavePrefs] 0:06:25.981 I/OVR: User is entering the holodeck. 0:06:25.981 I/WIN: Opened window Settings 0:06:32.623 I/OVR: User is leaving the holodeck. 0:06:31.663 G64: core: Run: [OnBeforeXPSavePrefs] 0:08:19.175 I/OVR: User is entering the holodeck. 0:08:19.175 I/WIN: Opened window Settings 0:09:34.456 I/OVR: User is leaving the holodeck. 0:09:33.492 G64: core: Run: [OnBeforeXPSavePrefs] 0:09:48.080 G64: warn: Undefined function: ProcessKeyPress RawKeys_OnKeyHold 0:12:11.519 I/OVR: User is entering the holodeck. 0:12:11.519 I/WIN: Opened window Settings 0:13:53.812 I/OVR: User is leaving the holodeck. 0:13:52.851 G64: core: Run: [OnBeforeXPSavePrefs] 0:14:23.765 I/OVR: User is entering the holodeck. You opened settings, closed the menus. Back into settings, back out. Back in, back out. Several times in a row, separated by multiple minutes. So far, so good. 0:04:20.439 I/WIN: Opened window menu bar 0:04:51.348 I/OVR: User is entering the holodeck. 0:04:51.348 I/WIN: Opened window Settings 0:05:03.063 I/JOY: Saitek Pro Flight Rudder Pedals Axis 0 assigned to joy_use_rbrk 0:05:07.734 I/JOY: Saitek Pro Flight Rudder Pedals Axis 1 assigned to joy_use_lbrk 0:05:18.474 I/JOY: Saitek Pro Flight Rudder Pedals Axis 2 assigned to joy_use_hdng 0:05:34.106 I/JOY: T.A320 Pilot Axis 2 assigned to joy_use_thro 0:05:43.018 I/JOY: T.A320 Pilot Axis 3 assigned to joy_use_none 0:05:48.188 I/OVR: User is leaving the holodeck. Assigning hardware. Here's what we gathered so far up to this point. 1) Loaded the TBM at ICAO code GCXO 2) Gizmo checked the license, it's valid, 9 days remaining until a new license renewal 3) Opened settings window 4) Assigned a set of Saitek Pro Flight Rudder Pedals to left toe brake, right toe brake, and rudder yaw axis 5) Assigned the T.A320 throttle to left throttle and the other axis to nothing 6) Exited the menus Still moving along smoothly. 7) Then reopened the settings and messed about a bit more with the throttle assignments 8) At some later point you tried to do an engine start on the TBM, which seemed to have worked (the ignition at least fired, it seems) 9) Then flew for nearly 4 hours 10) Exited the sim - At this point, this is the strange part. The sim just stopped, but didn't properly unload. So, everything up until this point is fine. It's the shutting down of X-Plane that appears to be somehow stalled. Is the above scenario what happened? If not, can you clarify?

We both had a good look at your last log, and it looks like X-Plane just stopped. In particular, these lines... 3:48:43.752 I/SIM: Exiting the sim without confirmation 3:48:43.752 I/SIM: Exiting the sim without confirmation 3:49:00.015 D/STM: Transitioning from state state_Normal to state_ShuttingDown 3:49:13.372 G64: core: Run: [OnBeforeXPSavePrefs] 3:49:24.142 G64: core: Run: [OnBeforeXPSavePrefs] So looking through everything, it looks like you flew for 4 hours, and then it seems you tried to exit the sim, but the sim froze. This is what we gathered. Can you confirm?

@Ratnow If you're referring to the check mark for the proxy server in the installation, unless you are using a proxy server, you can just leave that unchecked.

Are you using a 3rd party scenery? From what I can see, it looks as though X-Plane isn't even loading completely. And it looks like it's your scenery (GMMI), with the TBM causing this. If the TBM reads corrupt scenery, it will crash, because it's collecting information for the terrain radar. Corrupt scenery will still load for other aircraft, because few aircraft use a terrain radar. Try removing the scenery for the area, and just use default scenery. Test and see if it crashes again.

As soon as the CL650 is wrapped up, the TBM fix will be added. Including, we hope, a navdata file from navigraph. A lot of what is going to go into the next TBM update is being done in the 650, so it'll just be a matter of bringing the fixes over. We're on the tail end of working on the 650, however, no firm ETA. It is in beta testing at the moment.

ah, you have "the bug". This is happening to some people, and we are investigating. Have a look in the image you posted. On the PFD (the screen on the left). Take a look to the right of the altimeter (Next to the RANGE dial). There's your AoA. We're looking into this, and we think it's a GPU driver issue.

Looking through your log file again, there is unusual activity going on. First of all something about the gatekeeper license (our DRM) is showing up as "bad". This might be nothing, but it might be something. Is it possible that you can run X-Plane from your desktop instead of your OneDrive folder? Can you run a test with a new copy of X-Plane installed on your desktop. No scenery. No plugins. Download the installer from the X-Plane website, run it, then update it. Then install the TBM only. Then test and see what happens.

This is the same problem as I posted above. Either the TBM is not activated or Gizmo is not installed. Make sure you have activated the TBM when it is run for the first time, by entering your email and password for your X-Aviation account.

Can you remove the shaders you have installed and try again? I'm not sure if that is causing the problem, but I would like you to try re moving them and seeing if that has any effect.

Happy to see you have it resolved. This is a known issue with the name of the scenery being too long.

I'll take a look at this in the next day or 2. You have quite a lot of plugins.

Ok, wait for the computer to get back, then we'll proceed.

Ok, I'm going to have to ask you to make a separate install of X-Plane only. No scenery. Then install the TBM only. No other plugins, other than what comes with the TBM. This won't have any effect on your activation and DRM for the TBM. Load the TBM at SCIP with Metal DISABLED and in windowed mode. There will be a runway and water. Make a flight and see if it crashes. If it does crash, post your log. If it doesn't crash, go into your settings and enable Metal. Reload X-Plane in windowed mode. Test and see if it crashes. If it crashes, post your log. If it doesn't crash, go into your settings and set the sim to full screen. If it doesn't crash, the problem with the other installation of X-Plane is a plugin conflicting with the TBM. If it does crash after this final test, the problem lies in full screen mode, which has been reported to LR, and they have already, in turn, hammered AMD about the drivers. In any case, please post back any findings and we'll dig deeper.

It's important to have the "start with engines running" checkbox unchecked. But going by everything you've said, it just looks like the code isn't getting installed. We've had this happen in the first few months after release, but not this late. Can you confirm if the crash bar (the black and yellow bar on the overhead) actually moves. If it does move up, does it stay up or come straight back down.

Can you try Windowed mode and see if the problem persists?

Are you running full screen or windowed mode?

Could you post your log.txt file (found in your root X-Plane folder). This tells us more about the crash. If you've started X-Plane again since the crash, you'll need to load the TBM again and have it CTD on you, so a new log file is written.

If you are, indeed, using an on board GPU, consider getting a separate graphics card. On board GPU's will cause all kinds of problems. @oldflyguy consider yourself an honorary support member.