RobW05

I had a lot of crashes with the TBM initially, that was shortly after it came out and surely has evolved since then, but I discovered that for example a combination of the TBM, Shortfinal EDDM and World Traffic 3 made my sim crash reliably. But it also happened with other aircraft occasionally, so I suspected World Traffic to be the root cause. I have gotten rid of World Traffic completely and nowadays using Traffic Global. I have not had much problems in the past 2 years, despite maybe a handful of crashes but really, that can happen with any aircraft. Most of the times it's a Windows issue, big Windows updates loading in the background are likely to cause this for example. I've learned to tame down my enthusiasm to constantly improve my sim with the next best addon and that stabilized my sim experience a lot. My priority is now to enjoy excellent aircraft models like the TBM or also the Torquesim SR22 with just a few additional add ons like Traffic Global, Avitab and Orthoscenery. And I couldn't be happier with the outcome. (ok, I have to admit I can't wait for the new weather in xplane 12 )

Hi, new user of your fantastic SR22 here. I was wondering if you could provide a custom command for the parking brake. I know the default "Toggle brakes max effort" works, but isn't that technically wrong? The parking brake handle in the SR22 just 'conserves' the brake pressure you are putting in with the toe brakes, so you always have to step on the toe brakes before you pull the brake handle. Otherwise you'll be up for a nasty surprise at startup. Now, when using the xplane "toggle brakes max effort" command it will provide brake pressure magically without stepping on the toe brakes first. Isn't that cheating? EDIT: I just found out there's a dataref I can manipulate to produce the result i was looking for - > afm/sr/f/misc/parking_brake That works for me, all is fine.

Is this while flying manually or with autopilot on? If manually: What happens when you engage autopilot in alt hold mode, does it still go up and down? And if with autopilot: Could it be that you still give input signals with your mouse which the autopilot has to fight against?

Yes, creating a new airframe will reset it.

The user guide describes it best: In the real aircraft, this knob permits adjusting the friction (resistence to movement) of the engine throttle. In the simulation of the aircraft, clicking the throttle friction knob locks the throttle in place, such that it won’t follow user throttle inputs anymore, provided that the physical throttle control isn’t moved too far. This enables use of lower quality throttles that are prone to having some “noise” in their outputs. When the physical throttle is deflected sufficiently far from the virtual throttle position, the virtual throttle will start slowly “dragging” to the new physical throttle position. This can be used for very fine throttle adjustments, even when very little precision is available from the physical throttle axis.

That might be the issue. You have to arm it within 5 minutes prior to TOD. It will be ignored in case you do it earlier. Other than than it's pretty much straight forward: - set your VNAV profile - set an altitude preselection lower than your current altitude (typically the altitude you have been cleared to descend to by ATC) - arm VNAV within 5 minutes prior to TOD (simply do it when you hear the "vertical track" callout)

No, the G1000 isn't suited for VNAV climb. You can climb in FLC or VS mode but have to manage altitude restrictions manually.

I guess you also checked the maintenance menu for any failures? And just to make sure, have you checked and turned off xplane default failures? If you're following the checklists closely I really can't think of anything else than a failure. Hmm wait, do you by chance have any script running or maybe a hardware binding which could prevent fuel to flow? It would be worth to try without any scripts and all hardware unplugged. If it's working then you know how to troubleshoot further.

Did you turn the fuel selector to either left or right tank?

It was moved to copilot side a few versions back. (for the reason that the real thing has it on copilot side )

It could easily be dependent on the direction you're taxiing. It's weird sometimes yes. I know a certain spot in the Orbx Courchevel scenery where I can park and shutdown just fine, but next time I start xplane I find my TBM on fire right after loading.

Very likely the problem lies in the scenery. I have experienced that myself everytime I taxied over a certain spot in an airport scenery. The problem was then fixed by the scenery author. However, try to choose another parking spot and avoid crossing the area you crashed before.

It works, yes, but you really shouldn't be greeted with this screen anytime you start the sim (unless you did exit the sim without proper shutdown of the airplane) and moreover you should be able to press yes or no without the sim crashing. Something's not right with your installation or maybe you have conflicting plugins. Try without any scripts and plugins or maybe even with a fresh copy of xplane.

You could try deleting the content of your x-plane 11\Output\TBM900\state folder. That should give you a clean state without triggering the flight recovery window next time you start. Be aware this also deletes your aircraft state and you will start with a new one.

What happpens when you press "no"?

If buttons are sufficient for you then you don't need FWL or Spadnext. Just assign a button to the mixture up command and another button to the mixture down command. Using these two buttons you will then be able to control the right side of the throttle from cutoff to flight idle and back.

You can achieve that with Spad.Next too, you just need to know which datarefs to look at. (same as with the script I guess )

As oldflyguy said there's the P-factor mostly noticeable at takeoff (low airspeed) which you need to counteract with rudder (I usually activate the yaw damper to counteract as soon as flaps are retracted). Keep in mind that the more you pull the yoke to rotate the more pronounced the rolling tendency will be right after takeoff. Better just put very little back pressure to smoothly rotate and you will have a much smoother takeoff with less pronounced yaw and rolling tendency. That being said, in the TBM you have also a very noticeable torque effect coming from the sheer amount of power from the engine. You will definitely have to counteract with the yoke or with aileron trim to keep wings level whenever handflying. It is most pronounced with a high power setting.

That's the correct step. No AI planes should be set. Also in case you are running a third party traffic plugin make sure it isn't set to control xplane AI.

I guess he was talking about the two red buttons at the bottom of the two audio panels, Pilot and Copilot side.

Although I haven't tried with the latest version, it always worked for me @clr100 Maybe you have some conflicting hardware binding or a script interfering?

The display changes from TAS to Mach automatically when you reach Mach 0.4 That's how it works also in the real G1000.

You may want to update your GPU driver as you are on a fairly old version. That may solve your problem. Edit: sorry, disregard. I somehow confused your log with another one. It's not your driver.

Page 89-90 of the G1000 manual is what you're looking for.

Hi Jumtri, just to share my own experience, I didn't have a single issue with it other than some crashes due to AI aircraft. This is in fact a problem which is still to be solved, but Hotstart keeps working on it as far as I know. Now, there was a time when I was new to xplane where I tried out a lot of stuff, installing and removing plugins and scenery constantly. I had a bunch of crashes and problems as a result until i figured out that I don't really need all that stuff. So today I enjoy flying over Orbx regions or even default scenery with just a few plugins installed and with a rock solid sim. I know that's not exactly helping with your problem, but I wanted to give some other opinion.