Viper TQS Calibration procedure
-
I’ve received a procedure from TM to recalibrate the Viper TQS, i share it here :
https://drive.google.com/file/d/1i8BG-12riwqvIPMwO10oMnzfL4Vx-Zpn/view?usp=sharing
Hope it will help ! -
@benco that is excellent … thanks for sharing it out!
-
@benco
Thank you for sharing!!
Regards,
Tomcattwo
(VoiceClone) -
@benco thanks for sharing. Surprisingly, TM don’t publish this on the TQS support section for whatever reason…Information hiding to keep the support busy?
-
@r00t They’ve probably not got around to it yet.
-
@benco My radar cursor was aiming down unintentionally. Hope this helps.
-
@Ebubekir-Çağrı-Şen i had the same issue, i set “Large” in the “DeadZone” for “Cursor X and Y” in the “Avionics Control” tab.
-
@benco did the calibration help for this issue?
-
@wazza69 yes, it could :
-
@wazza69 No it doesn’t
-
@Ebubekir-Çağrı-Şen
I tried this, but for some reason it is not detecting the full range of motion for the throttle. Even with afterburner it is only about 75%.
Update! It works! I think I was pressing the comm switch too long, instead of just 3 seconds to start the calibration.
-
Does anyone use the Viper TQS in IL2 Battle of Stalingrad?
Update: Problem solved. Using the method in “Solution Found” did not change the calibration in BMS, and it did solve the issue in IL2 Sturmovik BoS.
I can’t set up the Thrustmaster Viper TQS throttle to work in IL-2 Battle of Stalingrad. All other buttons are recognized. Furthermore, it works fine in Falcon BMS.
I saw this solution, “SOLUTION FOUND”
"It’s necessary to change the position (on the throttle axis) where the button is activated.
To do so :- Move the throttle to the new position where you want the button activated (in that case, 100 instead of ~80%)
- Press and hold for 2 seconds the paddle + the chaff/flare button (on the side) "
I do not want to do that, because it will change the calibration, and I use this throttle primarily in Falcon BMS. I do not want to have to reset the calibration every time I go back and forth between Falcon BMS and IL2 BOS. Any ideas?
Is there anything else that I can try?
-
@benco
Thanks a lot for this procedure!
Unfortunately, I have an additional enigma here, and I hope somebody can help me out.Yes, it’s the well-known IDLE DETENT story.
I understand and appreciate the “PRESS” and “RELEASE” logic. But what I definitely do NOT understand is this:The tiresome BUTTON 18…
… the “trigger spot” should be located right BEFORE the bump, right?
I mean, inside the “engine-off” area.In my case, it is located (and triggering) exactly at the IDLE spot - actually AFTER the bump.
Can this be correct?
Can this be corrected?
I read in the calibration PDF file, that button 19 (the AB detent) can be fine-tuned by hardware.
But can button 18?Latest firmware 1.26 is installed…
EDIT - I opened a new thread about this issue: Viper TQS: Button 18 actually in the wrong place
-
Update!
I was able to solve my “button 18 displacement” with this calibration procedure - thousand thanks to @benco!Took me a couple of tries.
But I figured out that at the start of the calibration you probably need to keep button 5 pressed WHILE pluggin in.
Or simply keep pressing button 5 for longer than 3 seconds.Either way, I am relieved and happy
Thanks again mate!!! -
I could use help, my viper tqs axis calibration go all screwed up again. I tried maybe 10 times to recalibrate, but no luck. I uninstalled and reinstalled the drivers. When calibrating I tried holding in button 5 three seconds, I tried holding it in longer, I tried holding it while plugging in the viper tqs. I’m really frustrated at this point. Everything worked fine for over a month, and all of a sudden today it was not working. I suspect when I was messing with discord’s press to talk function and using button 5 for that, that might have caused the screw up, so I won’t use that anymore, but I just can’t get things fixed here. Anyone have any ideas?
Update, I finally got it recalibrated! However, I have no idea why it was not working and why it is now working. This happened the 2nd day I owned the Viper TQS, and now this is the second time, about two months later. Maybe what worked was after making sure the drivers were installed, I then updated the drivers, then calibrated. Or maybe it was after removing the calibration button as the talk button for discord. Who knows, but there could be a better way to calibrate this, that is for sure!
Anyone else being driven mad by the calibration procedure? I’m a teacher, so I am already nuts, this is just making me nuttier, which I did not know was possible.
-
@Scotters For me, the best way to ensure a positive calibration result was:
Keep pressing #5 while pluggin in and confirm that all the TQS lights stay dark.
After a couple of seconds, release the button and confirm that all lights turn on.For my understanding, that is the “ready” signal for the calibration.
-
@Amadeus75 Thank you, that is a great way of know if the calibration procedure is working!
Do you guys enable virtual buttons or not? It appears that when I mapped everything back a couple of months ago, I had virtual buttons off. When I enable them, it messed up some of my keymapping, but when turned off, all was good. If I want to enable virtual buttons, I guess I would just have to recalibrate some things, but do I need virtual buttons on?
-
@Scotters
I do not use the virtual buttons.
With the new BMS launcher and the “press” and “release” logic, there is no need for them.
I don’t know about other sims… but if it’s just for BMS, then better keep it simple.