Band is the one that made me adopt it.

I couldn't do without GameCommander now. I use it as Band describes; it is best to use a push button instead of having it continually on. When I installed it first I had the flu, and sometimes during fits of coughing my gear would retract at the worst possible moment.

Like Band, I haven't noticed warping either.
I use GameCommander for pretty much of everything that doesn't go on my stick and throttle buttons:
- quick buffer-based 6 calls on channel 4 for non RW-capable squaddies and other text responses like "busy", "rgr" and "wtg" (I say "way to go 1" for channel 1, "way to go 2" for channel 2 etc.). I even programmed voice commands to change channel 5 without touching the keyboard.
("tune rogerwilco" will type .radio 5 in the buffer and I programmed a voice command for each digit)
- plane controls like hook, dive flaps (I only say "Dive"), engine, damage display, fuel cell selector, WEP, doors
- game controls like ground clutter ("clutter"), squad highlighting, exernal/internal views in buffs, autopilot ("climb", "level", "angle"), .ef, icon setting
It is best to keep the voice commands short. There are some cases where two words sound too similar, so I change one; for example I could not get "clipboard" to display the clipboard, so I programmed "menu" instead.
It still happens that GC doesn't recognize correctly my commands (when I'm excited for example

), but not often enough for me to ditch the program.
As for the views, I use GC only to switch between gunner, bombsight and cockpit positions and for toggling external/internal view in a buff.
------------------
DrSoya
308 (Polish) Squadron "City of Cracow" RAF
Part of the
Northolt Wing (First Polish Fighter Wing)