We all have to start somewhere! :88)

Thanks!!! :salute:

:DL

* The 'main' one is in /data/cfg/controls.cfg. The others are stored in mod folders and such.

* No version in my docs.

* Yes tried starting a new carrier.

now even more curious other edits got put back in the config as well as camera changes.

So I just copy / pasted my original controls.cfg (backup) and the camera and other commands are back to where they were so thats the file :yep:

It seems as if the dive and surface keys are bound to some internal code and cannot be changed.

Modding Mod's
 

Hi Mates,
Now I don't use RFB, but if RFB has a Commands.cfg, That is overwriting SH4 commands.cfg, in JSGME. You will need to disable RFB, Change Commands there, & renable RFB to see changes.
Otherwise; as Danlisa suggested, make your own Mod by creating,
Mod name file, Example: (.cfg changes) in that file create a Data folder. In the Data folder, create Commands.cfg folder with changes you want. When you install your new Mod it will overwrite any previous changes introduced by other JSGME changes.

Danlisa;

See post #14 :salute:

Before I have to curse you for making me install SH4, how do yo know that Binary Key designations you have in your OP are correct for the CTRL + Key combinations? As far as I can see they are for the single Key orders i.e S = Surface & D = Dive

Work around
 

Steamy
Workaround; Use Depth meter to set/preset dive depth limit. All Crash Dive is, is crush depth + flank speed. Setting PD., Will prevent broaching, coming up in TC.

Try this - http://rapidshare.com/files/276924511/Commands_Mod.rar

Extract and check folder structure, ad to MODS folder and enable.

I disabled the default S & D keys and left only the CTRL combos.

:hmmm: That would be my question. Also, I don't remember what the "C" stands for in that line ... but it's worth investigating. Because the entire line must reflect your new binding.

However, if SW tested the file by deleting the command(s), and even that didn't work ... well, perhaps he needs to make the exact same change(s) to every version on the file on his computer. But I don't suggest deleting any command(s) ... it's better to just disable the command(s) with a semicolon.

This disabled the default s and d keys thank you, however the ctrl comobos dont work.

I tried correcting the syntax from 'CTRL D' to 'Ctrl+D' still doesent work.

But its a step in the right direction thanks.

All are very simply ... look above and below:

C - it's Crew Command (... ,C, ...);
c - it's additional key Ctrl (... ,c, ...) or (... ,Cc, ...);
s - it's additional key Shift (... ,s, ...) or (... ,Cs, ...);
R - to keep key of pressed (... ,R, ...) and so on ...

It's only comments for you ...

:har: Something stupidly simple, I had to forget that.

Thanks for the help everyone.

Unfortunatly I'm back at work now. Ill give this edit a try when I get home.

Ill let you know.

Thanks again.

This syntax does not work. I also tried

The D & S keys are still disabled but the ctrl+ does not work.

:rotfl:
The order of the specified symbols is not important ...
...
Syntax is absolutely correct!
...
You have other problems... may be at you keys are duplicated ... may be something another ...
may be you have not enough numbers of commands ... in Commands.cfg ... look:
"[Commands]
CommandsNb=600
MaxKeyCommandsNb=190; Keys number shoud be smaller than this value (in order to accelerate the loading)"

Again Im at work but Ill check it tonight...

I do know that the changes were applied as the fire torpedo button is back to the 'enter' key again :oops:

That I can fix :rotfl:

I dont think the keys are duplicated as S & D are the default keys. I just want to change that to ctrl+s like I did with the fire torpedo thing.