Vox problems

[Ack-Ack]

For some reason my vox has stopped working in game.  It works in Windows, applications like Skype and TeamSpeak and in other games like Defiance but for some reason, it no longer works with AH.  I've tried using the .resetv commands and no joy and I even deleted the voice settings configuration file hoping that would fix the problem but still no joy.  I'm using a Logitech G930 wireless headset and have been using it fine for the last month until this past Sunday when it just flat out stopped working.  I've even tried moving it to different USB slots (both on my machine and on a powered USB hub) but still no joy.

ack-ack

[Skuzzy]

What recording/mic device is shown as being used by the game (Options->Preferences->Game Sounds)?

When you press 'T' to record a transmission do you hear the beep?  If not then the game is not seeing the mic at all.  Usually means the device is not correctly set in the game.

If you do hear the beep, then the game recognizes the mic, and it becomes a network issue.

[Ack-Ack]

In AH it shows the Logitech G930 as the recording/mic device.  No, when I press "T" I don't hear the beep when I try and broadcast when I'm tuned to myself (to test if my mic is working) or when I broadcast to the channel I'm tuned to.  The really strange thing is last night is I tried broadcasting on the range channel and people heard me, so I thought it was working again but when I tried to broadcast to the channel I was tuned to, no one on that channel could hear me, only the people on range channel.  Yes, I did make sure that I have tuned channel (T) and range channel (F12) mapped properly in case I had accidentally remapped the tuned channel to F12.

Could a network issue prevent me from broadcasting on one channel only?

ack-ack

[Skuzzy]

Not likely.  All client VOX goes to one server and the server just sees who is supposed to get the VOX from you.

If you are not getting the beep, the client is not connected to the microphone or it is not able to reach the server.

Just a thought.  How about power cycling your router?  I doubt that is it.

You might also try renaming the "settings" folder and do not map anything and try it online with the standard mapping in place to see what happens.

[Ack-Ack]

Stumbled on a fix, a strange one but a fix nonetheless.  It apparently was a corrupted template or maybe latest version of CM changed how key inputs are sent out, but in any case changing the key in the .map file from upper case to lower case fixed it. 

ack-ack

[Skuzzy]

Ok, that is odd.  Must have forced a rewrite of the databases and corrected the anomaly.  Wonder what the cause was?

[Ack-Ack]

The template had started outputting "Shift+T" instead of "T" when I was pressing on the button.  My guess is AH was seeing the command as two (Shift+T) instead of a single command which is why when I remapped it in Control Manager to a lower case "t", it started to work. 

The more I think about it, I'm pretty sure when I installed the latest version of Control Manager it must have corrupted my .map file in someway.  I had downloaded and installed the latest CM just prior to the problems starting. 

ack-ack

[Skuzzy]

Good to hear you figured it out.  Something I need to keep in the support list as well.  Thanks Ack-Ack.

[ImADot]

What would happen in the case of someone mapping a key but having their "caps lock" key turned on? Would it map at a normal keypress or require shift+key?

[Ack-Ack]

What would happen in the case of someone mapping a key but having their "caps lock" key turned on? Would it map at a normal keypress or require shift+key?

That's how I originally programmed my .map file but for some reason after I updated to the latest Control Manager, it changed the key from "T" to "Shift+t".

ack-ack

[Drano]

That's how I originally programmed my .map file but for some reason after I updated to the latest Control Manager, it changed the key from "T" to "Shift+t".

ack-ack

Go figure I use the control manager and just looked and it's still Shift+t. <shrug>    just following the thread.