![]() |
![]() |
|||
![]() |
||||
![]() |
||||
Frequently Asked Forum Questions | ![]() |
|||
![]() |
||||
![]() |
![]() |
|||
![]() | ||||
![]() | ||||
Search Older Posts on This Forum: Posts on Current Forum | Archived Posts | ||||
![]() | ||||
![]() | ||||
![]() | ||||
![]() | ||||
![]() | ||||
![]() |
: I can understand that Kinect wouldn't want to be having to try and identify
: commands in amongst your multiplayer babble. But this would also imply
: that in multiplayer, voice commands will no longer work if you're using a
: headset.
Oh, no. Maybe I didn't really state things clearly.
I use my headset in Battlefield 4, and voice command still work. What I mean was that, I think with the headset plugged in, Kinect uses that as the input microphone, and the microphone on the actual Kinect sensor itself is deactivated. But voice commands are still processed and work.
This might not be true whatsoever; I honestly have no idea. But as I said, when I occasionally stop playing and forget to unplug my headset from my controller and try to use voice commands for navigation, the Kinect seems to have a much more difficult time hearing my commands. I had assumed this was because it was using the headset microphone, rather than the one on the Kinect sensor. That could be totally wrong, it's just been my experience.