I've started to figure out the basics of setting up a profile using the editor, but I have one odd problem that I cannot solve.

Let's say I have my CapsLock key set as a PTT toggle, and I have three commands: medic, incoming, and sorry. I use CapsLock to toggle on and give my first command (medic) - nothing happens. I say 'medic' again, and I get the proper response. Now if I say 'incoming', Shoot responds with my second 'medic' call. If I then say 'sorry', I get the 'incoming' call, and so on. The program is always one call behind what I actually say. Suggestions?

I've run into similar problems before with particular games (Jane's F-15 for one) and the solution for me was to give Shoot a higher execution priority than the game. Even then, sometimes the problem came back. When that happened, I just terminated Shoot and started it up again.

would be nice if Shoot had a reset function rather than having to restart it. I have the same problem and its game independent. Seems to be more just a problem with sync.

Could a function be added to Shoot (maybe voice activated) that would clear the output buffer and re-sync the commands?

grumpyold wrote:

would be nice if Shoot had a reset function rather than having to restart it. I have the same problem and its game independent. Seems to be more just a problem with sync. Could a function be added to Shoot (maybe voice activated) that would clear the output buffer and re-sync the commands?

I'm fairly sure the author of shoot could implement a reset function. The problem would be that you'd still have to exit whatever game and activate the reset function. I don't think a voice activated reset would work since the program is already having problems executing commands in a timely manner by the time that you want to execute the reset.

It's possible that an application could be written to kill shoot and restart it (possibly with the same profile, if I can determine a way to figure out what profile is being used programatically). By creating a shortcut with a hotkey assigned, the app could be run by a keyboard command. The problem with that approach is that some games muck up keyboard access so that hotkeys to shortcuts don't function because the game traps all keyboard input

So, to make a long story even longer, without some work by the author of the program, I don't think there's a simple way around it.

If commands are out of sync, the reset command would just have to be repeated until it 'takes'. Then everything would work normally again...in theory.

I can't get hotkeys to work with my shortcut. I'm running VISTA64 and assigned a hotkey to the shortcut pointing to my app. I can click on the shortcut and the app runs fine, but the hotkey has no affect.

Does the hotkey work when you are just at the desktop and not work when in game, or does it not work at all?

Worked once or twice then stopped altogether until I placed it on the task bar (not desktop). Now it activates using the windows key and a numeric key (win+5).
The number represents it position on the task bar.

Must be a Vista thing...

Now, annoyingly, when Shoot trys to reset, it minimizes IL2. Inconvenient, but I can live with that. At least IL2 comes right back up when I click on it in the task bar.

I tried this scenario in the Windows 7 beta, seems to work there, maybe it is just Vista?

I've got the same problem with Shoot 1.6.4 on XP 32 and Vista 64, so it's not only a problem with Vista.

I got the impression, all is well until the SR cannot understand a command. After that all commands seem to be delayed by the number of the commands that the SR engine could not understand. But I am not sure.

Edit: After some more testing, I can finally reproduce the problem: the problem occurs when you give a command to Shoot while it's still executing another command. So as long as you wait for Shoot until it finishes executing a command before you give it the next one, you should do fine.
But this is obviously a bug and I hope it gets fixed soon.