Fssb R3 and TUSBA questions
-
The Whog has a CMS hat with a down button action, the Cougar does not.
That being said, I use the Whog FSS on the Cougar-FCC3 base because i like the Whog stick grip better.
Cougar sticks had two different paint treatments over its production runs. One was matt black and one was shiny black. One was more succeptable to palm sweat/salt than the other and would come off eventually. The Whog does not suffer this issue afaik. Real FSS eventually wear through too, so its not that bad of a thing unless you like them minty like I do.
Just to avoid confusion - by down, AV8R mean’s depressing. Most people read CMS down as CMS Aft - I see the confusion frequently, so thought I’d quickly stick my nose in
-
Just to avoid confusion - by down, AV8R mean’s depressing. Most people read CMS down as CMS Aft - I see the confusion frequently, so thought I’d quickly stick my nose in
I think perhaps the Warthog had the same issues with the paint. I have a few Warthogs, and one of them which is from the first run has quite a bit of paint wearing off. And as you wrote I still prefer that stick as it shows the most use and looks legit.
-
I’ve only recently put a WHog stick grip onto my Cougar base (with force mod), and the hog stick paint has been good thus far. I’ve had both of the Cougar sticks and have noticed the difference in the paint jobs. Same semi sweaty hand.
Not to start a double entendre thing, but… I’ve read that those who use alcohol based hand lotion will degrade the paint faster. Now if you’re flying drunk and spilling Vodka and brews on the controllers, well that might be realistic too
-
To my simple way of boiling it down, I see the TARGET software (GUI or Script) as a means to:
- relieve the user from the DX 32 buttons and another 32 for shifted buttons per DX controller accounting and assignment chore
- ability to run a customized game function to stick hat/button/slider/toggle mapping profile in either graphical or text modes. Thus eliminating the game specific mapping file such as BMS Keymap file and its hex encoded function format.
- ability to have user defined axes curves, button delays, holds, nesting; which is good for menu commands
- ability to combine multiple TM controllers into one virtual controller not limited to the DX 32 button limitation
- ability to control the LEDs on the WarHog throttle base, for gear status or flight surface states, etc.
That being said, I just use a manually customized version of the BMS FULL KEYMAPPING file and as DX controllers. For DCS, I use their built in mapping GUI. So while I did use TARGET GUI for IL2-CLOD, I really don’t use TARGET much anymore.
Now if my hotas use model was to use as many sim functions as possible, and didn’t care about the realistic FSS and TQS mapping BMS Keymap provides, or if I was using the Warthog throttle instead of a TQS, then I might consider using TARGET.
-
I applaud this effort by White-Eagle, being one of his customers. Its important to note that this WHog force mod will not be compatible to TARGET as it will be a pure DX controller.
Which is fine by me!
-
I am having problems assigning rthe DX keys to the correct switches in the throttle. I am running the FFSB r3 and TUSBA with crosswind pedals. I have tried modifying the order of the devices in devicesorting.txt file but if I put the TUSBA on second place the first button of the throttle is #32 so it assigns it to an OSB instead of the radio comms and so on on every other switch of the throttle. Can you help me?
-
-
Each DX device has max 32 buttons available for windows, so it’s perfectly normal that your Tubsa will start at 32 when it’s set to second place. It’s actually #33 but BMS counts #1 as item 0.Just assign the correct callbacks to the 32 in sequence, no?
And that little difference is important to catch when manually editing BMS keymapping files.
-
Ok I have assigned the correct dx buttons to the handle and throttle. Pushing the pinky button allows the shifted layer in the stick but with the TUSBA the pinky wont show the new shifted buttons for the throttle. I am running the FSSB R3 directly to the realsim pcb not using the thrustmaster warthog pcb. In this situation I lose the shifted layer in throttle buttons no?
-
no, it should work. I use shifted buttons of the throttle for idle detent for example.
-
But are you using the fssb r3 directly to the pc or have installed the thrustmaster pcb from the warthog to the fssb r3?
-
But are you using the fssb r3 directly to the pc or have installed the thrustmaster pcb from the warthog to the fssb r3?
I have a Cougar with RS FSSB1 on the Cougar PCB. But if you have issues with throttle via TUBSA, what FCC you have doesn’t matter. TUSBA makes the throttle a separate HID device. So you just need to know which button number BMS sees for the switch you wish to use in shifted function.
Also note that by default BMS sets shifted layers to start with a 256 number offset, but if you have more devices, it can happen that those 256 etc numbers are still used by Windows for your regular HID devices so you need to increase the offset in BMS config so that the offset starts with a number out of the regular HID range. -
Thanks I have the fssb the tusba the rudder pedals and thats it. When I presa the shift un the stick it se es correctly new numbers i.e. 68 69 etc but un the throttle it just shows the same dx number shifted or not. Should I look the key file?
Enviado desde mi SM-A500FU mediante Tapatalk
-
Thanks I have the fssb the tusba the rudder pedals and thats it. When I presa the shift un the stick it se es correctly new numbers i.e. 68 69 etc but un the throttle it just shows the same dx number shifted or not. Should I look the key file?
Enviado desde mi SM-A500FU mediante Tapatalk
I have the Cougar, Tusba & rusba.
Note that in BMS it will never show the shifted number. It will only work once you are inside the pit.
So take my example for reference. I have pinkyshift + uncage (push range button on throttle) for idle detent. When I push the uncage in BMS setup page, it shows 140.
So in my keyfile it uses SimToggleMissileCage 139 8 -2 0 0x0 0. See it’s 139 and not 140 because nr 1 in Windows is nr 0 in BMS logic.
When I want to set the idle detent on the shifted layer, I add 256. So 139+256=395. SimThrottleIdleDetent 395 8 -2 0 0x0 0
Also, don’t forget to set the pinky shift in both normal and shifted number! In my case SimHotasPinkyShift 34 -1 -2 0 0x0 0 SimHotasPinkyShift 290 -1 -2 0 0x0 0 -
I will try that. However in my stick setup page in game Isee the dx button numbers and If I press the pinky I see the sam numbers +32 and that wont happen with the throttle buttons.
Enviado desde mi iPad utilizando Tapatalk
-
I will try that. However in my stick setup page in game Isee the dx button numbers and If I press the pinky I see the sam numbers +32 and that wont happen with the throttle buttons.
Enviado desde mi iPad utilizando Tapatalk
weird, normally BMS doesn’t show the shifted layers. And +32 is weird too.
Check your “falcon bms.cfg” file inside the User/Config folder and look for the line set g_nHotasPinkyShiftMagnitude 256, it should say 256 by default. -
I am trying to use the key editor excel file that comes with bms, I select in the DX page threustmaster combos warthog joystick and TUSBA TQS. The joystick lets me choose two layers but the TUSBA only one (the 3rd is yellow). WHy I am not able to assign a 4th shifted layer for the TUSBA?
-
you are going for a warthog and r3??
why not get a used cougar, then r2?
I never got why the R3 is for Warthog only. At least in the Standalone version you just exchange the grip and thats it. Shouldn’t matter if its a cougar grip.
-
It works perfectly with cougar stick. You’ll just lose the CMS push function.
There are two ways of using FSSB3: with Warthog PCB or with Realsimulator one that is included. If you don’t have the Warthog you won’t be able to select its PCB but it’ll work perfectly with the other.
BTW, I don’t own it. It’s a friend of mine.
Cheers