-
-
Notifications
You must be signed in to change notification settings - Fork 482
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
Fix for blank vr screens not working #2432
Comments
You seem to also have the firewall issue from #2424 |
I don't have a fire wall enabled, so I'm not seeing the connection even if the error is the same? I respectively suggest this is an issue and not just a help ask since disable your fire wall, which appears to be the solution in the other thread is suboptimal at best. |
Even in that case it's tracked by that issue, this would just be a duplicate. Judging by some of the errors you could also try to properly restart your headset. After that it needs further investigating |
I’m not sure what you mean by properly. I tried both headset reset, power cycle, and resetting steam. I run through a bunch of permutations. But the error seems to persist. |
I have the black screen issue inside the headset too, SteamVR now doesn't have problems unlike yesterday, but a complete reinstall of Steam using official debs and not ubuntu debs tends to fix most problems In my case I'm using a Meta Quest 3 |
That issues is closed and doesn’t seem to have a proper resolution. |
I’m on POp_os and using the proper Debian package. |
I had to completely reinstall Steam using the official .deb from the website because SteamVR was complaining about "libcef.so missing" while it was right there... now it doesn't complain one bit, it doesn't crash one bit, but inside the headset I see black and a weird "light" flickering. This is a new problem, love it. |
I'm getting the same "End frame failed!" error and getting a black screen, even with the wiki fixes. I can't find anywhere else mentioning the error so i assume it's new. Using Tumbleweed with a Quest 1, SteamVR shows movement. |
They already decided it was related to a clearly unrelated fire wall issue (as in I don't have one), so not sure this will get any real attention :p. The sorta fix in the other thread is no good here. |
I don't have a firewall either, but my system has iptables, and the "add firewall" button takes care of it too. To verify it, do a |
Might be a vaapi codec thing, see https://dev.to/archerallstars/re-enable-va-api-hardware-video-acceleration-on-opensuse-tumbleweed-g8i |
That actually worked, even though I'm using an Nvidia card. Much obliged. |
Description
ALVR reports green, steam reports it seems the pico4 headset. Games start fine and show vr screen on monitor.
PICO screens remain blank (sometimes little bit of flashing).
I tried the recommended fix
~/.steam/debian-installation/steamapps/common/SteamVR/bin/vrmonitor.sh %command%
and
QT_QPA_PLATFORM=xcb ~/.steam/debian-installation/steamapps/common/SteamVR/bin/vrmonitor.sh %command%
No change.
General Troubleshooting
checked and rechecked, seems everything is in order.
Environment
Pop_os (Debian)
Hardware
Note: for Linux, an upload to the
hw-probe
database is preferred:hw-probe -all -upload
https://linux-hardware.org/?probe=3db990dffa
CPU:
i9 13kf
GPU:
nvidia 4070TI
GPU Driver Version:
550
Audio:
realtek
Installation
ALVR Version:
20.1.1.1
ALVR Settings File:
SteamVR Version:
what ever is current
Install Type:
exe
,deb
,rpm
, etc)zip
)OS Name and Version (
winver
on Windows orgrep PRETTY_NAME /etc/os-release
on most Linux distributions):"Pop!_OS 22.04 LTS"
debug
The text was updated successfully, but these errors were encountered: