• Logitech AK5370 and the XB360 controller - An Epic Tale of Microsoft's... Dumb.
    10 replies, posted
Alright, so, I decided that one day flying helicopters in ArmA 2 with my Xbox 360 controller might be fun. I plug it in, configure it, it works, happy joy joy. So I hop on vent and tell Foxton to get his ass in here, since I was hosting Domination and getting buttraped. Boy was I in for a surprise. I hear from Foxton that my microphone is broken, and that it's emitting some weird alien fuzzy bullshit noise. I do some investigation, and he's correct - every time I try to record anything, either via vent's test function or through sound recorder, I hear a horrible garbled mess. So I spent about five hours of my life doing the following: Installing sound drivers Uninstalling sound drivers Dicking with sound settings Using the Help and Support center on windows (to no avail, there's NOTHING in there except for speech recognition) Finally googling the problem Pressing the "FUCK IT" button and system restored to yesterday. So apparently, the problem lies within the Xbox360 controller. If you'll look at your controller (if you have one), you'll notice an Xbox Live headseat jack on it, between the two grips. That [b]ASSFUCK[/b] is responsible for this mess. The gist of the problem is that Microsoft's drivers (The plug and play stuff that windows installs when it detects a new USB device. Driver is used for lack of a better term.) for that controller add support for the headseat jack on the controller, which conflicts with the AK5370. There is [b]no[/b] known fix for this problem short of a system restore should you encounter it, at least from what I could see, so here's my message to you: [highlight][b]IF YOU ARE USING A LOGITECH AK5370 USB DESKTOP MICROPHONE, DO NOT PLUG IN AN XBOX360 CONTROLLER[/b][/highlight]
360 controller is plug and play with windows (well they are microsoft so that is why), why did you need to get drivers you screwed yourself over. i didn't need any additional drivers for my 360 controller that aren't already featured in windows so i don't know how you fucked that up
Not only that, but you should disable the 360 controller's audio devices in Device Manager. Besides showing up as a USB HID controller, it also doubles as a USB sound card, and tries to take over unless you disable it in Device Manager.
If you have a 360 headset try using it in the controller and you could use that.
[QUOTE=nerdygamer;16770494]If you have a 360 headset try using it in the controller and you could use that.[/QUOTE] That's a great idea, I never thought of that. I have a bluetooth headset because i hate cords dragging across my keyboard, mouse, and tickling my arms.
If you have multiple sound devices, open the sound control panel and set the default sound playback and sound recording devices to the sound card in the PC instead of the controller.
Logitech and Microsoft do have some weird drivers conflicts. Back when I was using Vista I received a wireless headset from Microsoft (looks like the 360 one, but is for the PC). The thing is, whenever I plugged it in, my G5 mouse stopped working at all. It was very strange. I had to wait til the drivers were updated from Microsoft so that it stopped doing that.
[QUOTE=Rusty100;16770053]360 controller is plug and play with windows (well they are microsoft so that is why), why did you need to get drivers you screwed yourself over. i didn't need any additional drivers for my 360 controller that aren't already featured in windows so i don't know how you fucked that up[/QUOTE] I didn't download any specific drivers, it's the crap that windows installs when you put in a plug and play device. I used the term driver for lack of a better one. [editline]12:34AM[/editline] [QUOTE=GiGaBiTe;16771452]If you have multiple sound devices, open the sound control panel and set the default sound playback and sound recording devices to the sound card in the PC instead of the controller.[/QUOTE] I did that, it still had that problem. I'm using a nifty logitech PS2 style gamepad now, although I'm going to miss analog triggers. [editline]12:37AM[/editline] [QUOTE=Pixel Heart;16770431]Not only that, but you should disable the 360 controller's audio devices in Device Manager. Besides showing up as a USB HID controller, it also doubles as a USB sound card, and tries to take over unless you disable it in Device Manager.[/QUOTE] That hadn't occurred to me. However, even after unplugging and making sure the device was gone from the device manager, the problem was still there, so I'm not sure if it would've helped.
[QUOTE=StickyNade;16784458] I'm using a nifty logitech PS2 style gamepad now, although I'm going to miss analog triggers. [/QUOTE] logitech precision?
I think XInput makes it easier for devs to fuck up and override direct sound's settings for mic input by lending them direct access to the XB controller's headset's GUID. Perhaps this is a problem with the game you're playing? Have you tried dicking around in Audacity?
Sorry, you need to Log In to post a reply to this thread.