Setkeys works with SH4 here's how

[darkfin]

I've been using setkeys with sh4 and it seems to work. Run setkeys. File, open. Browse to your sh4 installation folder, dat, cfg folder. You won't see anything yet. In the area where it says filename type *.cfg or commands.cfg and there you have it. Set your keys to whatever works. Setkeys is a great program and hasn't been sunk yet. There are a lot of escort commands in there.

Jim

[DirtyHarry3033]

Thanks for the tip, that's gonna be useful! I'm trying to get the Shoot! voice recognition to work with SH4 by replacing Commands.cfg with the SH3 command_en.cfg that came with the SH3 Shoot! profile.

It works but also seems to break certain SH4 key commands. For example, hitting "M" to open Message window no longer works.

Hopefully I'll be able to use SetKeys to edit the original SH4 Commands.cfg and assign keystrokes for the commands I want to send with Shoot!, and not break existing keys. That'll save me a lot of time, was gonna copy/paste the needed stuff from the SH3 Command_en.cfg

[peewee]

Originally Posted by DirtyHarry3033

It works but also seems to break certain SH4 key commands. For example, hitting "M" to open Message window no longer works.

This may be the reason

"If you have a file named set.keys in your current directory, then SeqEd, LineUp, GelEnter, and GelAssemble only respond to the keys that you have defined in it; all other keys will be silent. In the SeqLab sequence editor, keys that are not defined in the set.keys file retain their normal definition"

[DirtyHarry3033]

Originally Posted by peewee

This may be the reason

"If you have a file named set.keys in your current directory, then SeqEd, LineUp, GelEnter, and GelAssemble only respond to the keys that you have defined in it; all other keys will be silent. In the SeqLab sequence editor, keys that are not defined in the set.keys file retain their normal definition"

Thanks, but that's a totally different program you're looking at, it's part of a package from the National Institute of Health:

"The GCG Wisconsin Package is an integrated package of over 130 programs that allows you to manipulate and analyze nucleic acid and protein sequences. Scientists from all over the world have collaborated to develop and refine the Wisconsin Package, making it a flexible tool with which to analyze your sequence data."



The one Darkfin refers to is SetKeys for SH3, found here:

http://www.subsim.com/subsim_files/p...SetKey1_11.rar

It allows you to edit the Command_en.cfg in SH3 with a GUI interface, and apparently also works with Command.cfg in SH4.

My problem with the "broken keys" was because I copied the SH3 command_en.cfg file that had been modified to add keystrokes to commands only accessible thru icons, to SH4. There are some conflicts apparently.

SetKeys will allow me to edit the original Command.cfg from SH4 and add keystrokes to the commands I need - hopefully avoiding conflicts and "broken" keys.

[eweber]

I also use SetKey 1.3 designed for SH3. You can use it for SH4 but be careful! When you save the file, SetKey creates a bak file. you need to copy the heading from the backup file and paste it into the new cfg file:



[Contexts]
ContextsNb=13; max contexts nb is 16
Context0=None; default - should not be changed
Context1=Game
Context2=Pause
Context3=Spectator
Context4=Console
Context5=Museum
Context6=Effects
Context7=Final
Context8=Edit
Context9=Replay
Context10=ModalMsg
Context11=AdversarialMode
Context12=DeathEffect

[Commands]
CommandsNb=600
MaxKeyCommandsNb=170; Keys number shoud be smaller than this value (in order to accelerate the loading)

;Name = command name -> will be translated in command index
;Ctxt = command context(s) as indexes -> see [Contexts] section
;MnID = menu item id associated with this command
;Str = string id (from en_menu.txt) associated with this command
;KeyX = an entry containing <key_code>,<flags chars>,<help text id>; flags chars could be C=executed by the crew, R=repeat key, c=with control, s=with shift, m=only when mouse is captured (enabled), n=only when mouse is not captured (enabled)
;Page = <page_id>,<title_id>; associated page (only for user commands) and a title if is necessary

_________

If you don't the SH4 features won't work properly....

ew

[SteamWake]

woops sorry opened the wrong door.

and I in the Modding forum ?

[Dodger01]

Having become addicted to barking out commands using Shoot in SH3, I knew there was no way I'd be able to play SH4 without it, so I started using SetKeys to reconfigure command.cfg. I found early that simply copying the commands_en.cfg from SH3 didn't work.

Unfortunately, as eweber said, simply using the SetKeys edited commands.cfg breaks some features in SH4. In my case, the radio and gramophone wouldn't work at all, although I was able to use some voice commands to get the gramophone to start and stop without displaying the interface. It took some long testing to figure out that it was indeed SetKeys causing this.

From that point on I backed up commands.cfg before using SetKeys, then simply cut and pasted the edited commands into the back-up copy and used THAT one with SH4. I never thought of simply replacing the header, but I'll try that next time.

At this stage I simply cannot imagine not using voice commands. Standing on the bridge scanning the horizon it's a simple matter of shouting, "Set course to my mark," when I want to change course, or "Sound general quarters!" when going into battle or just to keep the boys on their toes!