[TEC] Tutorial for mapping commands to keys?

[DirtyHarry3033]

Glad you got it working now!

Actually after I made that last post, I got what I think was the exact same error you mentioned when I shut down SetKeys. I had made several "nested" folders and put Commands.cfg at the bottom level, opened it, made a change and saved, to see if maybe the depth of folders had something to do with it. Worked fine, so I deleted the folders I'd set up. Then, when I quit SetKeys it popped up an error dialog complaining about a missing path, was like 8 or 10 lines long. Bet it was the same error you saw

So, I'm wondering if you accidentally deleted something SetKeys expected to see, before you saved?

BTW, my experience is that SetKeys makes the Commands_en.bak when you save. It's a backup of the original file in case your mods don't work. You can just rename it and undo your changes. Shouldn't be necessary for you to create it yourself to make SetKeys save your changes!

OK, now that you've got it working all you need to do is open your edited copy in one text editor, and your live file in another. Then for each command you mapped to a key, copy the new "Key0=" line from the edited file, and paste it into the live file as the last line for the relevant command. Then save, and you should be able to use the new keymap to execute the command!

One thing to keep in mind is, if you add a mod that affects Commands.cfg it will blow away all your hard work. I always replace the mod's Commands.cfg with my custom one before installing the mod. That way I can keep my keymap! If there are newly-mapped keys in the mod that I want, I add them to my Commands.cfg before I do that, that way I get the best of both worlds.

Good luck, hope you get it working like you want - that voice recog absolutely rules! I use Shoot! and won't think of playing without it

DH

[panthercules]

I've taken to creating my own JSGME-ready mods with just my tweaked config files in them (e.g., menu_1024_768.ini, menu.txt, cameras.dat, etc. - and now commands.cfg) - that way, I can install and uninstall them just like any other mod, which has saved me a tremendous amount of time during testing and saved me from losing any of the work when I install or uninstall other mods. Just have to keep track (which I usually do in a readme or the title of my mod folder) of which mods formed the basis/starting point for my tweaks - so I can distinguish the stock 1.3-based ones from the RFB-based ones, for example. Things can get so confusing, but this has really helped me keep things straight while I'm doing all this experimenting and other folks' mods are still getting updated.

I'm not sure what the problem with the .bak files was, but for some reason SetKeys didn't create its own .bak copy but worked as soon as I created one for it to detect/use. In any event, it seems to be working fine now, and I've successfully added mapped keys to about 6 or 7 of my most-wanted commands, so I'm looking forward to getting them loaded into the speech recognition files and using them on patrol.

It's been a while since I used Shoot (back in my heavy SH3 days) - does it allow you to assign multiple spoken commands to the same game action/key output? (i.e., can you set it up so it will recognize 3 different ways to give the "dive" command, or is it limited to a one-to-one arrangement?) I never really thought about doing that when I was using it, so I don't think I ever actually tested that, but I had the impression for some reason that you couldn't tell it to output the same letter if it heard "this" or "that". Maybe I was just thinking too narrowly at the time.

[DirtyHarry3033]

Shoot! lets you set up as many statements for a command as you want. Here's my commands for the attack scope for example:

-------------------------------------------------------------------------
<command name="Go To Attack Periscope 1" phrase="attack scope">
<key type="F4"/>
</command>
<command name="Go To Attack Periscope 2" phrase="attack periscope">
<key type="F4"/>
</command>
<command name="Go To Attack Periscope 3" phrase="go to attack scope">
<key type="F4"/>
</command>
<command name="Go To Attack Periscope 4" phrase="go to attack periscope">
<key type="F4"/>
</command>
<command name="Go To Attack Periscope 5" phrase="scope">
<key type="F4"/>
</command>
<command name="Go To Attack Periscope 6" phrase="periscope">
<key type="F4"/>
</command>
<command name="Go To Attack Periscope 7" phrase="go to periscope">
<key type="F4"/>
</command>
<command name="Go To Attack Periscope " phrase="go to scope">
<key type="F4"/>
-------------------------------------------------------------------------

So that's 8 different ways to say it, you could have 80 if you wanted

If you're gonna use Shoot, you might also want to get the profile editor here:

http://clans.gameclubcentral.com/shoot/

Makes it a lot easier to write a profile, especially if you're starting from scratch instead of modifying an existing one!

DH

[Digital_Trucker]

Yep, not only can you make multiple statements for a command, you can make multiple commands for a statement (with pausing to allow for actions to happen). For instance, you can set one statement to issue a crash dive command, wait for a specified number of milliseconds, then rudder hard to port/starboard, wait again, deploy decoys, and go silent. The only problem with this kind of command set is that I don't think Shoot will accept any more commands until it is done with the group.

DH is right about the editor, too. I wouldn't want to make an SH profile without it (that's why I wrote it to begin with, I got tired of trying to code commands ).

The one thing Shoot doesn't do that would really be helpful is mouse movement/actions. Given all the hassle that you would have to go through for different screen resolutions, I can understand why that function is not there, though.