TBM 850

Hello, I was having this problem and reached out to Just Flight support. I thought it might be helpful to share their reply here, as (as far as I can tell) I seem to have solved the problem by following some of their suggestions. In my support ticket I had let them know that my Community folder was completely empty, and that I was getting CTD with Windows showing CoherentGTJS.dll or CoherentGTCore.dll as the cause of the crash. Of their suggestions below, I only did two things. I cleared the shader cache (Google how to do it, there are a few more steps than they describe) and I uninstalled and reinstalled all of the Visual C++ redistributable libraries (available from Microsoft, google it). I have not been getting CTDs any more (so far, and granted it was hit and miss when it was happening). Here's their full reply: Crashes involving CoherentGTJS.dll or CoherentGTCore.dll are commonly reported in applications like Microsoft Flight Simulator (MSFS) and are typically related to UI rendering issues, as these DLLs are part of the Coherent GT UI middleware used for in-game interfaces. The common causes for this issues are: Memory corruption or heap allocation issues – These DLLs often crash due to corrupted memory pointers, especially when interacting with other mods or third-party content​. Outdated or incompatible GPU drivers – Many users report that updating or rolling back GPU drivers can resolve the issue​. Corrupted installation or cache – A fresh install of the game or clearing the shader cache sometimes helps. Outdated Visual C++ Redistributables or DirectX – Ensuring all runtime libraries are up to date is essential​. Here are some steps you can try: Update GPU Drivers: Use the latest stable version from NVIDIA/AMD. If the issue started after an update, try rolling back to a previous version. Update Windows and Runtime Libraries: Ensure Windows is fully updated. Reinstall the latest Visual C++ Redistributables and DirectX. Clear Shader Cache: For NVIDIA: Go to NVIDIA Control Panel → Manage 3D Settings → Shader Cache → Clear.

My preference would be dual 750xi's as I could put the chart on one and the map or flight plan on the other.

Any updates on the 2024 compatibility patch since SU2 was just released?

Thank you for the praise. I hope you thoroughly enjoy them! I'm glad you solved your problem easily. It's a fine balance for me as to which cockpit interactions will work with the hardware inputs. Too few and we run into problems like this, but the advanced cockpit builders want everything to be an L:Var. If I use the system of abstraction that Asobo designed to do this, however, you run into bizarre corner cases with very unexpected results. Happy flying, and let me know if there is ever anything else I can do for you!

I don't have this issue, i just downloaded the latest SU2 beta to date

Found it. Axes and Oh's does it. I have all my controls assigned with that. As soon as I connect AAO to the sim, it greys out the GeneralAvionics circuit, and I have to reactivate it with the avionics master. [image: 8018ad64-7118-4d12-858b-729d156c37a2.png] Without AAO, the circuit is off on startup and comes on with the radio master, as it should. Now I have to find out why AAO does this. Might be in the script for the TBM I use for StreamDeck. Tricky bitch... Thanks for your help :)

Hello, long time :) can we expect to correct this issue in next update ? Thanks!

Can we expect that next update will proper simulate using bleed high and decrease TRQ?

@Black-Square said in Air conditoning "allows the cabin to be cooled before the engine is running": I've already fixed it, as well. The fuel pump will also respond accordingly now by not cycling on and off when there is no fuel supply. Nice! @Black-Square said in Air conditoning "allows the cabin to be cooled before the engine is running": MSFS 2024 compatibility update Man, MSFS really dumped a load of work on you guys (3rd-party devs in general I mean) with the 2024 compatibility problems with 2020 planes. Before getting the TBM, the main plane I'd been flying for months is A2A's Comanche, and FS2024 messes with its ability to restore the saved cockpit state, so I figure it's probably done similar things to the TBM850.

The TBM 850 does not have the "novel" style of power lever used in the TBM 900 and later, so you should find it much easier. The power lever, prop lever, and condition lever are three separate axes. The power lever can be bound natively in the MSFS controls menu, which is what I believe most of my users do, including myself. If you have a more complicated hardware setup, you can always write scripts for any kind of behavior you're looking for. Let me know if you have any questions, and I am always happy to help.

I believe you still need to copy the TBM 930 from 2020.

After many repeated flights.. The 750 and the 530 did not display LPV. They displayed RNP (sorry - my bad) Tried the same approach with the Duke. The 750 displayed RNP, same result - no GS indicator Tried a different approach. This one displayed L/VNAV on both the Duke and the TBM Approach worked a treat. So if it says RNP in the approach, I know it's not going to work.

@Black-Square I didn't even know it had some wingflex! Hahah the more you know! I do admire that you work on everything now, nothing is left behind. Thank you for your dedicated work!

That is great news, thanks for working on it. Keep up the good work, your aircraft are amazing!