AKRocco
-
Posts
8 -
Joined
-
Last visited
Single Status Update
-
Hey man did you get your 1-4 check your display cable error fixed? This seems to be happening across the board with windows mixed reality. My odyssey is doing the same. Also when you unplug your headset and re-plug it in is there an audible sound like you've plugged in a usb device? Sounds strange but mine becomes recognized but without a sound. Whenever I have got it working there's been that you just plugged in a usb device windows sound. I also had some luck uninstalling my usb serial bus controllers in device manager and then restarting to have them reinstall. After the restart I plugged back in to a 3.1 and it worked....until the next restart! Have you also tried command prompt as admin and then sfc /scannow ?
-
No I never did get my first headset working. The replacement they sent has worked so it was definitely a faulty headset for me. Unfortunately the 1.4 error is not very specific and there's a hundred different things that could cause it.
I did have an issue with the usbs on the mb itself, they were causing stutters in tracking and audio, and I would constantly hear the connect/disconnect sounds. Didn't matter which usb port I used, 2.0, 3.0, 3.1, type C, they all did it. Fix for me was using a powered USB hub. No idea why it would work better than direct but it does for me.
I haven't tried that command prompt command. I do know that there are a few things that register in the device manager for a headset. For the G2 it comes up as a display, a WMR device and under the usb for tracking. If you haven't already I would take a look in there and see which part isn't coming up.
Hope you get your headset running!
-
-