Goran_M

This is a common problem we're seeing with AMD GPU's and running X-Plane in full screen. This is not something we can fix with code, nor is it something Laminar can fix with X-Plane. This is something AMD needs to address. The workaround is to run X-Plane in Windowed mode (the better solution for now), or if you insist on running X-Plane in full screen mode, have a window open in the background. It can be an explorer window or your browser, but a window needs to be open while X-Plane is running in full screen mode. This works most of the time, but it has unpredictable results. Try either or both of these options, and post back results. Hopefully, this is something AMD addresses some time soon.

I'm guessing you are running X-Plane in full screen (not windowed) mode. Am I correct?

This is the command for the cockpit manipulator. It should work. tbm900/actuators/cb/light

I couldn't tell you the issue with your hardware. We have quite a few people using the TBM with the Logitech Extreme stick, and they have no problems. One of our testers has that exact hardware. The only thing I can suggest is that you make sure everything is calibrated correctly and all axis assigned.

I'll need the complete log.txt file immediately after X-Plane crashes.

Looking through the forums, I've already replied to you. less than 2 hours after your initial request for help. Unless something else comes up, I'll consider your issue solved.

I've sent Saso your log file. He's still investigating. For more direct contact, consider joining our discord.

Mojave is too old of an OS to run the TBM on. Please consider updating to, at least, Catalina.

After looking at the screenshot more closely, the time to TOD is 1 minute 18 seconds. Not 1 hour and 18 minutes. Apart from that, there really is nothing more we can do with the default G1000 code. We did what the SDK allowed.

You're running MacOS 14. This is very likely your problem. macOS: Version 10.14.6 (Build 18G7016) Please consider upgrading to, at least, Catalina.

This looks like a problem between Littlenavmap and X-Plane. In any case, post a log.txt file and I'll take a look. Make sure you post a log file from a crashed session.

Can you post the entire log.txt file

I was corresponding with him through DM, here on the forums, and he confirmed on a clean install, with no plugins, there were no crashes. Following this, I instructed him to add the plugins and scenery back, 1 at a time, until it crashes, then to post results to determine if it's something we can fix or the author of the offending add on needs to fix.

If the engines are running when you load it, it means the TBM is almost definitely not activated. The aircraft should be C+D.

Not something we've seen reported. If anyone else can jump in, we'll be happy to look into it.

This is not something we can duplicate on our end, so we're still investigating. Something to try would be to use OpenGL instead of Metal, just for testing purposes, because of the Vega GPU.

It's not something we can check, since neither of us have anything from RSG. Perhaps someone else can chime in and offer suggestions. Alternatively, I can send you an invite to our discord server where we have a hardware dedicated group. Perhaps someone in there could help you.

Just curious, if no switches work, how did you get it started and flying? If nothing works, but cursors change to what they're supposed to be, it means it's an activation issue.

I see 3 potential problems. AMD GPU. X-Plane has an issue working with AMD. Are you running in windowed mode? Corrupted scenery (Australia Pro 2.03). xswiftbus (Overriding the TCAS) Can you try a different area, and make sure you removeall 3rd party plugins, and then test again. Perhaps get in touch with the Australia Pro author and ask him to fix the scenery. Here's a section of the missing files for that scenery. (It could very easily be the cause of the crashes, due to the TBM trying to read scenery that isn't there or corrupted.) 0:31:42.856 I/DSF: Warning for missing scenery file: -14+139 0:31:42.909 I/DSF: Warning for missing scenery file: -12+139 0:31:42.962 I/DSF: Warning for missing scenery file: -13+139 0:31:39.832 G64: core: Run: [OnSceneryLoaded] 0:43:22.650 I/DSF: Warning for missing scenery file: -14+140 0:43:22.739 I/DSF: Warning for missing scenery file: -13+140 0:43:22.782 I/DSF: Warning for missing scenery file: -12+140 0:43:19.650 G64: core: Run: [OnSceneryLoaded] 0:55:09.182 W/SCN: Missing object objects/cars/dynamic/police_car_var1.obj from package Custom Scenery/AustraliaPro 2.03 (chrisk and cole)/roads/; replacing with blank 0:55:09.182 W/SCN: Missing object objects/cars/dynamic/police_car_var2.obj from package Custom Scenery/AustraliaPro 2.03 (chrisk and cole)/roads/; replacing with blank 0:55:09.182 W/SCN: Missing object objects/cars/dynamic/police_car_var3.obj from package Custom Scenery/AustraliaPro 2.03 (chrisk and cole)/roads/; replacing with blank 0:55:09.182 W/SCN: Missing object objects/cars/dynamic/BusXTran_D.obj from package Custom Scenery/AustraliaPro 2.03 (chrisk and cole)/roads/; replacing with blank 0:55:09.182 W/SCN: Missing object objects/cars/dynamic/police_car_var1.obj from package Custom Scenery/AustraliaPro 2.03 (chrisk and cole)/roads/; replacing with blank 0:55:09.182 W/SCN: Missing object objects/cars/dynamic/police_car_var2.obj from package Custom Scenery/AustraliaPro 2.03 (chrisk and cole)/roads/; replacing with blank 0:55:09.182 W/SCN: Missing object objects/cars/dynamic/police_car_var3.obj from package Custom Scenery/AustraliaPro 2.03 (chrisk and cole)/roads/; replacing with blank 0:55:09.182 W/SCN: Missing object objects/cars/dynamic/police_car_var4.obj from package Custom Scenery/AustraliaPro 2.03 (chrisk and cole)/roads/; replacing with blank 0:55:09.527 I/SCN: DSF load time: 638025 for file Global Scenery/X-Plane 11 Global Scenery/Earth nav data/-20+140/-12+141.dsf (5032 tris, 0 skipped for 0.0 m^2) 0:55:10.153 I/SCN: DSF load time: 1235996 for file Global Scenery/X-Plane 11 Global Scenery/Earth nav data/-20+140/-14+141.dsf (79868 tris, 0 skipped for 0.0 m^2) 0:55:13.840 I/SCN: DSF load time: 616077 for file Global Scenery/X-Plane 11 Global Scenery/Earth nav data/-20+140/-13+141.dsf (63635 tris, 0 skipped for 0.0 m^2)

That would be something for the RSG guys to look into or, perhaps someone in here, who has the equipment, could help you out.

If you're happy with that work-a-round, then by all means, continue with it. Try to avoid comparing the TBM with other add ons. A lot of stuff in the TBM, you won't find in other add ons. A perfect example of this is the ice and rain effects. When other drawing plugins are introduced, like reshade or shadex, unpredictable things may happen. However, as I mentioned, if it works, then by all means continue using it how you wish. Glad you got it working.

Any 3rd party plugins can be found in the X-Plane/Resources/plugins folder. If it gets a little confusing, or you're too nervous about removing files and folders, just install a separate, temporary copy of X-Plane, and install the TBM into that. No other plugins, aircraft or scenery. If it works there, then there is something awry with the original X-Plane install which would need further investigation.

I would like you to try 2 things. Disable Vulkan and run the sim in OpenGL mode. And also remove ShadeX. The other issue I see is that the log file is indicating you also have Reshade installed. If so, can you make sure all files associated with Shadex and reshade are removed (not disabled), and test again. Keep in mind, this is not a solution I'm proposing, but more of a process of elimination. Please post back results.

I've sent your log to Saso, and he'll investigate further. I'll get back to you.

That helps, but I also need the log.txt file. It's also found in your root folder. Something in your system is causing this, and I'm almost sure it's GPU in nature. It's actually the first time I've seen this issue since the TBM's release.