ALVR: 20.6.0 shows a blackscreen. Makes HTC Vive XR UI to crash

Description

It does kind-of-a system crash on HTC Vive XR.

20.4.X: Works fine 20.5.X: Handshake error 20.6.X: Headset goes into full black screen and nothing happens, buttons make sounds but even HTC home interface doesn’t work. Pressing the power button makes a restart.

This can be reproduced on both cable and WiFi connection, and both h264/h265 codecs

No idea how to get any technical details from here. There are logs from adb, but nothing much useful related to ALVR.

General Troubleshooting

  • I carefully followed the instructions in the README and successfully completed the setup wizard
  • I read the ALVR Wikis here and here

Environment

Gentoo Linux

Hardware

Basically HTC Vive XR and Gentoo Linux.

CPU: AMD Ryzen 7 5800H

GPU: AMD Renoir/Cezanne AMD Radeon 6700M

GPU Driver Version: Kernel 6.6.8, amdgpu

Audio: AMD Renoir ACP

Installation

ALVR Version: 10.6.0

ALVR Settings File: session.json

SteamVR Version: Build ID: 13024612 (default, no beta)

Install Type:

  • Packaged (exe, deb, rpm, etc)
  • Portable (zip)
  • Source

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions):

NAME=Gentoo ID=gentoo PRETTY_NAME=“Gentoo Linux” ANSI_COLOR=“1;32” HOME_URL=“https://www.gentoo.org/” SUPPORT_URL=“https://www.gentoo.org/support/” BUG_REPORT_URL=“https://bugs.gentoo.org/” VERSION_ID=“2.14”

About this issue

  • Original URL
  • State: closed
  • Created 6 months ago
  • Reactions: 1
  • Comments: 28 (6 by maintainers)

Most upvoted comments

The feature loss should be temporary. The problem is with our current OpenXR app lifecycle. When we release v21 we will add a non-vr lobby screen with some client-side settings, and we can work around this limitation.

I can reproduce the issue and I’m working on a fix

The bisection leads me to the commit 7bc20e40b675eb9e67cd881675a4fce2e5703761 introducing the bug Also, when using logcat with adb, I saw that the error that gets shown the most is an invalid textureid(0)

@waltercool please bisect the nightly versions (of the client) to find when this bug started.