Solved

VR Crashing every 25 minutes - New Device Connected


Userlevel 1
Badge

I’m streaming PCVR to my Quest using Virtual Desktop.  I haven’t had any issues until Tuesday this week: after 25 minutes of VR, with no other input into the Shadow, I hear the Windows ‘Device Connected’ chime and my VR game crashes.  I then see the USB/External drive icon in my taskbar with an NVIDIA graphics card listed as the external device.  If I force the game and Steam VR to quit and get it restarted, 25 minutes later I hear the ‘Device Disconnect’ chime followed by the ‘Device Connect’ chime and again, whatever VR game I’m playing crashes.

I mentioned this in the Virtual Desktop Discord and it does appear other people are experience the issue, and if they pause VR and interact with the streamer client, they don’t get the ‘Device Connected’ chime.  I also tested leaving the streamer up NOT playing VR, and as long as I’m interacting with the desktop, I’m not getting the ‘Device Connected’.

icon

Best answer by Gaijin 29 July 2020, 10:41

View original

This topic has been closed for comments

35 replies

Userlevel 3
Badge +1

I wonder if shadow is starting the power off process. Virtual Desktop is suppose to keep Shadow alive, but it sounds like yours might be ready to sleep. Have you tried running shadow from phone to use VR then touch phone say every 15 to see if you’re giving it what it needs to stay running? Just to see?

Badge

”Virtual Desktop is suppose to keep Shadow alive”

 

Is that a new feature? I got used to moving the mouse every 25 min (annoying as hell). 

Using Shadow Boost, Mac client, 1GB up/down fibre, Oculus Quest via Virtual Desktop.

I’m also getting this: the symptom for me while playing Half Life Alex is the USB disconnect sound (higher to slightly lower pitch tones) then the whole VR environment either seems to freeze, or the whole scene moves with my head. Pressing and holding the oculus menu button doesn’t even seem to exit out of Virtual Desktop.


On the Shadow PC client (running on a Mac), I can still interact with Windows, but I have to then manually shut down Alyx using the floating SteamVR control panel (but this doesn’t allow me to save my position).


Hoping this is a glitch Shadow is aware of and fixing? Is it related to the auto shutdown at 30 minutes that was previously fixed? Or is it a Virtual Desktop issue?

Yeah I have this same issue; the timeout had been fixed for the stable PC client while using VR but now it is back in a different way with this; the Shadow doesn’t shut down itself but it disconnects the VR headset at roughly the same timing as it used to shut down the shadow.

What makes it worse is you can’t always recover without restarting Shadow entirely. At least with the old timeout with “are you there?” dialog, if you forgot to move the mouse enough and got the freeze, you could still recover by clicking “Yes, I’m still here” and then go right back in to your VR title. Now if you forget and you get that “Device disconnected” chime and message, you’re screwed. It crashes the game, it crashes Steam, and you can’t recover easily. 

I have noticed that the Oculus Rift platform seems to be able to possibly recover with just closing and reopening Virtual Desktop, but I only did that once, so I’m not sure on that.

When I play steam vr games using the oculus quest and virtual desktop, I find that after 15-20 minutes the server just shuts down. 
 

this is a Problem for my gaming but I understand why this has been put into place. 
 

my question is, is their a way to turn this feature off or extend it. I always power down the service when. Not in use I just need longer gaming time. 
 

I don’t want to put a mouse in my pocket or have to keep touching my iPhone screen to make it look like activity every 5 minutes. 
 

I just want to play a game and shutdown once I’ve finished. 
 

cheer sin advance. 
 

Banderas23

Userlevel 4
Badge +4

Unfortunately finding a way around the shutdown timer is against TOS (https://shadow.tech/usen/terms)

They are working on this issue regarding VR (thanks to the US VR exploration program) and i’m sure they will find something when VR is officially supported by Shadow 🙂 .

You can also find here a list of what is and isn’t allowed on Shadow :)

 

Hope i answered your question properly ^^

Userlevel 6
Badge +6

Most use a bluetooth mouse in their pocket and bug it every so often when they play, or you can just bug your mouse every so often while you play. But I do hope they put a proper fix for it soon. 

Userlevel 4
Badge +4

Most use a bluetooth mouse in their pocket and bug it every so often when they play, or you can just bug your mouse every so often while you play. But I do hope they put a proper fix for it soon. 

Nice solution Lili. 

 

I'm almost certain that I heard shadow says that, at some point they will find a solution for this particular issue. But i would say this will come with the official release of the VR app , not before ( but that's just my opinion tbh)

Userlevel 3
Badge +1

Shadow is suppose to see Virtual Desktop as an input device now for VR users. Maybe try the beta client, people have reported this works for keeping Shadow alive. 

Userlevel 3
Badge +1

”Virtual Desktop is suppose to keep Shadow alive”

 

Is that a new feature? I got used to moving the mouse every 25 min (annoying as hell). 

I think its been around a month. I know its a feature, but I also have evidence that sometimes it fails. 

Userlevel 1
Badge

having the same issue here. Virtual desktop, Steam VR, oculus quest, with mobile shadow client running to start the shadow and keep it alive. Quest freezes after I hear the chime and I can only recover bij restarting quest and launching VD again.

I know there is no official quest support (yet) but sounds like there a quite a few folks that have one and would love to use a quest with shadow. Heck I plan on upgrading my shadow if native support comes out. VR + shadows is simply awsome.

@VRLife could you send me your Shadow account email in private message?

It will allow us to investigate as this is not supposed to happen anymore with Virtual Desktop.

Hi

Same issue here.

 

Hope it’ll we be solved soon

Userlevel 6
Badge +6

Hi

Same issue here.

 

Hope it’ll we be solved soon

You should DM Loic (above) as well then! 

Userlevel 6
Badge +6

I’m streaming PCVR to my Quest using Virtual Desktop.  I haven’t had any issues until Tuesday this week: after 25 minutes of VR, with no other input into the Shadow, I hear the Windows ‘Device Connected’ chime and my VR game crashes.  I then see the USB/External drive icon in my taskbar with an NVIDIA graphics card listed as the external device.  If I force the game and Steam VR to quit and get it restarted, 25 minutes later I hear the ‘Device Disconnect’ chime followed by the ‘Device Connect’ chime and again, whatever VR game I’m playing crashes.

I mentioned this in the Virtual Desktop Discord and it does appear other people are experience the issue, and if they pause VR and interact with the streamer client, they don’t get the ‘Device Connected’ chime.  I also tested leaving the streamer up NOT playing VR, and as long as I’m interacting with the desktop, I’m not getting the ‘Device Connected’.

If your question was answered/fixed please mark it as answered, thanks ^^

Userlevel 1
Badge

what is your startup process to start quest VR? maybe I’m making a mistake here. What I do:

  1. start mobile client and go to desktop mode (1mbps)
  2. log in
  3. start VD on quest
  4. start Steam VR
  5. play for 25 min and get chime error and all locks up.

for those not experiencing the issue, how do you start up?

Userlevel 1
Badge

anyone? is the discord the better place to ask these questions?

So when I try to run virtual desktop with shadow boost, both shadow and virtual desktop crash in about 5 seconds does anyone have a solution for this? Thanks!

Userlevel 1
Badge

@Fishman1  - maybe open up a separate topic so we keep this thread focussed on the  25 min issue. cheers.

Userlevel 3
Badge +1

Here is how I do it. I start Shadow on my Mac, then switch Mac to 5mbps and then go to Quest. When I use it like this it never has issues and lasts awhile. I’ve mentioned up the chain that iOS doesn't seem to keep alive. 

Userlevel 1
Badge

Here is how I do it. I start Shadow on my Mac, then switch Mac to 5mbps and then go to Quest. When I use it like this it never has issues and lasts awhile. I’ve mentioned up the chain that iOS doesn't seem to keep alive. 

And yours never times out, and you never receive the ‘new hardware’ chime?  I have the issue if I have the streamer open on either my mac or my PC.

Userlevel 1
Badge

Hi

Same issue here.

 

Hope it’ll we be solved soon

You should DM Loic (above) as well then! 

Thanks Lily.  I did but haven’t heard back.  I’m **assuming** the team is working on it ;)

Userlevel 3
Badge +1

Here is how I do it. I start Shadow on my Mac, then switch Mac to 5mbps and then go to Quest. When I use it like this it never has issues and lasts awhile. I’ve mentioned up the chain that iOS doesn't seem to keep alive. 

And yours never times out, and you never receive the ‘new hardware’ chime?  I have the issue if I have the streamer open on either my mac or my PC.

Not when my Mac is running the stream. I turn it to 5mbps, then fire the quest up. Your Shadow has 100mbps upload and thats what the stream uses. Hence the 5mbps, to leave plenty of bandwidth for Quest.

Userlevel 1
Badge

Here is how I do it. I start Shadow on my Mac, then switch Mac to 5mbps and then go to Quest. When I use it like this it never has issues and lasts awhile. I’ve mentioned up the chain that iOS doesn't seem to keep alive. 

And yours never times out, and you never receive the ‘new hardware’ chime?  I have the issue if I have the streamer open on either my mac or my PC.

Not when my Mac is running the stream. I turn it to 5mbps, then fire the quest up. Your Shadow has 100mbps upload and thats what the stream uses. Hence the 5mbps, to leave plenty of bandwidth for Quest.

It’s not a bandwidth issue.  The issue is that the Shadow doesn’t recognize VR as input and tries to shut down after 30 minutes when it hits the inactivity timeout.  It was fixed for a week, but has come back as a weird hardware connect/disconnect issue.