Tusba Cougar throttle cannot be calibrated in Win11
-
Recently upgraded my rig with a brand new pc running on Win11. Downloaded 4.37 and then the problems showed up. 1) I can’t seem to calibrate any of the axes on my Tusba Cougar Throttle ( throttle axis AND x- and y-axis of the micro cursor) 2) When I want to change something in the config tree I get the following error message:
2
Any suggestion is welcome, because I’m starting to get desperate here
-
-
within BMS UI or in the first launcher?
-
have you pointed the patcher to bms? It seems to reference the old.Falcon 4.0
-
-
- To be clear: I’m talking about the TUSBA configuration
- Strange indeed. Hadn’t noticed it before.
-
- So the Tusba software itself … Cant help you there sadly enough
- It was my default upon installing 437. Had to set it to the bms exe (main screen of f4patch top and centre)
-
Hi,
i use a Cougar Throttle via TUSABA under windows 11.
I don’t understand your problem since idk what F4Patch has to do with throttle calibration.I use the latest version of RS_HID_DEV_TOOL_V12 to do the calibration for my TUSBA throttle.
Maybe you can explain in more detail what you try to do, screenshots of the actual process which fails helps
cheers
MagicP.S. i need to delete the TUSBA windows device from time to time and then rediscover/reinstall it to fix calibration problems.
-
Since I re-installed 4.37 on my new pc on Win11 I ecountered multiple problems . One of them is the TUSBA calibration. Another is the F4 patch problem. They are not related (I hope)
-
-
Downloaded the latest TUSBA firmware (v1.07). After recalibrating I get the same problem:
Min: 2351 (should be 0) = 97%
Max: 3968 (should be 4095) = 58%
Aft: 2548 = 63%
Idle: 3782 = 92% -
And this is what I get in BMS UI. This is in full AB:
-
@Doc0301 can you send a RS screen with throthle at minimun?
-
This is what i will make
Unninstal tusba in device panel
Restart Pc (tusba auto recognized)
Pair axes, moving all to Max and minimun.See if the throthle axis moves all their routes (full Green and full grey)
-
Another important thing, unmark the vertical Green bar (right mouse Burton i think) to disconnect the three throthle axes, to use all the throthle as an axis.
At this moment there is no way to use three axes (idle, min and aft) in bms, only one Axis.
-
This is with throttle at minimum:
And this is at maximum:
-
@Doc0301 Try calibrating in Windows instead of RS tool.
-
Unninstal device in Devices
Restart
PairI make that and works for me.
-
@Skorp I think it’s one of the last thing to do and perhaps fresh install of BMS can resolve something.
If it doesn’t work, back on win10
-
Dont go uninstalling anything until you have removed RS from the equation, and as @Icarus said, check if your device is showing up as a HID device in windows, and try calibrate it there.
-
Yes, bms is not the problem.
-
Problem solved !!
Windows callibration made that the full range was recognized again !! Then pairing TUSBA & Throttle and set calibration in RS HID Device tool. Then deleted the old TUSBA controller files of the Alternate Launcher so that new files could be made with a new callibration.
Now everything works perfect!
You guys have NO idea how gratefull I am to this community for helping me out . It’s a gratifying experience in this day and age that totally strangers are willing to sacrifice their time to solve your problem. You guys rock! And BMS forever !!!
Tiger! Tiger! Tiger!