Goran_M

You have SCEL scenery installed. Please check this post.

https://forums.x-pilot.com/forums/topic/20494-tbm-900-v1113-update-released/?page=4&tab=comments#comment-166835

Crashing during load tells me something else. After looking through your log for the scenery, it is indeed another problem. Please check here. https://forums.x-pilot.com/forums/topic/20494-tbm-900-v1113-update-released/?page=4&tab=comments#comment-166835

Do you have the SCEL scenery installed?

The reason I asked is the TBM and X-Plane (in many cases) have problems running full screen with an AMD GPU. This happens on both Windows or Mac versions. I run a Mac, and it has happened to me in full screen mode. This is a known issue, and Laminar have been all over AMD to get them to fix it. It doesn't happen to all add ons, but due to the TBM's heavy use of OpenGL and Cairo, the problem does present itself. A workaround, that may work is to have a window open behind X-Plane (while in full screen mode). This can be a browser or a Windows Explorer window. The better option that most/all people have had success with is running the sim in Windowed mode. It's not an ideal solution, but as soon as AMD fix this issue, the better it is for all of us.

Are you running the sim in windowed mode or full screen mode?

Remove the Jardesign ground handling plugin and retry. We've had problems with this plugin. Please report back results.

Sorry for the late reply. https://discord.gg/Snt5A3J9 Expires in 24 hours Let me know if you didnt get it in time.

From memory, it's "Prop Pitch ALL"

For the RAM? iMac's have a RAM door on the back. Only the RAM is modular.

If you're on an iMac, I'd suggest the 10 core CPU, 16GB GPU iMac still being sold at the Apple store. Forget about ordering the RAM through Apple. It's a rip off. Get the stock 8 or 16GB that comes with it, then order aftermarket RAM. You can get 2 OWC 64GB sticks for about $500AUD from Amazon, and then add the RAM that came with your iMac for a little bit extra. Also, Don't go for a high capacity built in SSD. Get the 1TB and then order an aftermarket 2 or 4TB NVME drive with enclosure and plug it into your thunderbolt port. I do this and X-Plane runs flawlessly. Whether or not you want to wait for the iMac's with the M1X chip is a decision you'll have to make. I wouldn't bother with the new M1 iMac's that are available now. I don't think they'll perform better than a current Intel iMac. If you're on a MacBook, consider getting an eGPU. Your CPU may bottleneck you, though. So you might have to weigh up the options.

Glad it worked. 20/20 hindsight, I should have known about the dataref, but it was early morning, and I was caffeine depleted when I made that post. Anyway, enjoy.

First of all, nice setup. The torque is determined by the values entered in the acf file, under the engine parameters within Planemaker. The warnings are coded around that. So there isn't really any dataref that could help. I'm not sure how home cockpit setups work with that kind of thing, but if you could somehow set it up to alert you when you reach the max torque limit in the acf file, that could probably help.

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.