View Full Version : Set Key; problem with a couple keys
Paulverisor64
08-01-08, 07:51 PM
I'd like to record a couple keys on top of other keys which will be activated by the control button and the selected key. There are 2 keys which I can not seem to set using the Setkey utility. These keys are the right arrow and down arrow.
Does anyone know if there is a way to have these 2 keys select correctly?
badwolf
08-01-08, 08:33 PM
One way is to give them temporary keys, then go into Commands_en.cfg and put in correct value. KEY_RIGHT = 0x27, KEY_DOWN = 0x28.
Paulverisor64
08-01-08, 10:04 PM
Thank you for your suggestion.
I took a look at the commands_en.cfg file and I must say that I'm a little confused with all the numbers and categories. I'm not sure of how much would have to be changed.
It is unfortunate that the 2 keys that I seem to not be able to select through Setkeys happen to be keys that are used by so many functions. (move, strafe, rotate etc...)
I've tried renaming assignments to another key in Setkeys but I've made the discovery that those keys are used in a similar fashion already.
badwolf
08-01-08, 10:48 PM
What exactly do you want the pair of "control + key" to do. I might be able to help.
Paulverisor64
08-02-08, 07:29 AM
What I would like to assign to the Control + Directional keys are the following actions.
Control + Left Arrow: Hard Left Rudder
Control + Right Arrow: Hard Right Rudder
Control + Up Arrow: Rudder Amidships
Control + Down Arrow: Set Heading to Current View
Since you can not steer the U-boat using the WASD keys I'd like to approximate these actions.
I have the N52TE keypad. With this you can place keys where ever the logical grouping might be. All of the keys assigned to looking around are in the WASD position. I have used up the key slots and would like to place the manual U-boat turning keys in the most logical place which would be over top of the other directionals. I don't ever use the slow turn which is Control + directional key.
I actually started re-assigning (without removing the default) all the directionals to use [, ], Home, End but am finding this isn't necessarily a good idea.
badwolf
08-02-08, 12:54 PM
I'm not familiar with that keypad, looked it up in google and it mentions a mini joystick. You might be able to use a macro, and assign your joystick to an unused key combination.
A long time ago, I tried the same thing, re-assigning the control-arrow keys to the funtions you mentioned. I had to remove the other commands first, but I didn't use it, can't remember why.
Paulverisor64
08-02-08, 01:04 PM
I have went into the en.cfg file and have for the most part figured out how to make the changes that I was looking for. Now the left arrow, right arrow, and up arrow work exactly the way I want them. I don't know if it was something that I messed up while switching out both the key0 and key1 but my heading to view key does not work. I will attach the lines that should instruct "Heading to View" and just for comparison purposes also attach "View to Heading" down below.
[Cmd148]
Name=Heading_to_view
Ctxt=1
Key0=0xBB,C,"="
Key1=0x28,c,"CTRL Down Arrow"
[Cmd149]
Name=View_to_heading
Ctxt=1
Key0=0xBD,,"-"
I have tried the keyboard "=" as well as the "CTRL Down Arrow" and they both don't work.
They both appear correctly in the Setkeys keyboard callout.
Thank you for pointing me in the right direction, hopefully someone might have an idea of why the Heading to View command doesn't work.
badwolf
08-02-08, 04:11 PM
[Cmd148]
Name=Heading_to_view
Ctxt=1
Key0=0xBB,C,"="
Key1=0x28,c,"CTRL Down Arrow"
I always had trouble with this command with the "=" sign, even though it's in quatations. This is the original.
Name=Heading_to_view
Ctxt=1
Key0=0xBB,,"+"
Change the "=" to a "+" or "Equals Key"
Name=Heading_to_view
Ctxt=1
Key0=0xBB,C,"+"
Key1=0x28,c,"CTRL Down Arrow
but still press the same key =
Whenever you change [Cmd148] and use the = key in setkeys, it puts "=" instead of "+" which stops the command working, you have to change it manually.
Paulverisor64
08-02-08, 06:37 PM
Awesome!
That is quite strange, but you found out what the culprit was. Thank you so much for hunting down the answer to my problem.
To give you a little background on the N52TE gamepad that I use; this is a gamepad that has a 14 key keyboard type layout, also includes a 4 direction D-Pad, and a couple thumb buttons. I've used this gamepad in the Battlefield 2 game which I've played, and it's convenience of button location, and good key reaction really improved my game. I now use this gamepad in every game I play. If anyone should ask, I could recommend either the new N52TE, or old N52 depending on the application you would use it for.
There are 3 seperate keystates (which means 3 times more keys than the default layout). I have layed out my speed and dive commands on one state. My different internal stations are layed out in the next keystate and my surface, periscope and directional keys are on the 3rd state.
I've not yet set up any macros for Silent Hunter III, but that functionality is also there if needed. Perhaps there might be a way to script something for times when I run the game unattended.
Thanks again for your help!
badwolf
08-02-08, 06:49 PM
Glad to help, Paulverisor64, thanks for the N52TE gamepad info.
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.