RADAR CURSOR COUGAR
-
Hi!
Can anybody point me to a joystick-file for TM Cougar hotas with the radarcursor working? I can’t seem to find it and am not capable of programming it with Foxy.
And maybe there is a file with wich you wil be able to use the cursor as a mouse/look funtion? That would be nice…Thanks!
-
dont need a joystick file (examplehere.tmj), you can use the cougar fully in unprogrammed mode (red button) with BMS.
Do that, and the radar cursor is a pair of DX axes, which you can assign within BMS setup quite simply.
-
What is wrong with Dunc_DX, which is included in your install?
You’ll find it in your :\Falcon BMS 4.33 U1\Docs\Key Files & Input\Device Setup Guides & Profiles\TM HOTAS Cougar folder, complete with instructions on how to set everything up.
-
What is wrong with Dunc_DX, which is included in your install?
You’ll find it in your :\Falcon BMS 4.33 U1\Docs\Key Files & Input\Device Setup Guides & Profiles\TM HOTAS Cougar folder, complete with instructions on how to set everything up.
+1. Dunc’s is what I’m using and will sort the issue.
-
The only problem is that you lose the analog capability of the left and right wheel brakes. BMS has a number of limited analog axis.
-
The only problem is that you lose the analog capability of the left and right wheel brakes. BMS has a number of limited analog axis.
Well no, BMS is not limited by the number of analog axes it uses.
You lose the analog capability of the left and right wheel brakes of the Cougar, only if you actually own the Cougar rudder pedals. And you can get around that with either a TUSBA or RUSBA device I believe (I dont own the rudder pedals personally).
Each controller can only present up to 8 DX axes to windows, however. So the Cougar, as a single controller, is limited to eight axes - for instance, X and Y, throttle, cursor x and y, rotaries 1 and 2, makes 7 axes - rudder would be 8. So the rudder pedals clearly would be 10, which windows will not accept. plugging the rudder into a RUSBA will present the rudder as a separate controller, and get around this limitation. Or if you dont own cougar pedals, then you dont have this issue to start with.
In either case, BMS itself has no issue with the number of axes it sees from windows. Your issue lies in getting windows to see all the axes.
-
As Blu3wolf correctly stated above this is a DirectX limitation, which only affects you if you have the old RCS rudder pedals which plug directly into the Cougar HOTAS sidestick base.
In addition to using a RUSBA (or TUSBA for the TQS) you could also change the axes which are active in CCP (see page 3 of TM Cougar - DX Setup Guide), though of course you would have to choose 2 other axes which you would lose if you enabled the toe brakes.
All of which is completely irrelevant to the Original Poster, unless he tells us he has a set of these old rudder pedals, which so far he has not.
-
Thanks everybody. Can’t get it done but I’ll keep trying. Lot’s off useful information. This forum rocks…
update: got it fixed! And in the process made a blu-107 hit an airstrip in ccrp-mode! The wrong airstrip but oh well…
-
I am using my Cougar with Duncs profile and works perfectly well and absolutely realistic, also I am using the CH pedals, so I have also toe brakes working
-
What is wrong with Dunc_DX, which is included in your install?
You’ll find it in your :\Falcon BMS 4.33 U1\Docs\Key Files & Input\Device Setup Guides & Profiles\TM HOTAS Cougar folder, complete with instructions on how to set everything up.
+1
-
Can’t get it done but I’ll keep trying.
In BMS UI setup >controllers >advanced >avionics, try using Cougar “Toe brake left” axis for cursor Y and “range” axis for cursor X. That is what I used before my TUSBA.
-
Foxy is a not needed confusion to most people.
When you open your Cougar control panel it should look like this in regard to the HOTAS Axes selected.
And in bms setup/controllers/advanced/Avionics the cursor X and Y are like this
-
Speaking of the Radar Cursor. I already posted the question somewhere else but maybe someone can confirm:
To my understanding moving the microstick to the direction of the writing (RDR CURSOR/ENABLE) is UP, so the cursor moves up then. And as far as I remember when using the Cougar “the normal way” that was how it worked. Am I right?
However with TUSBA now I have to reverse axis in the BMS Setup (Cursor X=Mouse Y). Is that the way it is?
-
PP1,
do you have the cougar control panel installed & are you using windows 10 maybe? I’d looked for a solution as this is my setup & my cougars are now working,I’ve installed the 2007 vista 64bit vista drivers & I’m using windows10 64bit , I just went into the device manager after plugging in the cougar as windows 10 doesn’t pick out the location of the drivers for some reason after installing these drivers, I right clicked on the in/out hotas that where showing as not installed correctly in the device manager & pointed the install drivers to the installed location I’d put the drivers at & it installed the Cougar no problem,
you need to select the manual calibration & apply before you go in the game, then when in the game you should see the micro stick x/y Axis now working if you have assigned them as per x/y toe brake etc, hope this helps,
Brilliant job btw & thanks to all who have taken Falcon4 to where it is now.
thanks,
-
Foxy is a not needed confusion to most people.
When you open your Cougar control panel it should look like this in regard to the HOTAS Axes selected.
And in bms setup/controllers/advanced/Avionics the cursor X and Y are like this
PP1,
you need to select the manual calibration & apply before you go in the game, then when in the game you should see the micro stick x/y Axis now working if you have assigned them as per x/y toe brake etc, hope this helps,
Brilliant job btw & thanks to all who have taken Falcon4 to where it is now.
thanks,
THANK YOU!!! I wish I had found this thread hours ago. I figured out the part about the default dogfight switch in the config file and reassigning the microstick axis in CCP from Duncan’s guide in the input documentation folder, but it wouldn’t work without calibrating. I even tried setting up the whole profile with the pinky switch layer, still no luck. But as soon as I calibrated it properly, BMS recognizes the microswitch axis and I can slew the radar cursor. YEA! I was about to give up.
-
+1
-
Greetings - Brand New to BMS 4.33 (Previously hard core SP3/SP4/Early BMS…
Having problem with analog microstick - went through step-by-step process and got all of the wright indications with my CCP - FLCS/TQS/Elite TM Rudders Cougar combination! But inadvertently chose Mouse and Keyboard for Microstick axes! NOW I cannot get toe brake HOTAS choices back to select. Even if a repeat entire process and re-calibrate - I can only get “Keyboard” and “Mouse” to be available for selection (HOTAS analog toe-brake never returned to be chosen)! Like I said, they were there originally BUT because a messed with RNG and ANT axes first - lost the chance. What am I doing wrong or missing?Currently using a HP gaming PC with Win 10 and successful install of BMS 4.33 - HOTAS Cougar and following Dunc’s Cougar DX guide to the letter . . .
-
Are you talking about configuring this in BMS or in the Cougar software itself? The name escapes me. Just PM me to remind me and I will have a look when I get home. if you have discord, we can hop onto that and I can see what I can do to help out.
For reference, I’m using a totally vanilla TM Cougar myself with TM RCS pedals and have no issues with getting this to work with BMS using said Dunc’s guide. (I’m also only using my Cougar in DX mode, I’m not using Foxy or anything either).
-
Thanks TAZZ - I finally figured it out - although I duplicated the BMS specific axes assignment changes in the HOTAS COUGAR CCP - I never actually “Applied” them. Once I did that all CONTROLLER SETUP options were fully available in BMS sim! No more issues - THANKS FOR THE RESPONSE!
