valvesoftware / steamvr-for-linux

Issue tracker for the Linux port of SteamVR

SteamVR Release Notes and Known Issues

This is a development release. It is intended to allow developers to start creating SteamVR content for Linux platforms. Limited hardware support is provided.

SteamVR and VR apps require a modern linux distribution with up to date graphics drivers. Ubuntu >= 20 or Arch for instance.

For discussions and questions, please use the SteamVR for Linux forum at http://steamcommunity.com/app/250820/discussions/5/.

For bugs, please file an issue on this github issue tracker. https://github.com/ValveSoftware/SteamVR-for-Linux/issues

GRAPHICS DRIVER REQUIREMENTS

SteamVR is built on top of the Vulkan API and requires the latest Vulkan drivers.

NVIDIA on Ubuntu

We recommend using the latest NVIDIA drivers from the "Graphics Drivers" PPA at https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa

AMD on Ubuntu

We recommend using the latest mesa drivers from the PPA at https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa

NATIVE DEVELOPMENT

Version 1.0.7 of the OpenVR SDK has full support for Linux platforms: https://github.com/ValveSoftware/openvr

steamvr-for-linux's Issues

Lighthouse firmware update

Your system information

• Steam client version (build number or date): Feb 21 2017, at 20:24:31
• Distribution (e.g. Ubuntu): Ubuntu 16.04.2 LTS (64 bit)
• Opted into Steam client beta?: [Yes/No] Yes
• Have you checked for system updates?: [Yes/No] Yes

I tried to update the Lighthouse firmware to the latest version, but after plugging in the usb cable and power while holding the mode button, the folder 'CRP DISABLD' will open with one file 'firmware.bin', the Update window will keep waiting for the base station until it timeout and fail.

By enabling bluetooth, pairing the stations and enabled bluetooth communications in SteamVR, then i was able to try to update the firmware wirelessly, this also failed. The file seems to be missing....

firmware_update.txt Wed Feb 22 2017 04:39:43.982452

Wed Feb 22 2017 04:39:43.982452 - ================================================
Wed Feb 22 2017 04:39:44.014224 - FirmwareWizard entering state Device Overview (0)
Wed Feb 22 2017 04:39:44.014916 - Start Firmware Update (Device Index:2, Recovery:0, ForceAll:0, ForceFix:0).
Wed Feb 22 2017 04:39:44.035362 - 1 Updates scheduled for Device Class: 4
Wed Feb 22 2017 04:39:44.035392 -     1: Watchman Disk Update: Existing:244, Required:436
Wed Feb 22 2017 04:39:44.035401 - FirmwareWizard entering state Base Station Start (10)
Wed Feb 22 2017 04:39:44.035406 - FirmwareWizard overwriting state to Shutdown VR Apps (1)
Wed Feb 22 2017 04:39:46.265900 - Delaying for 5000 milliseconds...
Wed Feb 22 2017 04:39:51.265004 - Delay done
Wed Feb 22 2017 04:39:54.355128 - FirmwareWizard entering state Base Station Start (10)
Wed Feb 22 2017 04:39:56.534602 - FirmwareWizard entering state Base Station Wireless Progress (17)
Wed Feb 22 2017 04:39:56.586405 - Wireless MCU Update: Existing:244, Required:436
Wed Feb 22 2017 04:39:56.636865 - Basestation Update: MCU ~/Steam/steamapps/common/OpenVR/tools/lighthouse/firmware/lighthouse_tx/archive/htc_2.0/lighthouse_tx_htc_2_0-436-2016-09-20.bin
Wed Feb 22 2017 04:39:56.637087 - Retrieved firmware update 0 percent complete (bSuccess = 1).
Wed Feb 22 2017 04:39:56.637146 - FirmwareWizard entering state Base Station Success (12) with No update necessary (4) 
Wed Feb 22 2017 04:39:58.126740 - FirmwareWizard entering state Device Overview (0) with No update necessary (4) 
Wed Feb 22 2017 04:39:59.702526 - Start Firmware Update (Device Index:3, Recovery:0, ForceAll:0, ForceFix:0).
Wed Feb 22 2017 04:39:59.702860 - No FirmwareUpdate description refresh: using old data.
Wed Feb 22 2017 04:39:59.702892 - 1 Updates scheduled for Device Class: 4
Wed Feb 22 2017 04:39:59.702927 -     1: Watchman Disk Update: Existing:244, Required:436
Wed Feb 22 2017 04:39:59.721959 - FirmwareWizard entering state Base Station Start (10) with No update necessary (4) 
Wed Feb 22 2017 04:40:01.815160 - FirmwareWizard entering state Base Station Wireless Progress (17)
Wed Feb 22 2017 04:40:01.866838 - Wireless MCU Update: Existing:244, Required:436
Wed Feb 22 2017 04:40:01.917217 - Basestation Update: MCU /mnt/vol0/home/madrang/Steam/steamapps/common/OpenVR/tools/lighthouse/firmware/lighthouse_tx/archive/htc_2.0/lighthouse_tx_htc_2_0-436-2016-09-20.bin
Wed Feb 22 2017 04:40:01.917435 - Retrieved firmware update 0 percent complete (bSuccess = 1).
Wed Feb 22 2017 04:40:01.917463 - FirmwareWizard entering state Base Station Success (12) with No update necessary (4) 
Wed Feb 22 2017 04:40:04.615454 - FirmwareWizard entering state Device Overview (0) with No update necessary (4) 

In the logs i saw that SteamVR tries to use "~/Steam/steamapps/common/OpenVR/tools/lighthouse/firmware/lighthouse_tx/archive/htc_2.0/lighthouse_tx_htc_2_0-436-2016-09-20.bin" but it is missing.

SteamVR Tutorial: The robotic core is facing the wrong direction

Your system information

• Steam client version (build number or date): 1487812945
• Distribution (e.g. Ubuntu): Ubuntu 16.10 (64 bit)
• Graphics driver version (run nvidia-settings): 4.5.0 NVIDIA 375.27.10
• Gist for SteamVR System Information: https://gist.github.com/leinardi/92f4ce3e986209d752c383791c16ef08
• Gist for Steam System Information: https://gist.github.com/leinardi/7f9cc3f021a3ef546a884260b8a14f78
• 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:

When the robotic core moves across the room, before asking you to press the Controller buttons, it keep the original orientation and gives you his back.

What I'm seeing:

Expected result:

Steps for reproducing this issue:

1. Start SteamVR Tutorial
2. Follow the Tutorial until you are asked to press the trigger button

SteamVR aborts with untranslated error if a system tray is not found

Your system information

• Steam client version (build number or date): 14896229631
• Distribution (e.g. Ubuntu): Ubuntu 16.10, Elementary OS 0.4
• Graphics driver version (run nvidia-settings): 375.27.13
• Gist for SteamVR System Information: N/A (Crashes before a UI opens)
• 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:

If a system tray application isn't running, SteamVR gives an untranslated message that doesn't makes it obvious what the problem is. The error should explain that a systray is needed.

Steps for reproducing this issue:

1. Close all system tray programs, or use one with limited support (like wingpanel in Elementary OS)
2. Open SteamVR
3. See untranslated error message (attached)

SteamVR does not start at all

System 1: Laptop

• Steam client version (build number or date): Mar 17 2017, 1489791860
• Distribution (e.g. Ubuntu): ubuntu 16.10 64-bit
• Graphics driver version (run nvidia-settings): 375.27.13
• Gist for SteamVR System Information: WTF?
• Opted into Steam client beta?: [Yes/No] Yes
• Opted into SteamVR beta?: [Yes/No] Not possible
• Have you checked for system updates?: [Yes/No] Yes
  Hardware: Nvidia Geforce 1070

System 2: Workstation

• Steam client version (build number or date): Mar 23 2017, 1490314264
• Distribution (e.g. Ubuntu): Debian Jessie
• Graphics driver version (run nvidia-settings): 375.27.13
• Gist for SteamVR System Information: WTF?
• Opted into Steam client beta?: [Yes/No] Yes
• Opted into SteamVR beta?: [Yes/No] Not possible
• Have you checked for system updates?: [Yes/No] Yes
  Hardware: Nvidia Geforce GTX 970

Describtion of my issue:

I expected the Steam-VR menu to appear. But I get only an error window when I click on
View->Start SteamVR (Beta)
The error states:
An error occurred while updating SteamVR (missing executable)
See the Steam support site for more information.

I already cleaned the download cache and tried again. HTC Vive is connected and running under windows without any issues.

SteamVR does not find the lighthouses

Your system information

• Steam client version (build number or date): Mar 30 2017, at 22:20:57
• Distribution (e.g. Ubuntu): Ubuntu 14.04 64b (kernel 4.4.0-31-generic )
• Graphics driver version (run nvidia-settings): 375.27.13
• Gist for SteamVR System Information: https://gist.github.com/awesomebytes/b3e8382640836560099aa79de464427e
• 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 expected SteamVR to find my headset, both controllers and both lighthouses. But it never finds the lighthouses.

Steps for reproducing this issue:

1. Open Steam (Beta)
2. Hit play on SteamVR (Beta)
3. Plug in the Headset (if I plug it previously it gets me in Preparing to launch indefinitely many times).
4. See how the headset and the controllers are detected (the headset shows a grey screen) but the lighthouses are not (and the lighthouses don't change from the green led to another status).

SteamVR hangs/closes when selecting 'Pair Controller'

Your system information

• Steam client version (build number or date): 1487812945
• Distribution (e.g. Ubuntu): Ubuntu 14.0.4
• Graphics driver version (run nvidia-settings): 375.27.13
• Gist for SteamVR System Information: https://gist.github.com/jlarison/9d3ac84862993033374840dc98736add
• 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:

One of my vive controllers is in the 'blue' state when powered on and the other connected on the first try and is in the 'green' state. When I right click on the greyed out controller in SteamVR and select 'Pair Controller', SteamVR either hangs or quits instantly. The same occurs when selecting SteamVR beta > Devices > Pair Controller.

Steps for reproducing this issue:

1. Open SteamVR
2. Right click on an inactive controller
3. Select 'Pair Controller'

Or:

1. Open SteamVR
2. Select 'SteamVR beta' > 'Devices' > 'Pair Controller'

source code for binary missing

You've modified radv and added at least some implementations for extensions like VK_NV_dedicated_allocation or VK_KHX_external_memory. But the necessary patches have not been sent to [email protected]

Please provide the source code and/or work on upstreaming your changes which would then benefit all users of the radv stack.

(Yes, I understand that Mesa's license doesn't force you to release these changes, but I'd hope Valve wants to do what's right. Especially since several Valve developers are already active on the various development lists for this open driver stack.)

SteamVR unable to find HDM

Your system information

• SteamVR Version: 1487744123 ( 2017-02-22 )
• Distribution : Xubuntu 16.04.2 LTS
• Opted into Steam client beta?: Yes
• Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

lanching the steam VR it gives me the following error message screenshot

driver installed using suggested PPA

Tracking is working, also controllers are recognized... and display turn on if I set HDM as extended monitor in X11.

Steps for reproducing this issue:

1. clicking start on SteamVR from Steam
2. waiting

Can't Open SteamVR beta 05/18/17 (SteamVR Home launch date)

Your system information

• Steam client version (build number or date): May 19 2017, at 00:22:30
• Distribution (e.g. Ubuntu): Arch Linux
• Graphics driver version (run nvidia-settings): 381.22
• Gist for SteamVR System Information: N/A - Cannot launch
• Opted into Steam client beta?: [Yes/No] Both
• Opted into SteamVR beta?: [Yes/No] Y - stable branch is not impacted
• Have you checked for system updates?: [Yes/No] Y

Please describe your issue in as much detail as possible:

When opting into SteamVR beta, SteamVR no longer launches.

Steps for reproducing this issue:

1. Opt into beta
2. Attempt to launch SteamVR

Error: Installation path could not be located (110)

Tracking is working but there's no video on the HMD and it's not detected by room setup. Also, room setup is in Spanish for some reason (I'm from Spain but I have everything else set to English).

Before I installed SteamVR I had the extended screen disabled, I suspect that may be related and I don't know how to enable it back. If that's the case, should I try uninstalling Nvidia drivers? Or is there a different way to enable it? (just a guess)

Intel i5 CPU, Nvidia 1070 with vulkan beta driver 375.27.13 on (k)ubuntu 16.04 x64.
Latest SteamVR beta. https://gist.github.com/DiThi/7457a794c9b4c778ce54fb71d8c3e8f4

I haven't updated the lighthouse firmware because they work perfectly on Windows, and it was the update when bluetooth power management finally worked properly. I can update them if you think it may be necessary, though.

edit: It was running with STEAM_RUNTIME_PREFER_HOST_LIBRARIES=0, I just tried without it, with same result.

Steam Store doesn't allow filtering for SteamVR games on Linux

Vendors are currently selling Steam Machines with Vives as optional peripherals, for example: https://www.cyberpowerpc.com/system/Syber_Steam_Machine_Elite

Users who buy such a Steam Machine with the Vive might go to the Steam Store and search for Games with SteamOS/Linux support and with Vive support and get this list as a result: http://store.steampowered.com/search/?vrsupport=101&os=linux

They then need to check for every single game whether this game supports the Vive on Linux, because this information is not available in the Steam Store. Often enough it is not available at all and users need to infer from the lack of information that it won't have Vive support on Linux. This is currently the case for almost all of these games.

That's a very poor user experience. What's the point of a store with filtering functionality if you can't even filter for which games you can play on your current platform with your currently connected peripherals? Why does there need to be a user curated list like https://steamcommunity.com/app/250820/discussions/5/133257959064016658/ instead of this information being available in the actual steam store?

Applications lock up on boot

Your system information

• Steam client version (build number or date): Mar 30 2017 at 22:20:57
• Distribution (e.g. Ubuntu): Arch Linux w/ Gnome 3.22.2
• Graphics driver version (run nvidia-settings): 375.27.15
• Gist for SteamVR System Information: https://gist.github.com/Vash63/1b230516d6d2ea5bfd2533c6c401b0eb
• Opted into Steam client beta?: [Yes/No] Y
• Opted into SteamVR beta?: [Yes/No] Y
• Have you checked for system updates?: [Yes/No] Y

Please describe your issue in as much detail as possible:

Launching the tutorial, Destinations or Serious Sam VR: TSE all fail to send any video to the headset (stuck in SteamVR 'waiting for game' menu). Upon checking desktop, window is visible in Gnome with no content and frozen. Destinations required a kill -9 to stop, the other two required a normal kill -15. stdour/err from Steam shows:

Apr 06 02:09:53 vashnix steam.desktop[13545]: shaders/vulkan/tracked_camera_ps.spv
Apr 06 02:09:53 vashnix steam.desktop[13545]: shaders/vulkan/tracked_camera_undistort_ps.spv
Apr 06 02:09:53 vashnix steam.desktop[13545]: shaders/vulkan/tracked_camera_edgefilter_ps.spv
Apr 06 02:09:53 vashnix steam.desktop[13545]: shaders/vulkan/tracked_camera_reprojection_ps.spv
Apr 06 02:09:53 vashnix steam.desktop[13545]: shaders/vulkan/tracked_camera_lines_ps.spv
Apr 06 02:09:53 vashnix steam.desktop[13545]: DeleteFBOFreeList: Removing 7 FBO objects, total 1
Apr 06 02:10:03 vashnix steam.desktop[13545]: Warning: The game hasn't rendered a frame from us in over 10 seconds
Apr 06 02:10:14 vashnix steam.desktop[13545]: Warning: The game hasn't rendered a frame from us in over 10 seconds
Apr 06 02:10:24 vashnix steam.desktop[13545]: Warning: The game hasn't rendered a frame from us in over 10 seconds

This is with Destinations, output from the other two applications is similar. Desktop Vulkan applications such as Mad Max or Serious Sam Fusion work without issue.

Steam segfault when starting SteamVR 1487886215

Archlinux, RX 480

When started with STEAM_RUNTIME=0 steam it doesn't crash. With the runtime enabled, steam crashes when start steamvr, but vrmonitor and vrcompositor keep running and working.

steamvr system report
https://gist.github.com/ChristophHaag/e5ba90319a9d706a037a56e8b853a591

backtrace:

Thread 15 "CIPCServer::Thr" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xe8febb40 (LWP 15818)]
0xf7c8b3a5 in pthread_join () from /usr/lib32/libpthread.so.0
(gdb) bt
#0  0xf7c8b3a5 in pthread_join () from /usr/lib32/libpthread.so.0
#1  0xd5c21431 in vortex::CVortexThread::~CVortexThread() ()
   from /home/chris/.local/share/Steam/SteamApps/common/SteamVR/drivers/lighthouse/bin/linux32/driver_lighthouse.so
#2  0xd5c1d30f in vortex::CLighthouseUsbThread::~CLighthouseUsbThread() ()
   from /home/chris/.local/share/Steam/SteamApps/common/SteamVR/drivers/lighthouse/bin/linux32/driver_lighthouse.so
#3  0xd5c18b01 in vortex::CLighthouseThreadBase::Stop() ()
   from /home/chris/.local/share/Steam/SteamApps/common/SteamVR/drivers/lighthouse/bin/linux32/driver_lighthouse.so
#4  0xd5c18c90 in vortex::CLighthouseInput::Stop() () from /home/chris/.local/share/Steam/SteamApps/common/SteamVR/drivers/lighthouse/bin/linux32/driver_lighthouse.so
#5  0xd5c18d91 in vortex::CLighthouseInput::CConnection::Disconnect() ()
   from /home/chris/.local/share/Steam/SteamApps/common/SteamVR/drivers/lighthouse/bin/linux32/driver_lighthouse.so
#6  0xd5c18ede in vortex::CLighthouseInput::CConnection::~CConnection() ()
   from /home/chris/.local/share/Steam/SteamApps/common/SteamVR/drivers/lighthouse/bin/linux32/driver_lighthouse.so
#7  0xd5b4121f in CWatchdogConnectionMonitor::~CWatchdogConnectionMonitor() ()
   from /home/chris/.local/share/Steam/SteamApps/common/SteamVR/drivers/lighthouse/bin/linux32/driver_lighthouse.so
#8  0xd5b40a39 in CWatchdogDriver_Lighthouse::Cleanup() ()
   from /home/chris/.local/share/Steam/SteamApps/common/SteamVR/drivers/lighthouse/bin/linux32/driver_lighthouse.so
#9  0xd68b8c84 in CWatchdogTrackedDeviceProvider_Latest::Cleanup() () from /home/chris/.local/share/Steam/SteamApps/common/SteamVR/bin/vrclient.so
#10 0xd686195a in CDriverManager::CleanupDriver(CDriverManager::HmdDriver_t*) () from /home/chris/.local/share/Steam/SteamApps/common/SteamVR/bin/vrclient.so
#11 0xd686407f in CDriverManager::Cleanup() () from /home/chris/.local/share/Steam/SteamApps/common/SteamVR/bin/vrclient.so
#12 0xd679f470 in CHmdSystemLatest::Cleanup() () from /home/chris/.local/share/Steam/SteamApps/common/SteamVR/bin/vrclient.so
#13 0xe8e330c4 in VR_ShutdownInternal () from /home/chris/.local/share/Steam/ubuntu12_32/libopenvr_api.so
#14 0xea067702 in ?? () from /home/chris/.local/share/Steam/ubuntu12_32/steamclient.so
---Type <return> to continue, or q <return> to quit---
#15 0xe9decbb4 in ?? () from /home/chris/.local/share/Steam/ubuntu12_32/steamclient.so
#16 0xe9c24383 in ?? () from /home/chris/.local/share/Steam/ubuntu12_32/steamclient.so
#17 0xe9ce490e in ?? () from /home/chris/.local/share/Steam/ubuntu12_32/steamclient.so
#18 0xe9727458 in ?? () from /home/chris/.local/share/Steam/ubuntu12_32/steamclient.so
#19 0xe9ce4008 in ?? () from /home/chris/.local/share/Steam/ubuntu12_32/steamclient.so
#20 0xe9725f42 in ?? () from /home/chris/.local/share/Steam/ubuntu12_32/steamclient.so
#21 0xe972871a in ?? () from /home/chris/.local/share/Steam/ubuntu12_32/steamclient.so
#22 0xe9729546 in ?? () from /home/chris/.local/share/Steam/ubuntu12_32/steamclient.so
#23 0xeff15e30 in SteamThreadTools::CThread::ThreadExceptionWrapper(void*) () from /home/chris/.local/share/Steam/ubuntu12_32/libtier0_s.so
#24 0xeff1421b in ?? () from /home/chris/.local/share/Steam/ubuntu12_32/libtier0_s.so
#25 0xeff144ef in CatchAndWriteMiniDumpExForVoidPtrFn () from /home/chris/.local/share/Steam/ubuntu12_32/libtier0_s.so
#26 0xeff14541 in CatchAndWriteMiniDumpForVoidPtrFn () from /home/chris/.local/share/Steam/ubuntu12_32/libtier0_s.so
#27 0xeff18ac1 in SteamThreadTools::CThread::ThreadProc(void*) () from /home/chris/.local/share/Steam/ubuntu12_32/libtier0_s.so
#28 0xf7c8a301 in start_thread () from /usr/lib32/libpthread.so.0
#29 0xf7bb446e in clone () from /usr/lib32/libc.so.6

Keyboard and mouse disabled on exit

Your system information

• Steam client version (build number or date): 1487812945
• Distribution (e.g. Ubuntu): Gentoo
• Graphics driver version (run nvidia-settings): 375.27.10
• Gist for SteamVR System Information: https://gist.github.com/valentindavid/65e6ce45fffa02e2c1ebd939e18083ec
• Opted into Steam client beta?: [Yes/No] Yes
• Opted into SteamVR beta?: [Yes/No] Yes
• Have you checked for system updates?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

After exiting SteamVR, sometimes both my keyboard and my mouse stop working. It does not systematically happen. When it happens, it disables both. I then have to unplug and re-plug.

My mouse is a Roccat Nyth and my keyboard a Roccat Suora. I have disabled user access to hidraw of the keyboard and the mouse through udev (needed to configure them). However SteamVR still manages to disable them.

NVidia Vulken driver version 375.27.14

Can anyone confirm that the 375.27.14 version of the driver works as well as 375.27.13 does?

375.27.13 seems to be impossible to download directly from NVidia at this point. Thus, it would be good to know if 375.27.14 is expected to work.

If nothing else, it'd be awesome to see a mention of 375.27.14 in the Readme of this repo!

SteamVR thinks I have two left hands (left hand icon on both controllers)

https://gist.github.com/ali1234/f8fe8be420f986ca110de738da301b9f

Your system information

• Steam client version (build number or date): Feb 27 2017
• Distribution (e.g. Ubuntu): Ubuntu 16.04.2
• Graphics driver version (run nvidia-settings): 375.27.10
• Gist for SteamVR System Information: https://gist.github.com/ali1234/f8fe8be420f986ca110de738da301b9f
• 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:

SteamVR thinks I have two left hands - the left hand icon is shown on both virtual controllers.

Steps for reproducing this issue:

1. Be in the SteamVR menu space.
2. Wait for controllers to sleep.
3. Pick up controllers, one in each hand.
4. Turn on controller in right hand.
5. Turn on controller in left hand.

Result: http://i.imgur.com/x3oEWB0.png

vrcmd bash-script contains ms-dos CR

/SteamVR/bin$ ./vrcmd
bash: ./vrcmd: /bin/bash^M: bad interpreter: No such file or directory
That's a ms-dos carriage return there. Yuck!
It's fixed easily enough, tough:
SteamVR/bin$ flip -ub vrcmd

"Pair controller" crashes

Your system information

• Steam client version (build number or date): 1493162727
• Distribution (e.g. Ubuntu): Ubuntu 17.04
• Graphics driver version (run nvidia-settings): 381.09
• Gist for SteamVR System Information: https://gist.github.com/tcriess/89c8934b769968807062a4671e32618c
• 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:

When trying to pair the tracker by using the "pair controller" menu entry, nothing happens (the problem with the trackers is that they are easily un-paired unintentionally, thus essentially bricking them). In syslog the last entry usually is something like "vrmonitor[8893]: segfault at 7f7551c9513e ip 00007f75111d0640 sp 00007ffc44009cd8 error 4 in libQt5Core.so.5[7f751100e000+533000]", so I assume a crash somewhere.
Possible regression of issue #33

Steps for reproducing this issue:

1. start SteamVR
2. select "Devices > Pair Controller"

Can't open or uninstall SteamVR

Your system information

• Steam client version (build number or date): Apr 19 2017, at 00:37:25 (beta) and Mar 22 2017, at 23:45:04
• Distribution (e.g. Ubuntu): 16.04
• Graphics driver version (run nvidia-settings): 381.09 (beta)
• Gist for SteamVR System Information: Can't open it
• Opted into Steam client beta?: [Yes/No] Yes
• Opted into SteamVR beta?: [Yes/No] Yes
• Have you checked for system updates?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

SteamVR fails to open, the "going to launch game" dialog is always open. This happened before so I tried to uninstall and reinstall it. I can't uninstall it, tried both in Steam beta and normal.

I'm going to install Steam from scratch, I'm just filing this issue for the next person that has this problem, in case there's a quicker way. And of course for following the issue itself.

SteamVR Tutorial: No controller animation and wrong controller color

Your system information

• Steam client version (build number or date): 1487812945
• Distribution (e.g. Ubuntu): Ubuntu 16.10 (64 bit)
• Graphics driver version (run nvidia-settings): 4.5.0 NVIDIA 375.27.10
• Gist for SteamVR System Information: https://gist.github.com/leinardi/92f4ce3e986209d752c383791c16ef08
• Gist for Steam System Information: https://gist.github.com/leinardi/7f9cc3f021a3ef546a884260b8a14f78
• 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:

Vive Controllers are blue and show no animation when you press the trigger or swipe your finger across the trackpad button.

What I'm seeing:

Expected result:

Steps for reproducing this issue:

1. Start SteamVR Tutorial
2. Follow the Tutorial
3. Look at the controllers, press the trigger and swipe your finger across the trackpad button

SteamVR Home freezes system

System information

• Steam client version (build number or date): 25. April 2017
• Distribution (e.g. Ubuntu): Debian Testing
• Graphics driver version (run nvidia-settings): 375.27.13
• Gist for SteamVR System Information: https://gist.github.com/CarpeNecopinum/3854b43c57e97c512b58bc875b0f302b
• Opted into Steam client beta?: No
• Opted into SteamVR beta?: Yes
• Have you checked for system updates?: Yes

Issue Details:

Starting SteamVR yields the "vrclient shared lib not found" error. However, SteamVR and SteamVR Home start. One can look around, interact with the control tutorial (inside the Home) etc. at good framerates.

After ~3 - 30 seconds, everything attached to the same GPU as the Vive freezes (i.e. the Home App, the desktop).

SSHing in from another machine and killing all vr-related processes makes the system usable again. When I start SteamVR afterwards (without a full reboot of the computer), tracking works fine, but the Vive only shows a pattern of very dim red and black blocks (which are not affected by tracking).

VR-related logs at https://gist.github.com/CarpeNecopinum/fbd9979859e1881c9fe20b8d1cc3420a

No similar issues occur with self-written (Vulkan) VR-Apps.

Steps for reproducing this issue:

1. Update SteamVR to beta
2. Run SteamVR
3. Put on the Vive
4. Look around / interact with the Home App for 3 - 30 seconds

Update 1: The "vrclient shared lib not found" error does not occur with the SteamVR beta build of May 26. The freezing issues however are not fixed.

Update 2: Opting into Steam client beta prevents freezing of other applications on the same GPU. The screen inside the Vive remains useless until reboot, though.

Update 3: This appears to be related to #1 disabling reprojection as danginsburg suggested fixes the freeze issues.

Fedora 25 - room setup crashs

Your system information

• Steam client version (build number or date): SteamVR Version 2017-04-28 (1493337050)
• Distribution (e.g. Ubuntu): Fedora 25 (64 bit)
• Graphics driver version (run nvidia-settings): 375.39
• Gist for SteamVR System Information: https://gist.github.com/phobeus81/7b39ac5258373eaf4cd18fb3056f2dbd
• Opted into Steam client beta?: No
• Opted into SteamVR beta?: Yes
• Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

The Steam VR application can be launched via tools and seems to be starting up correctly and able to detect the lighthouses and controllers as well as the head device. The compositor is starting and showing screen.

When launching the steam vr room setup however, just a window is opened hangs for a while and then closing. When launching the steam vr room setup from console, a seg fault occurs. Thus it is not possible to setup the room anymore.

From the console I executed the room setup using strace and uploaded the dump to https://gist.github.com/phobeus81/e20c39bf7cc396ac21df91ae56550b9c

Steps for reproducing this issue:

1. Launch Steam VR
2. Select "Run Room Setup" from the menu

Dark rendering with reprojection in Destinations/SteamVR Home on radv

Looks like there isn't an issue yet for tracking this problem.

This has long, probably always, been happening on my RX 480 with radv.

Here is a video I made some time ago in Destinations:
https://www.youtube.com/watch?v=qQ6EHllQJJg
As soon as reprojection kicks in, the rendering goes dark.

I think this only happens in Destinations - and now SteamVR Home.

config path could not be located

• Steam client version (build number or date): Feb 21 2017 at 20:24:31
• Distribution (e.g. Ubuntu): debian/testing
• Graphics driver version (run nvidia-settings): 275.27.10
• Gist for SteamVR System Information: https://gist.github.com/voidplayer/49f7f91632760ac98a179ac7626c27e5
• Opted into Steam client beta?: Yes
• Opted into SteamVR beta?: Yes
• Have you checked for system updates?: [Yes/No]

Please describe your issue in as much detail as possible:

When I start stamvr it shows: "steamVR failed to initalized for unknown reasons. (error: config path could not be located(111))"

The headset in the status goes green, but when I try to do the room set up, the headset is off

Dmesg shows:

[Wed Feb 22 20:58:11 2017] show_signal_msg: 87 callbacks suppressed
[Wed Feb 22 20:58:11 2017] vrcompositor[2138]: segfault at a8 ip 00007f1052885d42 sp 00007ffc37459878 error 4 in libnvidia-glcore.so.375.27.10[7f10514a3000+13ef000]
[Wed Feb 22 21:11:15 2017] vrmonitor[2082]: segfault at 1 ip 00007f4c5ec54018 sp 00007ffef02dfd80 error 4 in libudev.so.0.13.0[7f4c5ec50000+c000]
[Wed Feb 22 21:11:21 2017] vrcompositor[2658]: segfault at a8 ip 00007f22a07efd42 sp 00007fff1cb7ca08 error 4 in libnvidia-glcore.so.375.27.10[7f229f40d000+13ef000]
[Wed Feb 22 21:14:43 2017] vrmonitor[2602]: segfault at 7fbe9ac4add0 ip 00007fbd9d5dac44 sp 00007fff117cd450 error 4 in libQt5Core.so.5[7fbd9d31c000+533000]

VR Tutorial: Left eye has very low resolution

• Steam client version (build number or date): 2017-02-23
• Distribution (e.g. Ubuntu): Kubuntu 16.10
• Graphics driver version (run nvidia-settings): 375.27.10
• Gist for SteamVR System Information: https://gist.github.com/aronschatz/7dc58af816e21b649f17981bb8f31346
• 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:

SteamVR Tutorial is very low resolution in left eye.

Steps for reproducing this issue:

1. Start SteamVR
2. Start VR Tutorial from SteamVR console
3. Close left eye, see the proper resolution in the right eye.
4. Close right eye, see very low resolution in the left eye.

Destinations Crashes after a short while

Using the Linux SteamVR beta with the Nvidia Vulkan PPA on Kubuntu 16.10, the VR setup all works fine. Room setup works and once the HMD is started, you can see the default VR space and chaperoned with the controllers just fine. More specs: i7-3770K and a 970GTX. On Windows, VR works good enough (as a comparison).

Starting the VR tutorial does not work, it dies before running in VR.

Destinations starts and begins to chug and then takes down the entire system. The HMD picture freezes and then the computer slowly dies.

I'm happy to provide any further needed details. I'm glad to see Linux support progressing.

Launching steamVR after launching Serious Sam VR shows a never-ending updating dialog

Your system information

• Steam client version (build number or date): 24 feb 03...
• Distribution (e.g. Ubuntu): debian/testing
• Graphics driver version (run nvidia-settings): 375.27.13
• Gist for SteamVR System Information: the same as number #7 but I changed my nvidia 950 to a nvidia 1060
• 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:

SteamVr doesnt try to update, but after launching serious sam VR, the next time you try to launch steamVR it shows the updating dialog:

"Updating SteamVR" and "preparing to launch SteamVR" with a progress dialog that does not progress

I tried to remove it, to verify integrity and all kind of things, but it doesnt work.

I also tried to opt out of the steam client beta, rm -rf ~/.local/share/Steam/SteamApps/common/SteamVR then verified integrity of the files to reinstall, then in the steamvr properties disabled cloud sync and opted into the beta again. But it only downloads the feb 24 built

I also have issue #16 so I cant really finish configuring the vive

I believe last version is from March 1st, so it should try to update

"Headset not detected" on Ubuntu 17.04 (GNOME)

Your system information

• Steam client version (build number or date): Apr 25, 2017 22:46:35
• Distribution (e.g. Ubuntu): Ubuntu GNOME 17.04
• Graphics driver version (run nvidia-settings): 381.09
• Gist for SteamVR System Information: https://gist.github.com/jessedubord/81703472551990a4085a3f715ce8949a
• 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've installed Nvidia proprietary driver 381.09, Steam client beta, and SteamVR beta. After starting SteamVR, the status window appears saying "Not Ready". The vrmonitor window above it says in red: "Headset not detected", with some text, then prompts me to "Reboot Headset". After I click Reboot Headset, it says: "Rebooting Vive.. Service Status: Failed."

HTC Vive indicator LED on the left-side of the headset shows red all the while, with the exception of PC shutdown, in which it turns green for a second or so.

I would use the Nvidia 375 Vulkan driver, but the PPA mentioned on the SteamVR-for-Linux github page doesn't have a package for the Zesty 17.04 release of Ubuntu.

Steps for reproducing this issue:

1. Install Ubuntu GNOME 17.04, update system, install Nvidia 381.09 drivers from PPA, install Steam client[beta], and install SteamVR [beta]
2. Run SteamVR

SteamVR Tutorial: Trackpad click not detected

Your system information

• Steam client version (build number or date): 1487812945
• Distribution (e.g. Ubuntu): Ubuntu 16.10 (64 bit)
• Graphics driver version (run nvidia-settings): 4.5.0 NVIDIA 375.27.10
• Gist for SteamVR System Information: https://gist.github.com/leinardi/92f4ce3e986209d752c383791c16ef08
• Gist for Steam System Information: https://gist.github.com/leinardi/7f9cc3f021a3ef546a884260b8a14f78
• 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:

Vive Controllers track button click not detected. This make impossible to complete the tutorial.

Perhaps related to #17.

Steps for reproducing this issue:

1. Start SteamVR Tutorial
2. Follow the Tutorial
3. Press the trackpad button when asked

Nvidia 381.09 beta driver supported?

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?

Headset firmware update: Source is invalid

Your system information

• Steam client version (build number or date): 1487812945
• Distribution (e.g. Ubuntu): Gentoo
• Graphics driver version (run nvidia-settings): 375.27.13
• Gist for SteamVR System Information: https://gist.github.com/valentindavid/0e09721a8fc99cc6306bea75d1dd1a10
• 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:

When trying to update the headset I get the following error.

Tue Mar 07 2017 18:20:58.866860 - Display Update: Existing:2097478, Required:2097504
Tue Mar 07 2017 18:20:58.917543 - Headset Display Update: /home/valentin/.local/share/Steam/steamapps/common/SteamVR/tools/lighthouse/bin/linux64/vivetools app /home/valentin/.local/share/Steam/steamapps/common/SteamVR/tools/lighthouse/firmware/htc/APP_0000000000200160.bin
Tue Mar 07 2017 18:20:59.585959 - Switch to IAP mode... wait for a while
Source is invalid
Failed
Tue Mar 07 2017 18:21:06.704618 - Failed with exit code: 24. Attempting retry: 1

I removed APP_0000000000200160.bin and recheck SteamVR files integrity. That did not help.

radv performance issues

Hardware: i5 6500, RX 480

I've made a thread here, but didn't really get a definite reply:
https://steamcommunity.com/app/250820/discussions/5/133257959064945402/

tl;dr: Everything runs bad and has missed frames.

Examples:
Destinations: https://i.imgur.com/Gj7ly7U.png
Dota 2 VR Hub: https://i.imgur.com/Ai7ST5M.png
SteamVR Unity example scene from the plugin: https://i.imgur.com/aa2sryH.png
edit: These screenshots show interleaved reprojection off, but turning it on makes no difference.

Only the SteamVR environment itself shows no missing frames, but it isn't all smooth either.

Serious Sam VR TFE with default setting runs at ~45 FPS and is not smooth either.

According to Plagman it ran better in development but something regressed.

I hope this gets fixed soon, because as it is now it doesn't really feel usable.

Room Setup instantly crashes

Running Room Setup shows the window for a second, then closes.

Log:

Found path: /home/oden/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64/steamvr_room_setup
Mono path[0] = '/home/oden/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64/steamvr_room_setup_Data/Managed'
Mono path[1] = '/home/oden/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64/steamvr_room_setup_Data/Mono'
Mono config path = '/home/oden/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64/steamvr_room_setup_Data/Mono/etc'
Preloaded 'ScreenSelector.so'
Preloaded 'libopenvr_api.so'

Big Screen VR menu not available

Your system information

• Steam client version (build number or date): Jan 19 2017, at 01:23:20
• Distribution (e.g. Ubuntu): Archlinux
• Graphics driver version (run nvidia-settings): 375.27.10
• Gist for SteamVR System Information: https://gist.github.com/CodeMichael/bf039a65ac9b121d80465fd32f7a8a2e
• 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:

The VR Big Screen menu doesn't appear when hitting the menu button on the controllers. The system bar does appear: Clock, Volume, Settings, System.

Steps for reproducing this issue:

1. Launch Steam VR
2. Press the menu button on the controller
3. No Big Screen game menu apppears.

vrcompositer crashes on illegal instruction

Your system information

• Steam client version (build number or date): 1487812945 (Built: Feb 23 2017, at 00:38:08)
• Distribution (e.g. Ubuntu): Gentoo
• Graphics driver version (run nvidia-settings): radv from valve git
• Gist for SteamVR System Information: https://gist.github.com/anonymous/c9e6862d121190e676c24a1de9b84655
• Opted into Steam client beta?: Yes
• Opted into SteamVR beta?: Yes
• Have you checked for system updates?: Yes
  My processor information if it is intresting:
  https://gist.github.com/anonymous/511bf6d822822aa2f3902489c5c1bffc

Please describe your issue in as much detail as possible:

I expect that SteamVR should start and work (+-beta), instead vrcompositor crashed on an illegal instruction upon start (a few seconds in, after compiling vulkan shaders?).

vrcompositer crashes when launching SteamVR.

Running it within gdb and looking at the backtrace it seems like the ssse3 instruction pshufb is used in the stb library.

(gdb) bt
#0 0x000000000053bbde in stbi__parse_zlib(stbi__zbuf*, int) ()
#1 0x0000000000541dd5 in stbi_zlib_decode_malloc_guesssize_headerflag ()
#2 0x000000000054223e in stbi__parse_png_file(stbi__png*, int, int) ()
#3 0x00000000005434b4 in stbi__load_flip(stbi__context*, int*, int*, int*, int) ()
#4 0x00000000005455a1 in stbi_load_from_memory ()
#5 0x0000000000453160 in CGenericResources::LoadGCImage(std::string*) ()
#6 0x000000000046927e in CGenericResources::Init(vr::IGraphicsDevice::CreateStruct_t const&) ()
#7 0x0000000000449b95 in vr::CHmdDistort::Initialize(vr::CVRNotificationManager*, CVRSharedState*, void*, bool) ()
#8 0x00000000004704f5 in CVRCompositor::Init() ()
#9 0x0000000000473235 in RealMain(unsigned int, ParsedArguments_t&) ()
#10 0x0000000000440066 in main ()

...
0x000000000053bbd4 <+1796>: add %rsi,%r11
0x000000000053bbd7 <+1799>: xor %r10d,%r10d
0x000000000053bbda <+1802>: pxor %xmm1,%xmm1
=> 0x000000000053bbde <+1806>: pshufb %xmm1,%xmm0
0x000000000053bbe3 <+1811>: add $0x1,%r10d
0x000000000053bbe7 <+1815>: movdqa %xmm0,(%r11)
0x000000000053bbec <+1820>: add $0x10,%r11
...

In kernel log:
traps: vrcompositor[5623] trap invalid opcode ip:53bbde sp:7ffd6f5f7a60 error:0
in vrcompositor[400000+2a9000]

Steps for reproducing this issue:

1. Install steam on a computer with a non-ssse3 cpu, such as AMD Phenom(tm) II X4 955 Processor
2. Install SteamVR beta for Linux
3. Start SteamVR
4. Notice 306 error message
5. Notice trap invalid opcode in kernel log

NVIDIA driver v375.27.12 breaks rendering the SteamVR default environment

Your system information

• Steam client version (build number or date): 1484790260 (Jan 19 2017, at 01:23:20)
• Distribution (e.g. Ubuntu): Arch Linux
• Graphics driver version (run nvidia-settings): 375.27.12
• Gist for SteamVR System Information: https://gist.github.com/kkriehl/97a63ccee6b8aec20506d68aba672b8f
• Opted into Steam client beta?: No
• Opted into SteamVR beta?: Yes
• Have you checked for system updates?: Yes

Steps for reproducing this issue:

1. Install the new NVIDIA beta drivers from https://developer.nvidia.com/vulkan-driver
2. Start SteamVR and put on your HMD
3. See a black screen with colored lines in the center instead of the SteamVR environment (see attached picture)

Destinations works ok but does sometimes show the visually also broken SteamVR loading environment. A Unity test build shows the same visual glitches in the Unity loading screen. After the scene has been loaded it renders correctly.

Vive controllers stutter in Dota 2

Your system information

• Steam client version (build number or date): May 12 2017
• Distribution (e.g. Ubuntu): Archlinux
• Graphics driver version (run nvidia-settings): radv git, RX 480
• Gist for SteamVR System Information: https://gist.github.com/ChristophHaag/561bdce3e47eb5ee4aa87138d1cb4f29
• Opted into Steam client beta?: [Yes/No] Yes
• Opted into SteamVR beta?: [Yes/No] Yes
• Have you checked for system updates?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

Dota 2 VR Hub itself runs smoothly at 90 FPS without reprojection.
Only the controllers visibly stutter when you move them through the air. If I had to guess I'd say their position is only updated every second frame.
This doesn't happen in other SteamVR apps, just Dota 2 VR Hub.
I believe this has always been happening.

Error: Shared IPC Compositor Connect Failed (306)

Your system information

• Steam client version (build number or date): Built: Feb 23 2017, at 00:38:08
• Distribution (e.g. Ubuntu): Ubuntu 16.04
• Graphics driver version (run nvidia-settings): 375.27.10
• Gist for SteamVR System Information: https://gist.github.com/Kalman98/af18cfc4643c1cb84fac2e3df60df984
• Opted into Steam client beta?: Yes
• Opted into SteamVR beta?: Yes
• Have you checked for system updates?: Yes

vrclient_steam.txt: https://gist.github.com/Kalman98/011ea211060355416c7c97fd3dd23ad7
vrclient_steamvr_room_setup.txt: https://gist.github.com/Kalman98/6f2bf09e5d4d76c254e4f9c2944a6317
vrclient_steamvr_tutorial.txt: https://gist.github.com/Kalman98/248c71432a61dcbb5e441418f6e62286
vrclient_vrcompositor.txt: https://gist.github.com/Kalman98/23675ea1074d846ef0ff78dd87a41432
vrclient_vrmonitor.txt: https://gist.github.com/Kalman98/48cc8160248e3c4c32e759c0d801fe33
vrcompositor.txt: https://gist.github.com/Kalman98/9327d1b8506658cf7a552759e43c342a
vrmonitor.txt: https://gist.github.com/Kalman98/88d22643c8db447b80864000592b5429
vrserver.txt: https://gist.github.com/Kalman98/1286883ba42ca6ce6f96a0c51d8c8547

Please describe your issue in as much detail as possible:

I am using the null driver.
My steamvr.vrsettings config: https://gist.github.com/Kalman98/c069ac11efe97a720c1484463e5124bb

It gives me the error stated.

Steps for reproducing this issue:

1. Enable null driver.
2. Start SteamVR.

"Headset Off"

I launch SteamVR by going to the Library and double-clicking "SteamVR [beta]".
The top right "VR" icon does not appear to do anything.

I get an "Error Starting SteamVR" window, with the message:
"SteamVR is not available because a supported headset was not detected."

For standing only, the room setup utility says "Headset Off".
For room scale, the same text, plus "Controller Off" twice.

The status window says "Connect Failed".

The status window shows green for everything except one controller.
That controller's led is blue.

I've followed the procedure to update the base stations' firmware.
It worked for one, not for the other.
(No matter how many tries and variations of USB port, order, etc.)

Using Steam beta and SteamVR beta.
gpu: Gigabyte GeForce GTX 1060 Windforce OC 6G
gpu driver: NVIDIA 375.27.10
cpu: Intel i7-4770K, s1150
hdd: 250GB SSD Samsung 840 EVO
mem: 2x8GB DDR3 Corsair Vengeance LP 1600
distro: Linux Mint 18

VR Tutorial: Closing the system menu does not resume the tutorial

Your system information

• Steam client version (build number or date): 1489101908
• Distribution (e.g. Ubuntu): Gentoo
• Graphics driver version (run nvidia-settings): 375.27.13
• Gist for SteamVR System Information: https://gist.github.com/valentindavid/369e8bac13dbd80a95bf36bac50a5541
• 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:

When running the tutorial, the core asks to press to system menu to bring the dashboard. Then it asks to press it again to close it. Then the core stands there saying nothing like an idiot. I suppose the tutorial is not finished or it would be a terrible ending.

Can't run Room Setup

Your system information

• Steam client version: Mar 30 2017, at 22:20:57
• Distribution: Debian Stretch ('testing')
• Graphics driver version: 375.39
• Gist for SteamVR System Information: https://gist.github.com/javl/6e4fa8049cb9318b68e67c56611b97df (Truncated the logs to a single run directly after installing SteamVR (beta). Only 1 lighthouse connected.)
• Opted into Steam client beta?: Yes
• Opted into SteamVR beta?: Yes
• Have you checked for system updates?: Yes
• Hardware firmware: latest (installed using Windows)

Disabled HTC VIve display using xrandr --output HDMI-0 --off
nvidia-settings confirms the screen status is disabled, but the system report says Display Mode: Extended Display?

Please describe your issue in as much detail as possible:

Expected:

Starting the Room Setup or Tutorial programs to setup the playing area.

Actual result:

A window opens from a split second, SteamVR menu shows

Starting SteamVR Room Setup
(Unresponsive) SteamVR Room Setup

and the window closes. Same for the tutorial.
When starting SteamVR I do get to see the 3D environment (both on the desktop and in the headset) showing the lighthouses.

Steps to reproduct:

1. Start SteamVR by selecting it in the library and clicking the Play button.
2. After connecting, start Room Setup or Tutorial from the SteamVR menu.

Serious Sam VR TFE: Completely freezing the system

Your system information

• Steam client version (build number or date): 1487812945
• Distribution (e.g. Ubuntu): Ubuntu 16.10 (64 bit)
• Graphics driver version (run nvidia-settings): 4.5.0 NVIDIA 375.27.10
• Gist for SteamVR System Information (took yesterday, can't take an updated version since isn't starting anymore): https://gist.github.com/leinardi/92f4ce3e986209d752c383791c16ef08
• Gist for Steam System Information: https://gist.github.com/leinardi/7f9cc3f021a3ef546a884260b8a14f78
• 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:

It seems that the game completely freeze my system. It happened two out of two time that I started it: I went in the settings menu to change some graphical options and, after applying the changes, the entire OS completely froze. I had to reboot using the Magic SysRq + S-U-B.

Not sure if this issue should be reported here on directly to Croteam.

Steps for reproducing this issue:

1. Start SteamVR
2. Start Serious Sam VR
3. Open the settings and start the autodetection of the graphical settings or manually change and apply some setting.

SteamVR won't open.

My system information

• Steam client version: API: v017
• Distribution (e.g. Ubuntu): Ubuntu 16.04
• Opted into Steam client beta?: No
• Have you checked for system updates?: Yes

Full System Info https://gist.github.com/assumptionsoup/5e8d18cdedbdb6d6673fde36291c2ecb

The issue:

I click on the SteamVR button. A window pops up saying "Preparing to launch Steam VR". The window goes away. Steam VR does not launch. The process is running though (several of them in fact, because I pressed the button more than once):

>>> ps -aux | grep steam

jordan    2598  0.0  0.0  92344 22772 pts/0    S+   18:56   0:00 gvfs-open steam://startvrmode
jordan    3016  0.0  0.3 362820 108116 pts/0   S+   18:57   0:00 /home/jordan/.steam/ubuntu12_32/steam
jordan    3017  0.0  0.0  60808 22080 pts/0    S+   18:57   0:00 /bin/sh -c "/home/jordan/.steam/steam/steamapps/common/SteamVR/dl_ovr_runtime.sh"
jordan    3018  0.0  0.0  74828 24728 pts/0    S+   18:57   0:00 /bin/bash /home/jordan/.steam/steam/steamapps/common/SteamVR/dl_ovr_runtime.sh
jordan    3020  0.0  0.0  60944 22036 pts/0    S+   18:57   0:00 /bin/sh /usr/bin/xdg-open steam://startvrmode
jordan    3022  0.0  0.0  92344 22628 pts/0    S+   18:57   0:00 gvfs-open steam://startvrmode
jordan    3133  0.0  0.3 367220 108440 pts/0   S+   19:03   0:00 /home/jordan/.steam/ubuntu12_32/steam
jordan    3134  0.0  0.0  60808 22028 pts/0    S+   19:03   0:00 /bin/sh -c "/home/jordan/.steam/steam/steamapps/common/SteamVR/dl_ovr_runtime.sh"
jordan    3135  0.0  0.0  74828 24672 pts/0    S+   19:03   0:00 /bin/bash /home/jordan/.steam/steam/steamapps/common/SteamVR/dl_ovr_runtime.sh
jordan    3137  0.0  0.0  60944 22040 pts/0    S+   19:03   0:00 /bin/sh /usr/bin/xdg-open steam://startvrmode
jordan    3139  0.0  0.0  92344 22640 pts/0    S+   19:03   0:00 gvfs-open steam://startvrmode
jordan    3191  0.0  0.0  21296   972 pts/2    S+   19:04   0:00 grep --color=auto steam

Running this process in the terminal outputs:

>>> /usr/bin/xdg-open steam://startvrmode
Running Steam on ubuntu 16.04 64-bit
STEAM_RUNTIME is enabled automatically

Then returns.

Steps for reproducing this issue:

I installed SteamVr via the first popup when opening steam. I tried installing steam from both ubuntu repositories and from the .deb file. All versions have this issue.

Installation path could not be located (111)

Your system information

• Steam client version (build number or date): Feb 21, 2017
• Distribution (e.g. Ubuntu): Arch Linux
• Opted into Steam client beta?: [Yes/No] Client and SteamVR
• Have you checked for system updates?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

When starting SteamVR the compositor shows up correctly and displays full what the headset should be seeing (controllers can be seen as tracked through this window) however the headset display does not turn on.

Shortly after the SteamVR Compositor window appears, the error message "SteamVR failed to initialized (typo btw) for unknown reasons. (Error: Config path could not be located (111))" shows up. The indicator light on the side of the headset is green, but its display is off.

Room setup will crash immediately after launching.

I've tried running with the Steam runtime with nvidia (378.13-2) and nvidia-beta (378.13-1) drivers, but both give the same issue.

Log during error.

My setup consists of two 1440p monitors over DVI with the headset running over HDMI. I have a Nvidia GTX 970.

Steps for reproducing this issue:

1. Start SteamVR Beta Client
2. Watch as SteamVR Compositor appears and works correctly (albeit displaying 1080p on a 1440p monitor)
3. Error message with title "Error Starting SteamVR" appears stating: "SteamVR failed to initialized for unknown reasons. (Error: Config path could not be located (111))"

GetControllerState from FnTable always zeroes VRControllerState_t struct

Your system information

• Steam client version (build number or date): 1488992261
• Distribution (e.g. Ubuntu): Gentoo
• Graphics driver version (run nvidia-settings): 375.27.13
• Gist for SteamVR System Information: https://gist.github.com/valentindavid/64b4ee1ebdca82af92cdf6d4f0bedb10
• 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:

GetControllerState from FnTable:IVRSystem_015 (C API) always return with a zeroed VRControllerState_t struct when GetControllerState from IVRSystem_015 returns with a correct VRControllerState_t struct.

This is a problem for ViveCraft for example that uses the C API through JOpenVR. No button on the controllers work.

Here is an example of program. When running, hold buttons. It should then show non zero values. But it is always 0.

#include <openvr.h>
#include <openvr_capi.h>
#include <iostream>
#include <chrono>
#include <thread>

int main() {
  vr::HmdError err;
  auto ignored = vr::VR_Init(&err, vr::VRApplication_Scene);

  auto vrsystem = (VR_IVRSystem_FnTable*)vr::VR_GetGenericInterface("FnTable:IVRSystem_015", &err);

  if (err) {
    std::cerr << vr::VR_GetVRInitErrorAsSymbol(err) << "\n";
    return 1;
  }
  while (true) {
    for (vr::TrackedDeviceIndex_t i = 0; i < vr::k_unMaxTrackedDeviceCount; ++i) {
      VRControllerState_t state;
      if (vrsystem->GetControllerState(i, &state, sizeof(state))) {
	std::cerr << state.ulButtonPressed << "\n";
      }
    }
    std::this_thread::sleep_for(std::chrono::seconds(1));
  }
  return 0;
}

SteamVR Performance Test not available for Linux

Your system information

• Steam client version: August 16, 2016
• Distribution (e.g. Ubuntu): Ubuntu 16.04
• Opted into Steam client beta?: Yes
• Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

SteamVR Performance Test is not available for Linux/SteamOS.
http://store.steampowered.com/app/323910

This makes it more difficult to determine if I should get VR on Linux..

Tracking not smooth and a little delayed.

Your system information

• Steam client version (build number or date): 1487812945
• Distribution (e.g. Ubuntu): Ubuntu 16.10 (64 bit)
• Graphics driver version (run nvidia-settings): 4.5.0 NVIDIA 375.27.10
• Gist for SteamVR System Information: https://gist.github.com/leinardi/92f4ce3e986209d752c383791c16ef08
• Gist for Steam System Information: https://gist.github.com/leinardi/7f9cc3f021a3ef546a884260b8a14f78
• 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:

When you move your head around it is noticeable that the tracking of the HMD is somehow delayed and not smooth. This is especially clear if you have tried SteamVR for Windows before.
Also the tracking of the Controllers seems to have the same issue: it looks like the position is being interpolated/approximated and the movement isn't smooth and instantaneous like on Windows.

This issue is really annoying for the HMD because it makes the experience really unpleasant and, after a while, nauseating.

This happens with any linear combination of AsyncReprojection and AllowReprojection (both on, both off, only one of them on).

It is most noticeable while playing some game like Destinations or SteamVR Tutorial but, to me, it is also clear inside the SteamVR environment.

Steps for reproducing this issue:

1. Start SteamVR
2. Look around and focus your attention on static items like the chaperone bounds
3. Start Destinations or SteamVR Tutorial
4. Repeat step 2

"An error occurred while updating SteamVR (missing executable)"

Your system information

• Steam client version (build number or date): Feb. 23, 2017
• Distribution (e.g. Ubuntu): Ubuntu 16.10 x64
• Graphics driver version (run nvidia-settings): Nvidia 375.27.10
• Gist for SteamVR System Information:
• 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:

After updating SteamVR beta in Ubuntu, I receive this error when trying to run it: "An error occurred while updating SteamVR (missing executable)". I tried restarting, uninstalling completely then reinstalling, but no fix. I also tried to verify integrity of tool files, and it said files checked out OK, but I'm still getting this error when I try to run.

Steps for reproducing this issue:

1. (Allegedly) Update SteamVR and/or Uninstall then Reinstall on Ubuntu
2. Try to run SteamVR by going to the Library, then Tools, then SteamVR.

Error: Shared IPC Compositor Invalid Connect Response (307)

Your system information

• Steam client version (build number or date): Feb 23 2017 at 00:38:08
• Distribution (e.g. Ubuntu): Debian Sid
• Graphics driver version (run nvidia-settings): 375.27.10
• Gist for SteamVR System Information: https://gist.github.com/Seegras/536eb51028e5c84df84809f0dbb6d701 (Sorry, gist insisted on removing LFs).
• Opted into Steam client beta?: [Yes/No] Yes
• Opted into SteamVR beta?: [Yes/No] Yes
• Have you checked for system updates?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

Steam started with STEAM_RUNTIME_PREFER_HOST_LIBRARIES=0 (or without, doesn't change)
Upon Starting "SteamVR (BETA)" it comes up with an error:

SteamVR failed to initialize for unknown reasons (Error: Shared IPC Compositor Invalid Connect Response (307))

After this, the monitor does detect headset, controllers and base stations and their state (standby/ready/connected), but an error-window persists ("Connect Failed: A key component of SteamVR isn't working properly") and everything else, including room setup doesn't work.

I can enable the Vive as display via nvidia-settings (and it will show a distorted workspace), but the error remains the same.

Error-Code is not on https://developer.valvesoftware.com/wiki/SteamVR/Error_Codes

VR Button in top right of Steam does nothing

Your system information

• Steam client version (build number or date): Feb 23, 2017
• Distribution (e.g. Ubuntu): Arch Linux (Seems to be distro agnostic)
• Graphics driver version (run nvidia-settings): 375.27.10
• Gist for SteamVR System Information: N/A
• 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:

Clicking the [VR] button in the top right of Steam does nothing. I see no output generated in the console output either when it is clicked. Going to Library>SteamVR>Play DOES work.

Issue is experienced by many other users. Discussion thread here.

Steps for reproducing this issue:

1. Plug in HMD
2. Click newly appeared VR button in top right
3. Nothing Happens
4. Shed a single tear :(