Viper TQS throttle problem
-
I have a strange problem with the TM Viper TQS. All the buttons work OK in BMS but the throttle itself does not increase incrementally when I move the throttle forward. Instead, after just 1-2 millimiters of movement the Z axis indicator jumps to the afterburner position. No way I can increase power just a little bit at a time.
I reinstalled the driver. Is there a way to reset the TQS or do I have to calibrate the throttle. If so, how would I do that? Configuring the Z axis response in the T.A.R.G.E.T. app doesn’t make a difference.
Could it be that the potentiometer is fubar? If so I would have to return the device and ask for a replacement.
Any ideas/help are greatly appreciated.
Bikeman
-
@Bikeman
Sounds to me as if the AB-position is set at the wrong place.
Try opening the setup (in-game) and reconfigure the AB-threshold. -
@Amadeus75 tnx for your reply. Done that, doesn’t solve the problem. Btw, I see the same effect in DCS
-
@Bikeman
You might want to follow this thread as well…
https://forum.falcon-bms.com/topic/25023/inverted-throttle-idle-detent-not-working
Maybe there are similarities… -
It will not help you, but everthing is ok here : so “Could it be that the potentiometer is fubar?” could be the right question.
-
@Bikeman VKB makes a great little “JoyTester” applet … works for all HID joystick/gamepad devices, nothing VKB specific.
https://www.vkbcontrollers.co.uk/pages/downloads
also start/run Joy.cpl for the Windows builtin calibration tool …
I believe those calibration-ranges are stored in the registry, under
[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput]
if you need to delete them or reset them… might give you a lead, to google for more help.
-
I had a problem with erratic behaviour of my new TQS, albeit a different one and it was only triggered when I activated Opentrack. I had the device connected to a powered USD hub. It was solved when I plugged it directly in a free port on my PC. I know it is probably irrelevant but in the slight chance that it is not, I am posting this.
-
@airtex2019 Thanks for the useful link!
-
I have just had the very same problem. Move a few millimetres from idle and the output goes to 80%. A little more and button 19 is triggered. Mid-position and the output is 100%. Everything else seems ok.
I installed the software on another machine, plugged in the throttle, and had the same fault.
There is no ability to recalibrate it in the control panel. Thrustmaster overrides the Windows default control with its own and doesn’t provide a calibration facility.
Considering a button is also being triggered I expect that something has corrupted internally. Reinstalling the firmware made no difference.
This doesn’t look good for the Viper TQS IMO. Less than two weeks of use and it is broken.
I’ve opened a support ticket with Thrustmaster but I expect I will start an RMA on Monday and have a replacement sent out.
-
@scubapics is this with Target running or without?
I think there’s an easy registry hack to get back the stock Windows joy.cpl experience … if you want to try that (to recalibrate)
-
@airtex2019 I don’t think that will work as I installed the device onto a machine that has never had it installed previously. By virtue that it is also triggering a button press by just moving the throttle indicates a fault in the code within the device itself.
-
@scubapics Have you had any answer from TM support ?
same probleme than yours today, Just after iddle detent, from 0 to 80%.it appear that I can’t disabled virtual buttons too.
-
@Wingedsky @scubapics the symptoms here sound very similar to bug(s) that I fixed just yesterday…
I mean, if DCS and other apps are broken too, then yeah ok it’s clearly faulty hardware, return it.
But if the problem is just BMS … please consider trying the latest alpha-build of Alt Launcher to see if it cures the problem.
https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/releases
-
@Wingedsky said in Viper TQS throttle problem:
@scubapics Have you had any answer from TM support ?
same probleme than yours today, Just after iddle detent, from 0 to 80%.it appear that I can’t disabled virtual buttons too.
I did but I had already started the RMA process. It was collected today.
They wanted a video of the fault. I had already sent one with the support request. I fully expect others to start seeing this problem along with the replacement having it soon too unless it’s fixed in a firmware update.
-
@airtex2019 said in Viper TQS throttle problem:
@Wingedsky @scubapics the symptoms here sound very similar to bug(s) that I fixed just yesterday…
I mean, if DCS and other apps are broken too, then yeah ok it’s clearly faulty hardware, return it.
But if the problem is just BMS … please consider trying the latest alpha-build of Alt Launcher to see if it cures the problem.
https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/releases
It’s not game related. The fault is with the unit itself as can be seen in the windows control panel
game controllers applet. -
-
It’s not game related. The fault is with the unit itself as can be seen in the windows control panel
game controllers applet.Same for me , not game related
-
@Wingedsky @scubapics cool… well, not cool … but I’d feel bad if a simple bug caused a number of people to return their nice new throttles
-
@scubapics same problems as the ones I encountered. I returned the TQS to the seller and am expecting a replacement any day soon.
-
@Bikeman said in Viper TQS throttle problem:
I have a strange problem with the TM Viper TQS. All the buttons work OK in BMS but the throttle itself does not increase incrementally when I move the throttle forward. Instead, after just 1-2 millimiters of movement the Z axis indicator jumps to the afterburner position. No way I can increase power just a little bit at a time.
I reinstalled the driver. Is there a way to reset the TQS or do I have to calibrate the throttle. If so, how would I do that? Configuring the Z axis response in the T.A.R.G.E.T. app doesn’t make a difference.
Could it be that the potentiometer is fubar? If so I would have to return the device and ask for a replacement.
Any ideas/help are greatly appreciated.
Bikeman
Problem solved. I returned the unit and got a new one. New it works like a charm. Makes one wonder what kind of quality control TM has (if any).
-
Problem solved. I returned the unit and got a new one. New it works like a charm. Makes one wonder what kind of quality control TM has (if any).
I returned mine today too. Will have one new soon