02-20-2017 01:58 PM
Hi, Ive had my Vive for about 3 days now and i'm fuming, Firstly ill start with the spec,
I5 6600k,16gb ram, 1070 GTX 8GB on a Asus Z170A.
Thats right, that motherboard is poping up alot on forums.
So my issue; first day it was very hard to get past setup as only one controller or the headset would stay synced, if two controllers were on headset wasnt.
Done some research= Inateck PCIe card,asus mobo usb chipsets not working well with the vive.
Put the card in, can get past setup and play the game for a little while (I have no idea how long I was in the matrix)
not long enough for £800!
So ive spend the next 2 days trying everything, I mean everything.
I have even emailed Asus about the z170a and its issues with the vive and this is what I got back.
"I am sorry to hear that you are facing issues with your Z170-A motherboard.
Based on the provided information I understand that the motherboard does not work with the HTC VIVE VR Headset."
Although the mobo is suppose to be VR ready beyond. hmmm
So i'm at a total loss.....of about £800.
Im fairly handy on comps but this has stumped me.
so Ive created a libary of crash reports.
In the last 3 I see the same message. and I would like to send these to someone to analyze please and im not 100% what im looking at but heres what stands out to me.
Sun Feb 19 2017 22:27:04.275 - lighthouse: LHR-403DFAE4 H: Trying to start tracking from base F8B3C567: Bootstrap failed because no IMU data was available
Sun Feb 19 2017 22:27:04.309 - lighthouse: LHR-403DFAE4 H: Trying to start tracking from base F8B3C567: Bootstrap failed because no IMU data was available
Sun Feb 19 2017 22:27:04.341 - lighthouse: LHR-403DFAE4 H: Trying to start tracking from base F8B3C567: Bootstrap failed because no IMU data was available
Sun Feb 19 2017 22:27:04.343 - IPCPipe(vrcompositor (2824)): Process disconnected.
Sun Feb 19 2017 22:27:04.343 - Process vrcompositor (2824) disconnected
Mon Feb 20 2017 17:55:53.362 - lighthouse: LHR-403DFAE4 H: Trying to start tracking from base 81F6D135: Bootstrap failed because no IMU data was available
Mon Feb 20 2017 17:55:53.395 - lighthouse: LHR-403DFAE4 H: Trying to start tracking from base 81F6D135: Bootstrap failed because no IMU data was available
Mon Feb 20 2017 17:55:53.429 - lighthouse: LHR-403DFAE4 H: Trying to start tracking from base 81F6D135: Bootstrap failed because no IMU data was available
Mon Feb 20 2017 17:55:53.444 - IPCPipe(vrdashboard (6260)): Process disconnected.
Mon Feb 20 2017 17:55:53.444 - Process vrdashboard (6260) disconnected
Mon Feb 20 2017 17:55:53.451 - Sending Quit event to process vrcompositor (1496)
So my question is, is it the vive or is it the motherboard. And if im using the inateck card should it rule out that isses with the motherboard ?
PLEASE HELP ME the vive is an amazing piece of kit and ive built this pc to run it, if its the wrong mobo ill change it but I have to know for sure!
02-21-2017 11:28 AM
Do you perchance have the Vive's camera enabled in the SteamVR settings? If so, have you tried disabling it or reducing the refresh rate? It could potentially be a data throughput issue of the USB connection for some reason, and if so, this should help. As for your test with one base station, did the issue occur with both base stations or...?
Past this, I'd recommend either trying to setup the Vive in another room completely (or even another house/office/etc) to try and isolate it against being some form of interference. It may also be worth trying it on another computer, if you've a friend with a VR ready PC. Based on the info you provided, I don't think it's a problem with the Vive hardware components.
While it's possible it could be the something with the motherboard, but I'm not 100% convinced and will investigate on our side to see if there's any compatibility issues we've identified with your motherboard model. Issues like this are traditionally caused by enviromental interference or data throughput issues on the USB port (which should have been resolved using the Inateck PCIe card).
02-21-2017 12:14 PM - edited 02-21-2017 12:19 PM
thanks I have the tripods coming tomorrow so will set up in another room.
Camera is off as defult I think, I havnt put it on tbh.
So as of now, if you use and MB port its grey straight away, switch to the PCIe card and it lasts 5-8 mins.
02-22-2017 12:43 PM
Today I recived the tripod, set everything up in bigger room, the living room. There were no improvments at all. but I did notice that when I turn my head from side to side, from each light house it seemed like that were a slight hitch or delay when looking left to right, it happens right in the middle. Could be nothing but it made me think, could it be when passing over from left to right and the other light house takes over it not working how it should, gets confused and greys out.
I need help really soon before this drives me crazy.
02-22-2017 04:21 PM
I'll need to do a little research to confirm, but my understanding is that both base stations are used in tandem, so theoretically that behavior (passing control from one base station to the other) shouldn't be occuring.
I wonder if there's an issue with the Vive's USB port. If you look under the cover (where the 3-in-1 cable connects to the headset), there's two USB ports under there. Try connecting the USB portion of the 3-in-1 cable to the other USB port and see if that changes anything. If so, the issue could be a loose or otherwise faulty USB port.
The issue could possibly be related to interference still, and the next step to try and verify if interference is the root cause would be testing with the Vive setup in a completely different place (friend's house, an office, etc). It may be worth shutting off every device in the house not related to Vive that sends a wireless signal, and disabling Wi-Fi on your PC as well (not just disconnecting, but disabling the Wi-Fi adapter temporarily). If either of these help, it indicates there's definitely some wireless interference degrading the IR tracking.
Another possible cause is some form of software issue or conflict occuring with Windows or other software on your computer. Have you attempted to disable or uninstall any anti-virus or firewalls? I know you've tried uninstalling some other software, so I think the next test aside from making sure firewalls/anti-viruses are not interferring would be testing on another PC. However, if the Vive works without this issue on another PC, it would only tell us that something in your PC's environment is resulting in the issue (or your play space, if you test with a PC in another location) but doesn't bring us closer to being able to provide a fix since it doesn't nail down the exact root cause.
Some additional questions below:
Lastly, I'm sending you a PM with my email address as I'd like to take a deeper look into your system report to see if that reveals any clues. Let me know if you'd like some more detailed steps on anything I mentioned.
03-10-2017 12:39 PM
Just an update.
So after the last 2 weeks I've had the vive replaced under warrenty.
First day was great played for 4 hours with not 1 issue,
2nd day it greyed out once after rebooting headset it continued to work for a few more hours.
3rd day it would grey out quite often.
After reading some advice I went into the bios and set it normal opposed to performace, no change there.
Today I did a fresh install of windows to make sure that no software previously installed was affecting it. after the fresh install the headset greyed out within 5 mins.
So! if its not the vive
and not conflicting software
It can only be two things, Hardware or the enviorment.
I have a friend coming round next week who also has a vive with the Z170m plus mobo in it, so that will rule out the enviroment. (if it works)
After talking with Vive support agent from the uk, he said that the motherboard I have could still affect the vive even though im plugged into the inateck PCIe card, is this true? Can anyone confirm?
Does anyone even know what mobos work perfectly fine with the vive?
I dont want to spend another £200 on a motherboard based on a could/maybe.
06-19-2017 01:30 PM
I've bought a recoomended Intek USB card, after spending 24€, problem is stil unsolved.
The weird things are:
1. It was working smoothly for months.
2. Whenever I install in a new USB the problem takes about 1 hour to appear for the 1st time.
3. It always appear as a small blind spot. Looking at a specific point it greys out the whole screen. But each time the spot is different, so it is not due to reflections in the enviroment (the environment hasn't changed lately, only room temperature is about 5 Celsius degrees higher). If I keep looking close to the spot the blind spot gets a blind cone bigger and bigger.
4. Most times the blind direction is low, under horizon. In the end, half a sphere in my environment are untracked directions, even if I look directly up to a lighthouse.
5. I have observed at the beginning, not only looking at a direction is enough, also position of controllers has something to do. At the beginning, I have tried looking at the blind direction and moving trackers around. Sometimes if I put both trakers on on side instead of one each side of the headset, picture returns. But the phenomena goes progresively worse and worse. After a couple of minutes it is unsuable.
06-19-2017 01:39 PM
It sounds like your issue is related to tracking, more so than software. Certain places cause grey-outs (loss of tracking) but only those places?
Have you tried setting it up in a different place to test? Maybe in a different room?
06-19-2017 09:17 PM
Hi my friend in misfortune.
I've Exactly such issue!
Let's keep communication. If any idea or troubleshoot - we will talk to each other.
12-18-2017 11:36 PM
I have a very similar issue. Works fine for 1-2hours then grey screen if I move my head one way. Always the same direction. But its facing away from my lightboxes, so both should be able to see me. When I'm looking at just one it seems to work OK ? Has only started in the last few weeks, as its got HOT in Australia (40+degrees) but I'm inside with the air con on. I've turned off all air con, fans to check that, but no help
12-19-2017 10:21 AM
I sent you a PM.