-
Notifications
You must be signed in to change notification settings - Fork 45
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
[BUG] No more SteamVR overlay #632
Comments
Quick question; how long will the SteamVR team leave up the 1.27.5 temp beta branch for SteamVR? It's gonna be my only real fallback that isn't the SteamVR 1.14 branch. |
Same issue, renders on 1.27.5. Works on Steam Deck, heard of same issue also on Arch from one other person. Distribution: Arch |
I'm experiencing a related issue. Sometimes the program manages to open, but then it freezes momentarily. Steam (not SteamVR) crashes on my PC, briefly displaying the new UI on the headset before it disappears. I suspect this may be related to Nvidia hardware acceleration. |
Hello @Dreaming-Codes, @Korysovec (could you pass it to that person if you have contact to them), @2-3-5-41 |
I've fixed my issue using Nvidia prime since I'm on an Optimus laptop, I'm on hyprland. |
I'm encountering this issue again |
Took me long enough to figure out; If You're on AMD graphics card(s), make sure steam is running under Mesa(RADV) drivers for the steam overlay to be able to use DRM. And for Nvidia graphics cards, you too should make sure steam in running under a graphics driver that allows for DRM on your GPU. Note: |
Describe the bug
SteamVR overlay no longer renders.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
SteamVR overlay renders, I don't care if it's the obsolete one.
System Information (please complete the following information):
nvidia-settings
orvulkaninfo | grep driverInfo
: 2023.Q4.1 (LLPC)Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.
The text was updated successfully, but these errors were encountered: