Thrustmaster rudder pedal random fail

I actually have a habit of checking all my control surfaces before taking off in the Cessna 152. Yesterday, I noticed the rudder was responding erratically. For instance, it may not move right away or it will recenter while the pedal is pushed all the way to one side. It was happening to both sides. I verified the yoke twist was okay.

After a few minutes it seems to have cleared. I was able to take a long taxi and take off without any issues.

When I landed the airplane, I lost ability to control with the pedals and took a hard turn shortly after landing. It was bad enough I ran off the runway. It was a bummer as it was probably the best landing I’ve made to date.

Has anyone else had a similar issue? It’s the t.16000m full flight pack.

Yes I’m losing usb connection to my controllers. I have to go to the controllers to make sure they are recognized by FS

1 Like

It sounds like your yoke twist may be interfering.
Did you try with that twist disabled?

1 Like

Verify that the hardware works (or discover and observe hardware faults) with DIView
(Download from LeoBodnar)

Thrustmaster use cheap potentiometer’s in their devices which can fail and glitchy, spiking behaviour is the start of this.

3 Likes

That’s a good idea.

I had another problem where the throttle was spiking the trim setting that resulted is some violent crashes. That was fixed by unbinding the trim. The funny thing there is the trim control on the throttle wasn’t exactly working just on it’s own. It was very slow to unresponsive. But as soon as I throttled down it could make instant, large jumps in trim.

The majority of all my crashes so far have come down to ThrustMaster!

1 Like

Thanks, will give it a try. I tried running a ThrustMaster utility but it didn’t work.

Same Problem here. Thrustmaster Pendular Rudder Pedals working fine.

After Landing while taxiing 3 times pulled to the left. I had to push hard right to keep the plane on taxiway.After a short while it dissapeared and then came back twice. After MSFS shutdown no more problems.

I first thought that there could be some taxiway-assistant and a bad marked taxiway. But i am clueless. Will check on that issue later… but it seems that i am not the only one.

If it happens again, visually check the rudder on the airplane. For me it looked like it was strobing/vibrating erratically. It was even making weird sounds.

Something else it can cause is a delayed rudder response that suddenly jumps to an instant full turn.

So far I’ve been a little dissapointed in ThrustMaster. I’ve now had erratic and spontaneous trim along with rudder failure. Keeps you one your toes at least.

But it’s kind of cool I was practicing a pre flight inspection and caught it! Seems silly in a sim but we can have system failures just the same.

After a bit of testing it seems the ThrustMaster controls are spot on. The throttle in no way interferes with the trim as it does in the sim. The throttle’s default trim buttons also work. In the sim they either don’t respond or make large, sudden jumps.

DIView shows the rudder pedals are perfect.

The slightest issue I see is the yoke seems to pitch left 0.25% and forward 0.1% at rest.

Just to be clear. Not on all products. Do research before purchase. You get what you pay for generally.

Where does the t.16000m full flight pack fall? I figured it was basic and could pick it up fast.

It’s not the most inexpensive. But it looks like one can spend thousands on controllers and gauges. At some point I’d probably rather buy an airplane :smiley:

The best controller I ever had was the old Microsoft Force Feedback stick. That thing was simply amazing!! I haven’t seen anything like it in the years/decades since it was killed off.

I did 5 flights today and haven’t had the issue return.

Yes. TM X56 and Saitek rudder pedals both behaving either erratically or not working at all. I have to go into the menu and mess with things (it doesnt seem to matter what) a bit come back and then maybe it will work.

Edit - also trim issues too. It stops working and starts again. Same for other controls.

I guess based on the other reply that I replied to it’s with the pot’s they use. I was just pointing out that not all Thrustmaster products use pots. Hence why you have to do your research ahead of time.

There can of course be other causes. (duplicate bindings, AI control/assistance settings etc) but the first thing I check every time is that the hardware is functional.

The T16000 is an “ok” device but it’s flaw is using a potentiometer which inevitably fails. It’s not alone in this. All the mainstream products have similar design flaws but after years of replacing various cheaper devices (including a couple of T16000’s) I decided that with all the money I had spent I could have bought into VKB, Virpil etc. So I did. The “total cost of ownership” is better with quality gear but the cost is quite a bit higher so for those who aren’t quite sure that flight/space games aren’t for them it’s a big outlay.

Topic moved into #self-service:peripherals

I do try to keep everything turned off. The only AI I have on is for ATC.

It could even be a USB issue of some kind.

For now I’ll make sure to keep up with the pre-flight checks. It helped develop a habit of verifying flaps and trim just before take off.

Try using a powered USB multiple plugin.

Thanks…I’m using one.

I have seen some instances where deadzones helped in situations like this.

The T1600 stick uses a Hall effect sensor.