Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Oculus user entitlement check failed" on Beat Saber after rebooting my PC #1860

Open
CodyMarkix opened this issue Jul 4, 2024 · 7 comments
Labels

Comments

@CodyMarkix
Copy link

Do not report issues when using the Virtual Desktop or ALVR drivers for SteamVR, this is not supported by Revive.

Describe the bug
When installing Beat Saber, running via Revive works fine, even after downgrading and modding. After a PC reboot, attempting to launch Beat Saber either via the Steam library or Revive Dashboard gets Beat Saber to the epilepsy warning, then crashes with an entitlement check fail.

To Reproduce
Steps to reproduce the behavior:

  1. Open the Oculus app
  2. Start SteamVR
  3. Open Beat Saber via the Revive dashboard
  4. See Beat Saber crash after the epilepsy warning
  5. Cry because you've been troubleshooting for 2 days straight

Expected behavior
Beat Saber opens up and authenticates with Oculus like intended

Environment (please complete the following information):

  • App: Beat Saber 1.29.0
  • OS: Windows 11 23H2
  • Headset: Oculus Quest 2 (ALVR)

Versions (please complete the following information):

  • Revive: 3.0.2
  • SteamVR: 2.6.2

Additional context
While I'm running an older (and modded) version of Beat Saber downgraded via OculusDowngrader, this also happens on the latest vanilla version. (1.37.0)

Proof of ownership:
BZ9yupb

@CrossVR
Copy link
Member

CrossVR commented Jul 4, 2024

Are the Oculus VR Runtime Service and the Oculus VR Library Service running in the background like normal? Some people in the past disabled those services and then complained their game wouldn't start anymore due to entitlement errors.

Since you have an Oculus headset, please try running the game normally first before using SteamVR, I assume you're running on SteamVR to use chat overlays? Also, ALVR drivers aren't really supported by Revive, but this seems like an unrelated issue.

@CodyMarkix
Copy link
Author

CodyMarkix commented Jul 5, 2024

I did try using Oculus Link and the game launched as intended. And the VR Library service never starts as far as I can tell, so I'm gonna try to play with it enabled later during the day (currently traveling somewhere, thankfully with my quest 2) and update this comment.

@CodyMarkix
Copy link
Author

@CrossVR attempting to start the VR Library service gives this error
image

@CodyMarkix
Copy link
Author

Also from what I've read, the library service should be automatically started by the OVR server, which it doesn't. (But perhaps that's irrelevant in the case of Revive?)

@CodyMarkix
Copy link
Author

image

@CrossVR
Copy link
Member

CrossVR commented Jul 5, 2024

I was more concerned with it being purposefully disabled. The fix I wanted to try was to have you start the game through the Oculus store app before attempting to start it through Revive again as this refreshes the entitlement.

@CodyMarkix
Copy link
Author

No, I never purposefully disabled the service (truth be told I never noticed its existence until now haha). I'm also trying to get zerotier working with oculus link to refresh the entitlement, will update you on that later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants