Key files don't get mapped
-
I have the TM Cougar and everything is working fine with it. But When in game setup after loading and saving a certain file I can see the name of that particular file under “current key file” but I don’t see the mapping happening at all. Cougars button when triggered only give OSB L or R. I loaded and saved many file like Dunc_DX maverick’s DeeJay’s. In each case the mapping juts don’t happen. What is going on here?
-
Sometimes buttons can get stuck in an on state. So if you are in setup and trying to press a button to set it up, it will sense the the stuck one instead. Safer to set up buttons by editing key file with text editor. If it is something other than this then maybe someone with more knowledge of cougar can chime in.
-
The two-column list is only keyboard mapping. Joystick mapping will never show up in the little white box. It still gets bound but you need to use the bottom “a button has been pressed” output text to verify.
-
you mean the input I think, yes the input gives me only left or right OSB numbers not the function of that button. everything else looks real fine.
-
Yes it will give the function. For me it says for example:
INPUT Button 33
Trigger 1/2Another example:
INPUT Button 51
No Function Assigned -
yes when it is working the way it is supposed the keys give you their function, that where I have the problem the functions are not mapped to the cougar hotas. Might be a result of some windows 8 updating?
-
May be. In control panel “Set up USB game controllers” select joystick, properties you can see the buttons illuminate (red circles)?
What is the bottom of your key file opened in Notepad?
-
its not the latest update, just checked it.
I have windows 8.* so I don’t see exactly what you described but I can see a game controller page. The first one show Saitek rudder and the second is the hotas cougar. I tried to make the cougar the first without success, could that be the problem? By the way when I click on keyboard command and it turns blue when I click on hotas button then that key command is assigned permenantly to that cougar button. But I can’t do that for the entire key command because there are too many of them -
ok fixed it, it was interference from the Saitek rudder.