Arrow III e Saitek X52 Pro



  • ... I try to post here this problem of interfacing between my Saitek X52 Pro and the Arrow III ... I can't understand why the rudder is not positioned in the center ... or only on the right or only on the left. ..
    I apologize if this question of mine is not your responsibility, of course you are authorized to delete it.
    David



  • In the control settings for the X52 Pro, make sure you are using the standard RUDDER AXIS, and not anything else. I am of course assuming you are using the Twist grip on the joystick for Rudder.

    So in the controls search box, look for "Rudder" (without the quotes), and then "Rudder Axis", click on that and assign your twist grip as usual. This should work.



  • @Tigerclaw

    screenshot 34.png

    I have assigned this but the rudder does not stop in the center ... or right or left ... ☹



  • It "looks" right for the Asse (Axis) but it should be in the centre. Maybe check for anything else that is assigned to the same axis? Look at the sensibilita (sensitivities) and see if it moves in there? Check in windows devices to see if the axis actually moves from left to right?

    Those are where I would start. If it functions in those areas, then I'm stuck for more ideas.



  • @Tigerclaw
    ... I checked everything you suggested to me everything is ok, so the problem is the drivers in fact if I uninstall them and let the X52 work with those of Win10 of 2006 curiously it works .. does it seem curious?



  • No not curious at all, the Saitek drivers aren’t really designed for today’s simulation.
    If you’ve got it working by using Windows drivers, that’s all good then yes?



  • @Tigerclaw said in Arrow III e Saitek X52 Pro:

    Not not curious at all, the Saitek drivers aren’t really designed for today’s simulation.
    If you’ve got it working by using Windows drivers, that’s all good then yes?

    ... let's say that it works even if the rudder jerks .. for example on taxis you can't turn with progression but suddenly and this ruins the simulation ... also with the Win 10 Drivers the Properties Window doesn't work 'of the Saitek ... this is curious?