I have a $650 door stop.Īll of the USB ports work perfectly fine with my Quest 2 btw. I'm all out of options and ideas to try now, if anyone has any suggestions? At this point I'm pretty cheesed off with it. Also, sometimes when I unplug and plug the headset into a USB port it crashes my PC. As soon as I plug in and power up the headset Windows Mixed Reality automatically starts up, so it knows the headset is there. It seems to be a USB issue of some kind, or the headset is faulty. I've tried them all, including every USB port already on my PC and I still get the cross next to the USB 3.0+ and "Can't run mixed reality" message. I've bought and tried both a powered USB 3.0 hub and a PCI-E USB 3.0 expansion card, that includes a USB type C connection. ![]() It's exactly the same hardware and USB ports as when I first got the G2 and it worked.ĭoing an internet search some people say using a powered USB hub or a USB PCI-E expansion card fixed their issues. I tried uninstalling and reinstalling Windows mixed reality again, a couple of times, but now when it runs through the initial setup and detects my hardware I get a tick mark next to everything except for USB 3.0+, that has a cross next to it and there's a message, "Can't run mixed reality". I had it running for a few days in 60Hz mode, (it would no longer run in 90Hz mode at all), but I started getting the black screen again even in 60Hz until eventually it stopped working completely. People seem to haver fewer issues with those. I'm just curious, is anyone else running an AMD card with their G2 and experiencing similar issues?Īs soon as graphics cards are back in stock I want to upgrade to Nvidia. At least then I'll know the headset isn't defective. I'm thinking of lending it to a friend who's running an Nvidia 3060 Ti to see if it runs fine for him. I'm hoping AMD will quickly release another update that will fix it and my headset hasn't suddenly gone faulty. I'm wondering if the issue has returned with the latest AMD driver. A quick internet search revealed other people with the black screen issue over the last couple of months (no mention of the snowy specs) and they all seemed to be using AMD GPUs but an AMD update seemed to have fixed it looking at the notes for one of their past driver updates. At first I wondered if it was the DCS update but I'm also getting a black screen in MSFS2020 and the snowy interference even when I'm just in the Windows mixed reality house or Steam VR lodge. It only started this week after the latest DCS patch but also about the same time I installed an AMD GPU driver update for my 5700 XT. I never used to see that, the picture used to be perfectly clear. I've also noticed that when I do have a display I can see tiny snowy specs of light and horizontal lines, like a snowy tv interference but very subtle. Sometimes it'll come back on again, but then randomly go black again but sometimes it just won't come on at all. I can still see DCS running on the desktop and responding to movements from the headset and I can still hear sound but no image at all inside the headset. There's no light coming from the lenses at all, like the screen is completely turned off. SteamVR easily gets confused.Īfter I tried things like this in various different ways, at some point I stopped getting the 125 error.Īll that said, I think the real solution is to wait for a version of Steam VR that is consumer ready.After working fine until now, my G2 has started to randomly go black inside the headset. Waiting for an unreasonably long time (way after Windows has completed showing driver install messages), Just wait 10 minutes or so. SteamVR > Settings > Developer > Remove All SteamVR USB Devices ![]() unplugging all cables from the link box. A fresh start (in an order like this one): Apparently this only applies to Vive Pre, but it seemed to get me out of a 125 once. If you got this after a failed firmware install, maybe it might be worth doing a manual firmware install. Plugging my mouse into a USB 3.0 port directly instead of via my keyboard (the Vive doesn't seem to like other USB-hub-like devices being present.) Switching to a USB 3.0 port, in stead of a 3.1 port. I had this issue come up several times in different ways, and I found no consistent answer for how to solve it, but I can list a few of things I did before it started working again. Some people on the internet even replaced their Vive to solve the problem.īut I think it's a case of dodgy drivers. Looking at the posts here in this thread, and comparing it with my own experience, the 125 error doesn't really say anything specific about the issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |