Well, you're doing all the heavy lifting - I'm just playing around with this stuff. Wish I had more time (and skill) to really help you.
BTW - While I was tweaking/merging my custom commands into the .csv files, I spotted a few other small things you might want to check. In voice_commands.csv, you've got a few instances where you have included both key commands and mouse commands for the same function (e.g., deploy decoys by key in ID #17, and with mouse in ID # 507, and next unit/previous unit in IDs 45/46 and 576/577, and (maybe) damage control in IDs 55 and 572) - not sure but that doesn't sound like a good idea. Also, I noticed that the same ID # 558 seems to be used for several different commands (e.g., Send range to TDC, Follow Nearest Warship (TM) and Normal Sweep (TM) ) not sure if that's intentional for some reason, but thought maybe not.
Have you noticed any slowdown, increased recognition problems or other issues as you've expanded the command set so radically? As part of my tweaking I'm winding up creating a somewhat slimmer command set - for example, other than from surface to about 70 feet, I don't think I really need to be able to command depth in 1-foot increments (something just seems a little wrong/too precise under the circumstances to hear myself ordering "make your depth 251 feet"), so I'm just doing 5-foot increments below roughly periscope depth - that gives me the chance to add commands to say it two ways (I also like saying "make your depth two five zero") and still pare down to fewer commands overall. Just wondering if there was any discernible upper limit this might eventually hit from a performance standpoint as the number of commands increases.
This is an amazing piece of work - really appreciate your contribution to the community here
