saitek quadrant throttle doesn't work.

[Sakkay]

In the menu is good, in the  flight didn't.

[ST_ami7b5]

mine works OK...

[HagarTheHorrible]

Mine works too.

[VR-DriftaholiC]

I have two and they both work. Does the light remain on?

[Beazil]

I have a throttle quadrant as well, but I've found many of the items I'd like to map to it aren't working (ie:  flaps).  I have to map them to buttons at the moment.  However, in conjunction with Driftaholic's comment and other posts I've found online, I've noticed and read that the Saitek quadrant has issues with usb 3.0.  You may have to either turn off usb 3.0 or simply use a usb 2.0 port if you have one available.  I'm not saying this is the answer - but I did have issues with my quadrant power flashing off and on until I changed from a 3.0 port to a 2.0 port.  Good luck.  Also, I have not attempted to change my mapping of flaps to the quadrant from a button, since I last mapped my controllers some time ago.  So it is possible that this issue has been fixed in subsequent patches. 

[VR-DriftaholiC]

I guess I can elaborate a little,

 

Beazil, The reason you can't bind flaps to an axis is because they worked as a button or a lever with only on/off in game. 

 

My throttles work fine in USB 3.0. Make sure you use Saitek's drivers: http://www.saitek.com/uk/down/drivers.php

 

Also make sure you can see them moving in "Game Controllers" section of Control Panel.

Edited September 26, 2014 by driftaholic

[=69.GIAP=MYATA]

I have a different issue with my setup.

I use a Warthog, Simped pedals and 2 Saitek Throttle Quadrants. 

When I start setting up my controls everything is fine until I assign the second Lever of the second Quad.

It looks good on the main assignment screen but if I check the details (the screen that allows you to change the curve) I see that the virtual level moves only up to about 50% even my real live Lever is already at about 98%. Then there is a sudden jump to full no the virtual one.

 

I already tried to re-install the drivers but wasn't able to get rid of this behavior.

This makes it impossible to use as every time I reduce the setting during flight just a little bit the value jumps to 50%.

 

Anyone experienced something similar?

 

I haven't opened a ticket yet as I hoped it is a known issue, bug, that is already on the devs list but as I saw that driftaholic owns two and they are working properly I am cocerned now.