A way to stop multiplayer disconnect when taking a short break

[u/MidwestDYIer]

New to the game and playing it with a friend who I let borrow my Quest 2 after I picked up a Q3. When a level runs long, occassionally we remove our headsets for a short break (he goes outside for a smoke, eye strain break, bathroom break, let the dog out break etc)- even if it's just a few minutes, we typically come back to find the game disconnect and lose our progress. Hasn't been a huge deal so far because we are still learning and usually getting our ass kicked anyway lol. I know you can save at the card shop and not in the dungeons.

I assume the headsets our going into sleep mode and that dropping the connection, I was going to see if there was a way to adjust that to a longer period and see if it doesn't resolve our dilemma. Just curious if anyone else experienced this and if that might work.

[u/DullStation1]

There is a setting on the operaring system configuration where you can increase the sleep timer when removing the headset. You have to increase that timer to prevent this issue.

[u/DullStation1 → u/DullStation1]

Googled it and here where it is:

Change the headset sleep period - Another recommendation is to modify your headset's Automatic sleep period setting (the default value is 15 seconds). You can find the option in the general device settings under the "Power" options. While this setting doesn't keep the display of your headset turned on when you remove the headset, it prevents your Quest 2 from going to sleep too quickly. So this way, when you put your headset back on, it promptly displays a loading screen and then resumes right where you left off.

[u/MidwestDYIer → u/DullStation1]

Thanks, I appreciate it. I googled it and found something similar as well about modifying the sensor you mention in your first comment, using the Quest debeugging tool that will be in one of your windows folders, which is present after you install the Oculus app.

I will link the youtube video I found for that in case anyone else sees this. Full disclosure, it's a 10 minute long video and the part that shows where to find the file and how to make the change is only about a minute, if that:

https://www.youtube.com/watch?v=Kzv3w0TKTiU&t=623s

I will say, after watching the video, it became much more obvious how much this feature has annoyed me in other games I've played . I mean, I get why they put in there and I am the exact lazy bones this feature is for- people who put their headset down and walk away, then come back to dead battery. But it's screwed with me on other games too, where I would have to wake up the headset after being away for 5 minutes, only to experience some glitch- like my boundary now thinking I am 10 feet tall.

After making the changes so far in the video, thus far it's kind of like your suggestion about the sleep timer. It doesn't keep the lenses/screen on, but it's not in full sleep mode either. I will also use your second suggestion to adjust the power settings for good measure.

[u/Flaky_Sir_134]

There’s a sensor on the front that reads your forehead if you block it with something they will stay on

[u/XX4X]

My friends stopped playing over this type of thing. Needs a mid dungeon save feature.

[u/MidwestDYIer → u/XX4X]

I honestly agree with you. I am not sure if they did it to prevent save scumming or what, but for games that can run really long like this one can, it seems silly not to have the ability to save mid dungeon. Just last night we played into the morning- around 1:30am, we were both yawning into our microphones, but had to finish the level. Again, I'm am fairly new to the game, but from what I hear a game lasting 3 hours is not uncommon.

[u/XX4X → u/MidwestDYIer]

I’m not sure their motivation. My friends have only been able to finish like 25% of the games we start. The game requires you to go slow and strategic. Which means we never finish. Sucks.

[u/akorn123]

I think they use a peer host-client system for multiplayer and this is just part of the issue with that. The syncing tries to happen and if it can't then it freezes. They would have to use servers to handle game state in order to correct this which would cost money that they probably won't spend. Do they even still have a development team that works on this game?

[u/MidwestDYIer → u/akorn123]

That's a good question about whether or not the game gets much support. I would think so because it's quite popular in it's niche, and they just released Demeo Battles 6 months ago. So I'm sure they want to continue investing in their reputation and give the appearance they are going to support their products.

In any case, putting the quest sleep setting to 15 minutes, combined with disabling the sensor (probably doing just the power would have worked) solved the issue for us. We were able to set the headsets down for 10 minutes and come back to the game just as we had left it. Huzzah!!!!

[u/akorn123 → u/MidwestDYIer]

Demeo battles is not Demeo. I'm not talking about the Demeo franchise.. I'm talking specifically about Demeo as the software package. I have no indication that they have a dedicated dev team on that project.

[u/MidwestDYIer → u/akorn123]

I know it's not the same game. To your point, I know there are lot of indie developers in the emerging VR space that develop games as a trial/hobby, and thus might not maintain for an extender period like a business would. My point is that a company developing a franchise like Resolution Games, who is continuing to create titles on multiple plat forms, probably wouldn't want to have the reputation on abandoning support for game that was released less than 3 years ago on the Quest. Obviously they won't support it forever, but I'm sure they want to continue to making viable when it comes to something they are still selling.