Disable headset sleep/standby

[deaedius]

Hello John,

 

I have confirmed that unplugging the TV HDMI did not resolve.  I have further observed that the VIVE is not going to sleep, it appears to be a display shut down instead although the VIVE headset is still technically running.  I unplugged the breakout box and plugged it back in and get a similar screen blink when the headset but I get an audio tone of the system recognizing the VIVE display, although it will go blank after a few seconds, the troubling symptom of when the VIVE screen goes black and my main monitor blinks I do not get a audio tone of it turning off or on, its just the vive display blacking out.  

 

I have ran DDU for a full clean removal of graphics drivers and will be installing 391.01 drivers again to see if this helps.  If not then I will go back to 388.71.

 

Thank you,

[deaedius]

Hello John,

 

I reviewed the logs for when the VIVE works normally and after driver install and system reboot, after diging around a bit I found some interesting things.
vrmonitor.log

Before system restart and driver install.

Thu Mar 01 2018 21:15:49.636 - [system] Transition from 'Connecting' to 'Ready'.
Thu Mar 01 2018 21:15:54.043 - [system] Transition from 'Ready' to 'Not Ready'.
When the VIVE goes into a "Not Ready State" this is when the screen goes black.

 

I restarted the VIVE by clicking the enable Direct Mode.

Thu Mar 01 2018 21:16:06.858 - [system] Transition from 'Not Ready' to 'Preparing to Quit...'.
Thu Mar 01 2018 21:16:06.869 - [system] Quit gracefully, power off devices and quit processes via dashboard ...
Thu Mar 01 2018 21:16:06.872 - [system] Quit gracefully: Wait for quit...
Thu Mar 01 2018 21:16:09.214 - [system] Transition from 'Preparing to Quit...' to 'Shutdown'..

 

 

 

Below are entries after the system was rebooted and drivers reinstalled.
2 successful launches of the VIVE

1.
Line 771: Thu Mar 01 2018 21:39:09.404 - [system] Transition from 'Starting' to 'Connecting'.
Line 800: Thu Mar 01 2018 21:39:11.974 - [system] Chaperone tries to change for the first time, but is invalid
Line 801: Thu Mar 01 2018 21:39:12.021 - [system] Transition from 'Connecting' to 'Ready'.
Line 802: Thu Mar 01 2018 21:39:12.065 - [system] Chaperone Universe changes for the first time

2.
Line 948: Thu Mar 01 2018 21:39:41.069 - [system] Transition from 'Starting' to 'Connecting'.
Line 965: Thu Mar 01 2018 21:39:43.548 - [system] Chaperone tries to change for the first time, but is invalid
Line 966: Thu Mar 01 2018 21:39:43.580 - [system] Transition from 'Connecting' to 'Ready'.
Line 972: Thu Mar 01 2018 21:39:43.738 - [system] Chaperone Universe changes for the first time

Before system reboot and driver install I see the following message.
Line 49: Thu Mar 01 2018 21:14:47.332 - [system] Transition from 'Starting' to 'Connecting'.
Line 77: Thu Mar 01 2018 21:14:49.747 - [system] Chaperone tries to change for the first time, but is invalid
Line 78: Thu Mar 01 2018 21:14:49.776 - [system] Chaperone tries to change for the first time, but is invalid
Line 79: Thu Mar 01 2018 21:14:49.839 - [system] Transition from 'Connecting' to 'Ready'.
Line 80: Thu Mar 01 2018 21:14:49.841 - [system] Chaperone tries to change for the first time, but is invalid
Line 81: Thu Mar 01 2018 21:14:49.997 - [system] Chaperone tries to change for the first time, but is invalid

If the VIVE has Transition from 'Connecting' to 'Ready'. and log message "Chaperone tries to change for the first time, but is invalid" is displayed after the screen goes black as seen above.

This is seen each time the VIVE fails to display its screen.

Failures.
1.
Line 49: Thu Mar 01 2018 21:14:47.332 - [system] Transition from 'Starting' to 'Connecting'.
Line 77: Thu Mar 01 2018 21:14:49.747 - [system] Chaperone tries to change for the first time, but is invalid
Line 78: Thu Mar 01 2018 21:14:49.776 - [system] Chaperone tries to change for the first time, but is invalid
Line 79: Thu Mar 01 2018 21:14:49.839 - [system] Transition from 'Connecting' to 'Ready'.
Line 80: Thu Mar 01 2018 21:14:49.841 - [system] Chaperone tries to change for the first time, but is invalid
Line 81: Thu Mar 01 2018 21:14:49.997 - [system] Chaperone tries to change for the first time, but is invalid
Line 88: Thu Mar 01 2018 21:14:50.029 - [system] Chaperone Universe changes for the first time

2.

Line 407: Thu Mar 01 2018 21:34:49.877 - [system] Transition from 'Connecting' to 'Not Ready'.
Line 408: Thu Mar 01 2018 21:34:49.877 - [system] Check for dismissable warnings at startup.
Line 413: Thu Mar 01 2018 21:34:49.927 - [system] Transition from 'Not Ready' to 'Ready'.
Line 431: Thu Mar 01 2018 21:35:09.816 - [system] Chaperone tries to change for the first time, but is invalid
Line 432: Thu Mar 01 2018 21:35:09.816 - [system] Chaperone tries to change for the first time, but is invalid
Line 435: Thu Mar 01 2018 21:35:09.932 - [system] Transition from 'Ready' to 'Not Ready'.
Line 437: Thu Mar 01 2018 21:35:09.952 - [system] Chaperone tries to change for the first time, but is invalid
Line 438: Thu Mar 01 2018 21:35:10.191 - [system] Chaperone tries to change for the first time, but is invalid
Line 439: Thu Mar 01 2018 21:35:10.282 - [system] Chaperone Universe changes for the first time
3.
Line 541: Thu Mar 01 2018 21:35:33.305 - [system] Transition from 'Starting' to 'Connecting'.
Line 569: Thu Mar 01 2018 21:35:35.721 - [system] Chaperone tries to change for the first time, but is invalid
Line 570: Thu Mar 01 2018 21:35:35.814 - [system] Transition from 'Connecting' to 'Ready'.
Line 571: Thu Mar 01 2018 21:35:35.845 - [system] Chaperone tries to change for the first time, but is invalid
Line 572: Thu Mar 01 2018 21:35:35.970 - [system] Chaperone Universe changes for the first time

 

I do not think it is a driver issue anymore, I think the system restart fixes it not a driver install, although it doesn't explain why it worked a couple days ago with just a driver install and no reboot.  It seems to be tied to the timing of "Chaperone tries to change for the first time, but is invalid" or whatever process the Chaperone uses.  I thought it was tied to the base stations syncing up but the timing of the base stations didn't seem to matter on working or non working even when observing them them going solid green or not, when the error "Chaperone tries to change for the first time, but is invalid" pops up AFTER the VIVE states it is ready, if it is BEFORE the VIVE does not have problems.

Anyway this is weird stuff, I hope this helps as well.  I will monitor tomorrow.  If I see the same errors I will try the 388.71 drivers if it still happens.  I will go back to 391.01 and stay there as I will then believe it is VIVE software.

Thank you,

 

[deaedius]

ok my last reply today.

 

I was looking into config files.  After manually changing within the VR the sleep timer from 5 seconds to 10 minutes. I found today in a setting the vive reverted back to 5 seconds.

"turnOffScreensTimeout" : 5.0,

 

I flipped this to 300.0. and will also continue to test.

 

Thank you,

[Synthesis]

It might behoove us to reinstall Vive completely, including USB drivers at this point and see if that helps at all.

Let's see what the turnOffScreensTimeout change does first though.

Thank you,

-John C

[deaedius]

Hello John,

 

Sure thing I tested the VIVE this morning and it was working.  I will test again tonight to see if there is any improvement.  

If the issue happens I will unplug the VIVE, uninstall everything, plug in and reinstall.

 

Thank you,

[Synthesis]

 

If it happens again, you can PM me or @ me here and we'll take it from there.

Thanks!

-John C

[Chagaze]

Hello,

 

I tested last weekend with "388.71-desktop-win10-32bit-international-whql.exe".

 

Problem still happen, no improvment, Screen turn off after 5s-10s.

 

The reboot seems quite efficient, but after a time, problem come again.

 

By the way, when i turn on the vr, i can say quite quickly if i will have the problem after 3s because the image is jerky when moving head. When it work fine, the image follow well the head moves.

 

 

[GrimCW]

A fix for this would be REAL nice about now.. Getting a little sick of having to reboot, reinstall and reconnect everything every time I'd like to play something in VR...

Seems to be the only way to do anything for it so far. I've tried the rest of these fixes and thus far nothing has worked aside from the disconnect everything and reboot everytime I want to play.

nearly a dozen SteamVR updates and several Nvidia driver updates since and its still a major problem..

[Synthesis]

Did you try changing "turnOffScreensTimeout" to a larger number?

You mentioned driver updates. Did you roll back to an earlier version or update to the current version?

Thanks,

-John C

[GrimCW]

I rolled back Nvidia to something I forget (it was about 2 months ago, but the drivers were from around November/December time. I know that because I finally got my EVGA 1080 FTW  in early january and actually tried to get back into VR more. But the issue was also on my original Nvidia GTX 980 as well). Found it in another thread like this one on google while trying to find a fix.

didn't help, and topping that it would make over a dozen newer games unplayable. On the note worthy side it also did make VR actually run worse when it did work (after a fresh reboot and replug) causing all sorts of frame loss and game or VR crashes.

 

 

for the list I've tried

Rollback of Geforce drivers

Beta SteamVR currently, and tried non-beta as well

Complete clean out of all VR drivers and fresh install

Clean out and reinstall of Nvidia content

Different USB ports (various 2.0 and 3.0)

increased shutoff/sleep time

and so far the only thing working is disconnect, reboot, reconnect. But after shutting down once, the bug returns if I boot back up at a later time. During that time it runs grand aside from an occasional flicker.