I would like to compare notes with an X56 user. I am having some problems with mine in MSFS and would like to see if other users are also.
Your reply would be greatly appreciated.
I’m not sure with the X56, but Logitech (Saitek) pedals, yokes, and throttles are particularly fussy in regards to calibration in MSFS, often showing issues like yours.
The only thing I have found to use to calibrate them properly is Diview.
https://heusinkveld.com/download-diview/
Probably worth a try, it might help your issue.
1 Like
Been using for about 2 years. No problems though I wish the Z axis was smoother and had a more natural dead zone.
What problem are you having?
Not using X56 but X52. In any case, explain your issues and we’ll try to help you.
The problems I am having are with my throttle axis, both of them are all of a sudden doing weird things. The left one works OK up to the 50% mark then jumps all the way to 100%. The right one immediately jumps to 50% when I touch it then only goes to 80% at full throttle. I have two X56 HOTAS systems and both of them act exactly the same. I have also gone back to P3D to test them there and they work as they should. So it seems that the problem is in MSFS. But it is odd that you guys aren’t have those problems. This is something that started just after the latest updates SU10 and the Canada 11. When I test these throttles with the X56 software and the joy.cpl they work fine. I have not been able to fly any planes in MSFS since this started and have gone back to P3D. I like P3D but I like MSFS more and would like to get this fixed.
1 Like
I’ve got the same problems with my Bravo after SU10 and Canada 
I have been using the X52 for almost 2 years now without issue. If I ask a dumb question, it’s only dumb if I don’t ask it…
-
I would initially rule out the HOTAS as the source since you have Two giving the same issue on Two separate systems.
-
Do you Program your Saitek from the HOTAS itself, or use the MSFS Lists and Sensitivity Curves? I use the HOTAS as they arrived, no attempt at trying to program anything directly from those?
-
How many different planes are affected?
-
Updates and Upgrades are the usual culprit.
I have had to redefine my Throttle setting in the MSFS Controls Options menu, from Throttle 1 Axis, to Throttle Axis, or to Throttle 1 (0 to 100%), or vice versa, after a Program Update or an Aircraft Upgrade…
Occasionally, a Reverse Axis box may have to be Checked, or Un-Checked. All it takes is a simple little program code element to throw things off.
In MSFS I am not using FSUIPC and have done all the binding using the sims binding and sensitivity settings. This is a problem with every airplane I have tried it on. I mainly just fly the warbirds and most recently the F/A 18. It’s the same with all of them, one or two engines. Throughout this forum and a couple others there are several threads and posts about throttle problems since the last updates. And they are all different brands of HOTAS. Today I remembered that Saitek has a utility program that resets all calibration. I am going to try that.
Using an X56 HOTAS here and no axis issues. Be sure you have them mapped correctly.
Did you have any luck using Diview?
I downloaded it but have not tried it yet. At a quick glance it looked like it was just for rudder pedals. I am also going to see if I can use FSUIPC with MSFS. Do you know how to do that. Do you just put it in the community folder or what?
FSUIPC has an installer.
It will place things properly.
It will not correct any issues, but you can calibrate with it.
I’m not sure if the freeware FSUIPC version is still available, and if so, what functions that version has.
You may need the payware version to get the calibration functions.
I have the Saitek rudder, pedals and throttles.
I run all but the throttles through FSUIPC.
I still use Diview (it isn’t just for pedals - it will do any controller) for my calibration.
I use FSUIPC for its response curves (called slope by FSUIPC), which, to me, seem to react much better than the default sensitivities.
I have recommended Diview a number of times to folks here that seemed to have had similar symptoms as you.
It has worked in all cases so far, but there is always a first where it may not!
It sounds like the throttle Extremity Dead Zone settings may be set to a high negative setting.
I also find that sometimes when my thottle doesn’t go to full throttle, I have to unplug my X-52 USB and plug it back in, while in the Sim. Everything works normal after that. I only have to do that, when first starting the Sim.
I have been trying to figure out how to use Diview to calibrate the x56 but not having any luck. Do you have a link to the manual? Specifically for Logitech X56 calibration. One thing I did notice when trying to use Diview is that my throttle X and Y axis do the same thing that they do in MSFS, jumping from 0 to 50% or 50% to 0. What is ultimately the weirdest thing is that this throttle works perfectly in P3D but does this weird stuff in MSFS. This is primarily the reason I think the problem is in MSFS. But there are replies in this topic from X56 users that say they are not having a problem like mine.
Hi - I’m having horrid issues with my Saitek x56 (Logitech took over I think). Actually, it is not mine but a friend’s system. When he applies throttle in the sensitivity settings the X and Y axis move perfectly smoothly through the line with no hiccoughs, but when flying any twin engined aircraft, there is huge flicking of the throttles, during increase or decrease, followed by no throttle at all when he lets go of the controller. I’ve tried reinstalling the software for the throttles, I’ve tried changing USB socket (power issue?), I’ve checked for mapping conflicts, I’ve not managed to solve the issue. I removed everything from the community folder - no joy. Very frustrating. Any thoughts?
1 Like
I have managed to get my throttle to work correctly by doing this: first I Googled Logitech X56 Throttle Clear Calibration Utility. There I found the instructions of how to do it. So I did that then I downloaded the calibration utility DIView. and used that to calibrate my throttle axis. I then went to MSFS to see if there was any change. Everthing was back to normal except the throttle range was 0 to 80%. I haven’t done it yet but I am going to go back to DIView and see if I can correct it. The instructions for using DIView were in a post right up above this one but now I can’t seem to find it. I think it was. Select the box for the controller you want to calibrate, then right click in that box and select Raw Data and note the numbers in red, then right click on the box again and choose Calibrate. Put those Raw Data numbers in the fields, check it and that’s it. No need to save.
Thanks to TheSevenFlyer
1 Like
So, I tried more calibration through various calibrators and could not get the throttles to go to 100%. But through considerable research I found that this is only with the F/A 18, which is the plane I had been doing all this troubleshooting with. To get to 100% you have to hit the afterburner button. All the other aircraft I tested the throttle range was a full 0 to 100%. Apparently I just never noticed that the throttles only went to 80% with the F18. Anyway, it looks like I am back in business. The DIView Calibration tool did tne trick for me.
3 Likes
Here are the instructions for DIView:
To use it, right click on the box of the controller you wish to calibrate.
Select “View Raw Data” at the bottom of the pop-up.
Next, in the same pop up, select calibration.
Use the raw data that appeared when you selected that.
Put the actual displayed raw data values into the applicable spots in the calibration pop-up.
That’s it, no save required.
Be careful with those things because they might mess all your tests. For example on some planes 0% is reached before the end of axis travel because at the end of travel (which would be 0) you actually enable the thrust reversers. For example, the A320Neo FBW does this.
I just noticed with my throttle (X-56 HOTAS) that when both are mapped to axis neither will actually move the throttle until the throttle/s (left & right) are at roughly 50 percent. Then you’ll see the throttle in the cockpit move. From there they move full range 0-100 percent.
Anyone else notice this?