RobW05

That would explain it. The pressurization system begins to gradually depressurize the cabin at some point during the approach to match your LFE before landing. If that happens above 15000 ft you will get a cabin alt warning followed by the EDM. You can stop that by disconnecting and then reconnecting the autopilot. The warning messages will remain but you can continue your approach normally.

EDM is the emergency descend mode which is started automatically when the cabin altitude climbs above 10000 ft. That would happen in case of a cabin depressurization due to a pressurization failure or if you forgot to put bleed on or have the dump switch activated. I'm not sure about the "override" part, I think it could mean that you canceled the automatic emergency descent by pressing the AP/trims disc switch twice.

MrScott just recently provided one:

The last time you had the TBM running your system crashed, right? In that case, when you load it up next time you will get a window telling you that your last flight wasn't completed and it asks you if you want to continue where you left it or start a new one. Maybe, due to your 4 monitor setup this message is somehow hidden out of sight and it seems to you that it's frozen, while the TBM is just waiting for a "yes" or "no" input. Maybe you can temporarily switch to one screen and check if that's the case.

@WorthyQuill No need to feel sorry. It's a false positive on the Linux installer which is part of the downloaded zip file. Cameron explained that a few posts up.

You need to have an altitude set for at least one waypoint in your active flight plan and the VNAV profile set up. Then you can activate VNAV within 5 minutes before the calculated TOD. Don't forget to also set your preselected altitude.

This was posted a while back by Goran in the Hotstart discord cockpit builders section. (hope I'm allowed to re-post it here)

I don't own Traffic Global, but I am interested in it too. My best guess is it won't work, as in the Traffic Global FAQs they state that you need the "xplane TCAS hack" to get it working with third party plugins and aircraft. That means you have to configure up to 19 xplane AI planes in order to see traffic in the TBM and that is what seems to be the cause for many CTDs with the TBM. However, Traffic Global also provides Datarefs for the traffic, so theoretically Hotstart could also implement Traffic Global directly. Of course that would mean some effort on Hotstart side.

You can file bugs here: http://dev.x-plane.com/support/bugreport.html Be aware that a non-centered range ring might not be a bug per se. In the real G1000 the ring also includes wind information and I think that is also modelled in the xplane G1000. Definitively a bug it is when the ring is totally misplaced.

The "why" I don't know, but just to explain what I meant with "off": 1. It shows a false range. -> That is something Toto has been working on, so it's a TBM "bug" and will have to be fixed by Hotstart. 2. The ring sometimes does not center correctly. -> That seems to be a Laminar bug, but I have no idea if they are working on a fix. If you can reproduce it best would be to file a bug report with Laminar.

Can't help you, but the devs always need the full log.txt file as it contains important information for trouble shooting.

You could check the audio panel left of the PFD if you have muted the related chanel.

The TBM doesn't support xplane betas. That being said a lot of users had crashes with many third party aircraft in the current beta run. Just go back to the last stable release and you're fine.

I've just loaded up at GCTS runway 7 and confirm there's an issue. ITS localizer won't be picked up while the ISUR localizer (runway 25) is picked up just fine. Really strange, I've not come across such a problem before.

Almost correct, but you shouldn't consider airspeed as the determining factor. Depending on weight you choose a power setting between 46-50% torque and accept whatever airspeed that gives you. You can look that up in the POH under the cruise performance section. Look for the long range cruise tables.

Did you have that problem in the air during approach, or just on the ground? What the TBM900 does differently than the default G1000 is that it actually models radio beam propagation so the signal could simply be distorted since you are on the ground. What I noticed in your pictures is that you seem not to have picked up the ILS signal correctly in the TBM. (see the "ITS" identifier shown right next to the frequency in the NAV window in your second screenshot? That is missing in your TBM screenshot so it did not pick up the signal correctly) So my best guess is it may have to do with the radio beam propagation model and therefore be a cool feature or a bug coming from this.

Correct, the TBM's TCAS doesn't need AI planes set in xplane. But TCAS controlled must be checked.

I would recommend to install a fresh, second copy of xplane 11. Just add the TBM without any other plugins or additional stuff. Does it still crash?

Me again You are in display revisionary mode. Press the red button at the lower left corner of your PFD to get to normal mode.

Just to be sure, you have the power switch in BAT or GPU position, right? If so, then check the TBM maintenance menu and xplane failures as well in case you turned these on. Also check the circuit braker panel.

The manual seems to be misleading, in fact this switch seems to enable cabin lights to be turned on individually and will turn off at all once. It won't turn all lights on. This is what the POH says: The pilot can switch off the cabin floodlights and the baggage compartment dome light with the ”CABIN” switch.

That's the big question! There is not really a 'good' affordable yoke around(*), at least that's how it is now. Some may claim that even 1000 dollar is affordable when you get a very well produced product which serves you many years. (speaking about the Yoko the Yoke) But that's too much of a spend for me, at least for now. (*) But that might change. Theres a company called Honeycomb coming up with a yoke and a quadrant they claim to fill the gap between the low budget and expensive high quality yokes. It has 90° of travel on the roll axis and a bigger travel than Saitek also on pitch axis. That alone should be a great improvement. I'm still sceptical but I decided to jump the gun and pre-ordered one of these. It should come sometime in October and then I'll see.

I haven't found a really satisfying curve for the Saitek yoke and some time ago I gave up and got back to linear. Whatever i did to smoothen out the pitch response around center it created inconveniences elsewhere. The Saitek yoke, at least mine, has a too heavy centering force and is totally lacking fine control in that important range. What adds to that is the general heavily noisy output, I can watch the signal dancing around no matter how smooth I try to move it. So for me the solution is replacing that yoke and I plan to do that rather soon.

And you did extremely well so! I can enjoy a low level cruise above Orbx True Earth territory with Skymaxx Pro / FSGRW combo with graphic settings in the "upper middle class" and still get away with 25 to 35 fps.

Ahh, not too far away from mine, I actually have the i7-8700k / Z370 board. But I am sticking with a 1070 card. At the time I was getting it the 1080 Ti was just crazy expensive. Thanks!