-
Notifications
You must be signed in to change notification settings - Fork 50
Description
Describe the bug
in Vivecraft, or maybe other openGL Vr games. If you have two GPUs, the game doesn't render right in the headset or the vr view
To Reproduce
Steps to reproduce the behavior:
- Setup: you need two GPUs to reproduce it, both AMD in my case, as well as ALVR on the PC and headset, and a copy of Minecraft.
- set these enviroment vars in some manner to prevent a complete crash: MESA_VK_DEVICE_SELECT=/dev/dri/renderD129 & VK_DEVICE_SELECT=2
- ALVR will have you add a launch arg to steamVR, make sure to do that
- install farbic mod loader + the fabric version of the vivecraft mod into minecraft
- run steamVR, then launch minecraft. then set the game to VR mode
- the issue should show in the headset and vr view
Expected behavior
the feed should be normal... or at least not as buggy (ALVR has some minor glitches for me but that's not a SteamVR issue...)
System Information (please complete the following information):
Please use the latest Steam beta client and SteamVR beta for your bug reports!
- Steam client version (build number or date): 1763795278
- SteamVR version: build ID of: 20898164
- Distribution (e.g. Ubuntu): Arch Linux
- Steam runtime diagnostics: [generate via Help -> Steam Runtime Diagnostics in the Steam client]: https://gist.github.com/Nathan22211/0915d3f07a4aa9ea8d587499e3582037
- Steam and SteamVR logs: [generate by running this command in a terminal
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs] (i might need the excact filename for these...)
- Minidumps: [run the following command:
tar -zcvf ~/Desktop/steam-minidumps.tar.gz /tmp/dumps]
Screenshots
Additional contextAdd any other context about the problem here.
there's these erros in the MC console log on startup
[02/12/2025 18:47:56 PM] WARNING: radv is not a conformant Vulkan implementation, testing use only.
[02/12/2025 18:47:56 PM] [Worker-Main-14/INFO] Vivecraft: MenuWorlds: Downloading world menuworlds/world34.mmw
[02/12/2025 18:47:56 PM] [Render thread/INFO] OpenGL debug message: id=2, source=API, type=ERROR, severity=HIGH, message='GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_2D)'
[02/12/2025 18:47:56 PM] [Render thread/INFO] OpenGL debug message: id=2, source=API, type=ERROR, severity=HIGH, message='GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_2D)'
[02/12/2025 18:47:56 PM] [Render thread/INFO] OpenGL debug message: id=2, source=API, type=ERROR, severity=HIGH, message='GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_2D)'
[02/12/2025 18:47:56 PM] [Render thread/INFO] OpenGL debug message: id=2, source=API, type=ERROR, severity=HIGH, message='GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_2D)'
[02/12/2025 18:47:56 PM] [Render thread/INFO] OpenGL debug message: id=2, source=API, type=ERROR, severity=HIGH, message='GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_2D)'
[02/12/2025 18:47:56 PM] [Render thread/INFO] OpenGL debug message: id=2, source=API, type=ERROR, severity=HIGH, message='GL_INVALID_ENUM in glIsEnabled(GL_TEXTURE_2D)'
[02/12/2025 18:47:56 PM] [Render thread/ERROR] Vivecraft: ########## GL ERROR ##########
[02/12/2025 18:47:56 PM] [Render thread/ERROR] Vivecraft: @ post submit
[02/12/2025 18:47:56 PM] [Render thread/ERROR] Vivecraft: 1280: invalid enumI suspect the radv warning is due to what OpenVR needs and what I have installed. I talked to the dev and we suspect it's a steamVR issue as it's worked with 2 GPUs prior