Command(s) not pressing any keys in game

This is a head scratcher for sure... Just tried the command myself and it pressed the Q key twice and then the 4 key.  It would be more understandable if all keys didn't go through, but the fact that you said it changed your view means the 4 key DID get through to BMS, but not the two Q keys.

For troubleshooting, please try other commands that would use the same menu (AWACS / Q key menus) and see if any others on page 2 (or others) are having the same issue.  Past that, I would suggest adjusting the time keys are held down and the time between keys through the menu.
(say, "Change Keypress Timings" to open the menu while BMS profile is active and initialized)

The default is 0.05 iirc and it may be too fast for your game to catch -- I'd suggest bringing that up to 0.07 or 0.08 for testing, for both settings.  I'll message you in Discord with this info, too.  I think it's just happening too fast.  If it's not that, it might be the way VoiceAttack is targeting the application to send keys.  The profile is distributed with "Active Window" set as default, but you could also try targeting the Falcon BMS.exe directly through the profile options menu in VoiceAttack, near the top left of the editor near the profile name).

Let me know if any of that works, and if not we'll see what else we can come up with to try.   

(from discord)

Quote

wheelchock wrote ...
'had to copy the COMMS section from the default Full key file to my profile. Something was hosed up but its ok now"

So the issue was in his bms keyfile after all.  Status changed to non-issue.

*It was noted that there is excessively long initialization time, possibly on older CPU's? ...

NOTE:
These first rounds of BETA Tests are for functionality alone.  I have always planned to optimize the speed and efficiency of the initialization procedure, and know several places where it can and will be improved.  After 8 months, I needed to get this into the public space so that bugs and other issues could be addressed while I continue work on optimization, performance, and polish.  Thanks to everyone for helping out with testing and being patient with these early iterations.  Cheers!