protonscr

Nvidia 381.09 beta driver supported?

steamvrclosed
ValveSoftware/SteamVR-for-Linux#44 · opened 2017-04-07 by yaomtc · updated 2017-05-25 · 9 comments · github
Yyaomtc 2017-04-07 github

Your system information

  • Steam client version (build number or date): 1.0.0.54 / Mar 30, 2017 / 1490914880
  • Distribution (e.g. Ubuntu): Arch Linux
  • Graphics driver version (run nvidia-settings): 381.09
  • Gist for SteamVR System Information: https://gist.github.com/yaomtc/96200f58216acfa53abd0103f78a9748
  • Opted into Steam client beta?: Yes
  • Opted into SteamVR beta?: Yes
  • Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

I recently installed the latest Nvidia beta driver, 381.09, which added updated Vulkan support that I thought might just work with SteamVR. Gave it a try, and it was a bit laggier than I expected, so I wasn't sure direct mode was working. Sure enough, the report says it's not direct mode. So I guess the SteamVR beta doesn't yet support these new drivers for direct mode. I'll have switch to the "vulkan-beta" AUR packages in the meantime. EDIT: It might have been in direct mode, missed the Known Issue. So does this driver work as well as the 375.27.xx line?

Yyaomtc 2017-04-08 github

Well. I installed those other packages, but... either direct mode is working and SteamVR isn't aware, or I actually am stuck in extended mode. It felt and looked the same, anyway.

https://gist.github.com/yaomtc/3853be59d1e504cfa317d635c1b0c737

Kkkriehl 2017-04-08 github

You're right - SteamVR isn't aware if direct mode is working or not. If direct mode isn't working you'll see a VRCompositor window popping up on the desktop. If X11 is not explicitly configured to allow HMDs as screens the Vive screens won't show anything, either.
If direct mode on Linux is working you will see the SteamVR environment only on the Vive screens.
I think you can verify if it's working by searching for Instance extensions available inside the compositor logs: .local/share/Steam/logs/vrcompositor.txt. If the Vulkan extension VK_EXT_direct_mode_display is mentioned in the list below, the compositor should use direct mode even if it says Headset display is on desktop later in the logfile.

I'm only guessing, though. It would be great if someone with more in-depth knowledge could confirm that.

Yyaomtc 2017-04-08 github

Whoops, that's what I get for not reading everything. Direct mode is probably working, then - must be just added latency of the not-well-optimized beta that was bothering me.

I changed the title to a question. Performance seemed identical between this new beta driver and the older officially-supported driver. (Though the SteamVR tutorial doesn't exactly push my hardware very hard.)

Rroothorick 2017-04-10 github

381.09 Working flawlessly for me with SSVR:TFE in Ubuntu-GNOME 16.04.2 on a GTX 1070. I'm having problems with Destinations crashing but I always did.

Aaronschatz 2017-04-12 github

@roothorick Destinations crashing has been a problem the entire time. But this driver seems fine from my testing with SSVR:TFE. It's still a bit slow on tracking, but that's probably SteamVR.

Eeric-schleicher 2017-04-27 github

pardon my ignorance; what is SSVR:TFE?

Yyaomtc 2017-04-27 github

Serious Sam VR - The First Encounter

Eeric-schleicher 2017-04-27 github

Thanks!

Yyaomtc 2017-05-25 github

This was fixed on the readme at some point fairly recently ("NVIDIA cards require version 381.22 of the NVIDIA Driver or above") so this can be closed now.

Nothing extracted yet.