(My previous post is still in moderation, so this might not make sense yet. I'm pretty okay with having all the Oculus hardware hanging off a USB hub off the Stealth. Keeping devices off the Core allows for the maximum bandwidth to/from the video card, at least. There probably isn't a huge speed improvement to be had by plugging one device or another directly into the Stealth, versus into a hub or into the Core.
This is literally the only place suggesting that, though.)īecause everything's going into the single Intel bus in the Stealth, it also probably doesn't matter so much where in the hierarchy everything is. (There was this lone bit of speculation that "Fast back-to-back transaction" support was one of the things the Rift needs, and the Intel host in the Stealth supports that, but the chips in the Core don't. USB 2.0 is older, probably better tested, and probably runs as completely independent firmware from the 3.x firmware in the chip, so it's possible that's why the Sensors are fine when run in 2.0 mode. It sounds like this is a brand new chip and firmware ("G元522 integrates Genesys Logic self-developed USB 3.1 Gen 1 Super Speed transmitter/receiver physical layer (PHY) and USB 2.0 High-Speed PHY") being used in the Core, and the Rift and Sensors didn't exist when they were building it. It could still be a power issue, but I think it's more likely something's up with the USB chipsets in the Core, and they're just incompatible with the Rift and Sensors right now. We know the Rift does like most Intel chipsets (like the one in the Stealth).Īlso, I don't think I see random disconnections or dropouts like others have reported, and the Xbox Wireless Adapter, my SSD, and the ethernet on the Core all seem/seemed to be stable. We know there's a Cypress USB host in the Rift HMD, and that the Rift doesn't like some USB chipsets (but not specifically whether or not it likes the chips in the Core). We know there's a single Intel USB host in the Stealth, and two Genesys Logic in the Core, and the ethernet port is a USB device internally. Plugging the Sensors into USB 2.0 extension cables, and then directly into the Core, also makes the Sensors show up seemingly stable as USB 2.0 devices. (The Rift does not work on a USB 2.0 bus.) Plugging the Hawking UH214 USB 2.0 hub into the Core, and the Sensors into the Hawking, and the Sensors show up seemingly stable as USB 2.0 devices, just as they did when that hub was plugged into the Stealth. Plugging the Rift into the Anker makes it be not recognized just as if it was plugged into the Core directly. Plugging in my Anker USB 3.0 hub into the Core, and the Sensors into the Anker, makes the Sensors flake out just as if they were plugged into the Core directly. Also, I haven't tried any extended gameplay yet, but I've generally seen failures at this stage, so I'm fairly sure this follows. At least, I'm not convinced a different Core (RMA or otherwise) would work better/differently.
GENESYS LOGIC USB HUB DRIVER DRIVERS
I feel like it's possible drivers or firmware upgrades for the chipsets in the Core could fix it.
I did some light testing, and I feel like it's a USB chipset compatibility and/or bus bandwidth issue, not an issue with my particular Core hardware. I have the Rift HDMI plugged into the GTX 1080, and the Rift USB plugged into the left-side USB port on the laptop. Click to expand.Same, I describe that in my original May 2016 post.
0 kommentar(er)
