Hotas Cougar BMS 4.33 profile
-
-
Why?
Dunc_DX joystick profile and keyfile are already in the 4.33 install, in the \Falcon BMS 4.33\Docs\Key Files & Input\Dunc_DX folder.
Everything you need for a realistic profile, including instructions.
-
Oh sorry then , you can close the post or just leave it for other users to upload their profile is they want
-
Btw.
the Dunc_DX key file is by 99% identical to the BMS Full key file.
Only Padlock and Padlock Mode = AA have swapped key assignments. -
Thanks for that Kolbe, you’ve just answered a question for me
-
Will the Cougar Profile from 4.32 work with 4.33?
Thanks Guys, Yogi
-
I have been using Speedo-Falcon profile since allied force falcon with some reworking in foxy . The only trouble I have noticed so far is the throttle on the ground does not respond sharply as in 4.32. But in the air it is fine. Been looking and trying Dunc_DX, but not enough time.
-
problem with DUNK 4.33 profile , i open it from Foxy and i get : Error 1000 : Source file errors and device errors
ERROR 1000: Could not open input file
The compiler for some reason wasn’t able to open up the joystick file. Either it couldn’t find it, it contains no statements, or is in the wrong format (it could be a file for the original TM controllers). This shouldn’t occur if you’re compiling/downloading from Foxy.My old profiles eg switch_profile.tmj work ok
-
Got Win10, and Thrustmaster tells me that Hotas Cougar control panel is not needed anymore. Control panel do not find my Cougar anyhow.
So far so good. Moved Dunc_DX to User/Config and loaded it into BMS setup in the game, put there was no reaction on the switches.
It seem like I have to configure all switches by my self, or do anyone have a tip? -
Does the 4.33 install on Windows 7 require Foxy or T.A.R.G.E.T. at all, or does it just go through Windows 7 default HID driver settings for Cougar? Same for Dunc_DX files?
-
im new and just testing but so far it doesnt appear as if I need and TM software. working well as is.
-
problem with DUNK 4.33 profile , i open it from Foxy and i get : Error 1000 : Source file errors and device errors
ERROR 1000: Could not open input file
The compiler for some reason wasn’t able to open up the joystick file. Either it couldn’t find it, it contains no statements, or is in the wrong format (it could be a file for the original TM controllers). This shouldn’t occur if you’re compiling/downloading from Foxy.My old profiles eg switch_profile.tmj work ok
Geraki, have you copied Dunk 4.33 profile .tmj and .tmm to Foxy folder, and then load it from Foxy?
Once I had a similar problem and it was because forgot that joystick profiles must be copied to Foxy folder first. I mean the folder where Foxy has all their joystick files.
-
Does the 4.33 install on Windows 7 require Foxy or T.A.R.G.E.T. at all, or does it just go through Windows 7 default HID driver settings for Cougar? Same for Dunc_DX files?
Dunc_DX files uses DirectX buttons for 99% of the profile. Only PadlockAA, 3d Cockpit switching and wheelbrakes are used in Dunc_DX profile for foxy.
What this means, is that all the setup is on the Dunc_DX.key, and you should load that from BMS UI, not FOXY.
I was gonna say that you dont need foxy at all if you don’t need the 3 commands I said before, but I just realized that you need Foxy to clean up the joystick files compiled beforehand on your HOTAS.
To answer your first question, if you managed to install your HOTAS Cougar on windows 7 and it is recognizable as a Direct X input, then it will be enough for 4.33 to use it.
But again, Cougar installer installs Cougar CCP and Foxy, so you can use Foxy
-
Simple question, can we made a config witout DirectX?
-
Simple question, can we made a config witout DirectX?
Yes. Just use Target or Foxy as normal.