Gregg Seipp

I had X-Plane shut down on me. I was flying from KPIE to KTPA climbing through 24000 and I noticed I had AI popping up and disappearing all over my MFD and I didn't want to deal with it. I'd seen that on my first flight on the ground, airplanes just popping up on the ground and disappearing only to reappear a few seconds later. II'm not sure why it was doing that. It's only done that with the TBM so far...my first flight with 1.17. This is now my third flight. Anyway, I decided to load up WT3 since, why not? Maybe that AI stuff would stop. I loaded it up, it set up the flights and then, a few seconds later, X-Plane disappeared. *Sigh.* Checked the logs but there's no indication of a CTD or any problem at all. I've started WT3 mid-flight with other airplanes...never had an issue. I don't use terrain on the PFD and I haven't used rain effect unless it's on by default. So there's two issues: Why the AI popping in and out (X-Plane doesn't do this with other aircraft) Why the shutdown I've been flying X-plane for a few months now. Started with a clean machine. Never had a CTD or shutdown before today. *Sigh*

Aha.

Just adding to this thread since I caused a freeze. When I tried to use the keyboard to enter a minimum for an approach, it froze solid on me. Perhaps you're not supposed to use the keyboard for that but, just saying it caused mine to freeze.

I had something similar happen yesterday. I was putting the minimums for the approach in and tried to use the numeric keypad to enter '210'. The sim hung when I entered '2' and I had to kill it. When I went to restart the sim i reloaded my last flight, clicked 'Yes', the airplane was where I was when XPlane hung but then the engines just shut down. My physical throttle, both in the sim and my hardware, was set to flight idle. I shut everything in the airplane down and restarted without a problem.

On my second flight (where there wasn't any problem), the rudder trim stayed slightly left of center the whole cruise. No airplane (that I've heard of) would require full deflection of the rudder in straight and level flight. So, if it's happening to other folks then I would think it would be either something with the "Failure System" or a bug. I couldn't find any evidence that it was a failure.

I just bought the TBM yesterday (confirmed I have 1.1.7 running on X-Plane 11.30). Took my first flight today. Prior to departure, I added a bit of right rudder trim to counter p-factor. Uneventful departure and climbout, everything kept well within limits. Engaged autopilot around 3000' and made my way up. Up at cruise on autopilot, I noticed that the rudder trim was pegged to the left. I looked at the rudder on the tail and, yes, the tab is to the right (deflecting the rudder to the left). I tried the yoke control but that didn't move it. I then mapped keys and buttons to move the rudder trim...no joy. AP/Trims is on (tried cycling it off and on again). Autopilot is disengaged. All fuses are in. I can see the yoke button move when I click the buttons on my physical yoke as well as pressing the keys. I couldn't check the maintenance window because...well, I'm in flight. The departure was pretty simple...a slight left turn, engage nav, climb, level off, climb, another slight left turn, climb and level off. I gave up on the flight and reloaded back at my initial airport. I'm brand new to the airplane and I was all over the place when I was diagnosing it so it seemed like the smart thing to do. I checked the maintenance window when i was back on the ground and everything is green. Gregg EDIT: No mention of "rudder" or "trim" in the TBM900.log EDITEDIT: Well, I'm not sure what happened the first time. I decided to try the flight again and, this time, no rudder trim problem. No anything problem. The airplane performed flawlessly. It was great.

Yeah, X-Plane does too. The problem, to me, with all the shader control apps is that they create a near infinite number of combinations thereby increasing the odds of a video card crash. Like I said, when Vulcan comes the whole shader mechanism changes (and there may be a lot of video card crashes as that comes into play.) Probably years off yet.

Interesting. I don't use any shader program...don't see any point since they're all going to break when Vulcan comes along. Anyway, when I first got X-Plane it worked fine with a driver that, I think, was about 6 months old. I updated the driver back in December and X-Plane graphics got corrupted whenever it started. I reverted back and haven't changed since. I just got the TBM yesterday and it starts up fine. Haven't taken a flight but, so far, so good. I may try the latest driver at some point and I definitely will update if it causes a problem, but a lesson I learned a long time ago is that you don't update video drivers unless you have a reason. That is, don't upgrade just because there's a new driver. Gregg

I see a fair number of threads talking about how video drivers are involved in CTDs. What's happening there? Is it all the particle effects? Something else?

To be clear on that third point, as you fly along a route the G1000 automatically activates legs when you enter them. If it activates a leg that is part of the approach then the approach is activated the same as if you had activated it manually. BTW, here's a good video that shows how the real world G1000 auto-activates the next leg even if there is a discontinuity. Lots of good information in this video.

Actually, it should activate if any of the following occurs: If you activate the approach When you activate a leg which is part of an approach When you enter a leg of the approach but haven't yet activated it.

Good questions. I can't say it always automatically sequences automatically, though, I suspect that it does. The only real value I have with a G1000 is watching training videos of the real world system on YouTube which makes me far from an expert (though, I have many, many hours with the Flight1 G1000...but who's to say that one's correct?) The videos I have seen, where there is a discontinuity, the G1000 activates the next leg. The second. There is a fourth option: "Activate Leg" as well. There are a couple of reasons why automatic sequencing is important: If your only altitude restrictions are on the approach and there is a disconnect, you can't use VNAV unless you add a restriction manually on the STAR. It does not consider anything after the discontinuity. The workaround for this is to manually add a reasonable altitude restriction at the last fix of the STAR. If you modify your STAR to remove redundant fixes between the STAR and the approach the airplane flies into la la land. Here's a situation which illustrates both points at the same time (with another airplane). I was studying the G1000 VNAV by flying various STARs and approaches and decided to try the SUNST4 arrival into McCarran (KLAS) and the ILS 26L. The SUNST4 links to the ILS26L at PRINO. Here's the STAR and approach so you can get a sense of what I'm talking about. https://skyvector.com/files/tpp/1903/pdf/00662SUNST.PDF https://skyvector.com/files/tpp/1903/pdf/00662IL26L.PDF I loaded up the STAR and the approach into the flight plan which left PRINO and KLAS at the end of the STAR, followed by PRINO again as the first fix on the approach. So, I did the obvious thing...delete the PRINO and KLAS at the end of the STAR which, while it cleaned things up and looked right, was a very bad idea. From looking at the flight plan on the screen it looked perfect but there was that discontinuity in there. So this is what happened. First off, at CHIPZ the airplane stopped following VNAV down to the PRINO IAF altitude of 8000. It was holding at 11,000 feet and I didn't know why...the status indicators were confusing to me. While I'm trying to sort that out, it got to POKRR and just continued on straight. Not good. So I spun the heading dial, did a Direct To PRINO and descended manually. After I got on the ground and sat thinking about what happened, it occurred to me about the discontinuity. The G1000 was blind to the approach...it didn't know about the IAF altitude restriction at 8000 and had no connection to PRINO despite it looking that way on the Flight Plan page. I've pondered various workarounds. There is simply no way I can think of to get the STAR to link to the approach. You are going to have to do something manually somewhere in the process. The best thing I could come up with in this situation was to delete KLAS but LEAVE THAT REDUNDANT FIX (PRINO) IN THERE and, also, add the altitude restriction that's at the ILS IAF to the redundant fix. Finally, when you pass the last fix prior to the end of the STAR, Activate Approach (but be careful that VNAV doesn't stop when you do!). More generally, and I mean this seriously, just never trust the G1000 between the end of a STAR and the beginning of the approach...understand the discontinuity and have a plan. Gregg

I guess the answer is that it doesn't automatically sequence to the approach. I'm definitely looking forward to a release of the LR G1000 that will change that.

Thinking of getting the TBM but I do have one question. I know that the default behavior of the LR G1000 is, at the end of the STAR it does not automatically activate the leg from the end of the STAR to the approach...you have to do a Direct To, Activate the Approach or vector yourself manually. Does the TBM modification of the G1000 address that or do you still have to manually activate that the same way as with the LR version? Thanks, Gregg

Thank you!

Thanks! Very good to hear.

Hi, Thinking about buying this aircraft. It looks extremely well done. Can I ask if you have to use click-and-drag on the switches and knobs? I much prefer mousewheel for knobs and left click(up)/right click(down) for switches. Thanks for your time.