Jump to content
 
jrmichel2000

Vive Pro + Wireless adapter: screen goes dark

Recommended Posts

Don't hold your breath for a fix, I've been part of a thread on this support board for well over a year now with similar issues ( see 'Vive wireless adapter disconnects after a few minutes' ) and not a peep of help

I upgraded my CPU and motherboard with no luck ... I'm out of ideas but going back to a cable is not going to happen so I'm stuck with the annoyance

 

@VibrantNebula @jagibson

Share this post


Link to post
Share on other sites
On 12/3/2019 at 4:44 PM, Krogenit said:

I tried with default 3.7 Ghz for CPU and tried playing without MSI Afterburner/GPU overclock. No difference.

How about RAM? Are you overclocking your RAM as well? If you are, try not to OC RAM.

Share this post


Link to post
Share on other sites
12 hours ago, MB Geek said:

Don't hold your breath for a fix, I've been part of a thread on this support board for well over a year now with similar issues ( see 'Vive wireless adapter disconnects after a few minutes' ) and not a peep of help

I upgraded my CPU and motherboard with no luck ... I'm out of ideas but going back to a cable is not going to happen so I'm stuck with the annoyance

 

@VibrantNebula @jagibson

I was thinking about upgrading, but something stopped me and yes that's bad idea. I bought second adapter, but it also doen't works, so i will return second one. Currently i'm trying to get help from DisplayLink forum. Maybe that happens because bad USB drivers in adapter or hardware issues, like power managment.

I returned back to wired, but i really want to play outside with adapter. That's awesome when it works.

doggi1.PNG.dec7c42fccf738ab2d6376fbe8d13cca.PNG

 

 

 

 

 

 

 

I lost a lot time and money for fixing that...

Share this post


Link to post
Share on other sites
4 hours ago, alubaking said:

How about RAM? Are you overclocking your RAM as well? If you are, try not to OC RAM.

No, in second test where i disable all OC from CPU and GPU i also setted RAM to default 2133Mhz.

Share this post


Link to post
Share on other sites

POSSIBLE and I'm going to stress POSSIBLE FIX!!!

So after reading of other people having the issues and realizing that it's not limited to a CPU, motherboard, video card type or whether it's a base Vive or Pro I saw that someone had said they did not have the problem using the Cosmos, which doesn't use the lighthouses as it has inside out tracking.  So that got me thinking that therefore it's a lighthouse based issue.  Saw that people were having the problem with both 1.0 and 2.0 lighthouses, so that made me think that communications with the lighthouses is getting wonked.  For giggles I hooked up the original link box for the cables via USB 3.0 and the power plug with nothing else attached and then installed the bluetooth drivers and setup for the lighthouse power to be controlled via Steam VR.  Tested that the lighthouses were powering up and down when starting and closing Steam VR and they were.

The main problem I always had was after starting a game, within 7~10 minutes the HMD would go grey and I would here Windows losing and re-finding the hardware which could take anywhere from 20 seconds to a minute or two, and would get the grey drop out randomly after that.  Now?  I have tried it over a dozen times, rebooted, the whole enchilada and now at the same 7~10 minute mark (I use fpsVR as a timer) I get a 2~3 second black screen and it comes back ... and then no other drops during the whole play session, and at the moment it's been EVERY TIME, which it me is WAY more livable.

Don't hold me to this as everyone's mileage may vary and I thought that changing the headset channel fixed it and it ultimately turned out to be wrong, but if everyone can give it a shot (as I'm guessing most people still have their link box sitting somewhere) and report how it does, maybe even if it doesn't work for everyone it can narrow it down.

Share this post


Link to post
Share on other sites

I have been using this exact setup ever since I got my Wireless adapter. I have the linkbox plugged in so I can still use the Power Management features of the lighthouses. I have been experiencing these same dropouts and crashes identical to how they are shown in the YT videos. This is not related to the lighthouses. This is a software or driver issue of some sort.

Oddly enough, my wireless was stable until HTC pushed out the firmware and SW updates that fixed the AMD processor issues a while back. That is when these issues first started for me. I have reinstalled OS several times, issue remains.

  • Like 1

Share this post


Link to post
Share on other sites

Also here is a crash log from one I experienced last night. This was a full crash, not just a blackscreen. You will see that my fan cooling works very well on my adapter so this is not a heat issue.

[2020-02-14 22:27:39.234 -7 0x26C8 INFO LOG] M_Temperature=53, R_Temperature=46
[2020-02-14 22:27:49.231 -7 0x26C8 INFO LOG] M_Temperature=54, R_Temperature=48
[2020-02-14 22:27:58.159 -7 0x28FC INFO LOG] USB node not found 1.
[2020-02-14 22:28:02.295 -7 0x18C4 INFO LOG] (ControlCenter)Link Condition Change : peerSignalQuality = 255, performanceQuality = 3
[2020-02-14 22:28:02.478 -7 0x18C4 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_STOPPED(3), reason = SDK_CURRENT_STATE_REASON_LINK_LOSS(1)
[2020-02-14 22:28:02.481 -7 0x18C4 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_SCANNING(4), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2020-02-14 22:28:02.481 -7 0x26C8 INFO LOG] [SetCosmosAudio] Terminate OK.
[2020-02-14 22:28:02.486 -7 0x26C8 INFO LOG] Connection Status set to 2(CONNECTION_STATUS_SCANNING)
[2020-02-14 22:28:16.340 -7 0x18C4 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_CONNECTING(5), reason = SDK_CURRENT_STATE_REASON_AUTO_PROFILE_FOUND(4)
[2020-02-14 22:28:16.344 -7 0x26C8 INFO LOG] Connection Status set to 3(CONNECTION_STATUS_CONNECTING)
[2020-02-14 22:28:16.616 -7 0x18C4 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_CONNECTED(7), reason = SDK_CURRENT_STATE_REASON_SUCCEED_TO_CONNECT(13)
[2020-02-14 22:28:16.639 -7 0x26C8 INFO LOG] [SetCosmosAudio] Launch OK.
[2020-02-14 22:28:16.643 -7 0x26C8 INFO LOG] Connection Status set to 5(CONNECTION_STATUS_CONNECTED)
[2020-02-14 22:28:17.026 -7 0x28B4 INFO LOG] (ControlCenter)Get dock device name : VIVE1395
[2020-02-14 22:28:17.026 -7 0x28B4 INFO LOG] Device Name : VIVE1395
[2020-02-14 22:28:17.030 -7 0x28B4 INFO LOG] (ControlCenter)Otp Channel 1
[2020-02-14 22:28:17.030 -7 0x28B4 INFO LOG] (ControlCenter)Otp Channel 2
[2020-02-14 22:28:17.030 -7 0x28B4 INFO LOG] (ControlCenter)Otp Channel 3
[2020-02-14 22:28:17.030 -7 0x28B4 INFO LOG] (ControlCenter)Get dock preferred channel : Channel 2 (Player 1)
[2020-02-14 22:28:17.030 -7 0x28B4 INFO LOG] Preferred Channel : Channel 2 (Player 1)
[2020-02-14 22:28:17.037 -7 0x28B4 INFO LOG] (ControlCenter)CurrentFwVersion : 4.0.10377.40
[2020-02-14 22:28:17.037 -7 0x28B4 INFO LOG] (ControlCenter)FactoryFwVersion : 4.0.10327.19
[2020-02-14 22:28:17.037 -7 0x28B4 INFO LOG] (ControlCenter)NvmVersion : 8.32.2.7
[2020-02-14 22:28:17.037 -7 0x28B4 INFO LOG] (ControlCenter)MacHwVersion : 6577
[2020-02-14 22:28:17.038 -7 0x28B4 INFO LOG] (ControlCenter)RFEM1HwVersion : 8
[2020-02-14 22:28:17.038 -7 0x28B4 INFO LOG] (ControlCenter)RFEM2HwVersion : 8
[2020-02-14 22:28:17.038 -7 0x28B4 INFO LOG] (ControlCenter)ActiveFwVersion : MAIN
[2020-02-14 22:28:17.571 -7 0x18C4 INFO LOG] (ControlCenter)Link Condition Change : peerSignalQuality = 2, performanceQuality = 3
[2020-02-14 22:28:18.163 -7 0x28FC INFO LOG] USB node not found 1.
[2020-02-14 22:28:19.571 -7 0x18C4 INFO LOG] (ControlCenter)Link Condition Change : peerSignalQuality = 4, performanceQuality = 3
[2020-02-14 22:28:26.640 -7 0x26C8 INFO LOG] M_Temperature=51, R_Temperature=41
[2020-02-14 22:28:36.641 -7 0x26C8 INFO LOG] M_Temperature=54, R_Temperature=43

 

Share this post


Link to post
Share on other sites

Kudos to you all for an amazing amount of patience! I got rid of the adapter not long after my original post as to me, this is not a fluke issue, and being completely ignored by HTC has been all too familiar through the years of buying their products. I can no longer justify supporting them, so I will also be promptly selling my overpriced Vive Pro and moving on to another platform.

For those who persist, I really hope a solution becomes available soon. God know's you've all put in the work to try to figure it out!

Edited by jrmichel2000

Share this post


Link to post
Share on other sites

I'm having the same symptoms with my wireless Vive Pro.

i7 8700K

Gigabyte Z370 motherboard

MSI GTX 1080 Ti 

16GB DDR4-3200 PC4

Nothing overclocked

It was rock solid for a few weeks, then it said it needed a firmware update. I told it to go ahead and it just sat there and spun indefinitely. Now in every single VR session the following will happen after ~10 minutes: 

* Headset goes totally black

* LED on side of headset is red

* Motion tracking and all controllers still work 

* If I cycle the power to the headset by disconnecting and reconnecting the cable, 50% of the time it'll come back after 30s.

* Sometimes when it comes back the buttons on my controllers don't work, but motion tracking does

 

This is infuriating 

 

Share this post


Link to post
Share on other sites

Please sign in to comment

You need to be a member in order to leave a comment

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...