Hello @aronschatz, please copy your system information from steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. In particular, please include any CrashIDs or minidumps (found in /tmp/dumps/) related to this issue. You can put minidump files into an archive and drag and drop them directly into the comment box.
I have the same issue as the OP. I'm running different hardware but not significantly.
SteamVR starts with an error about a config file missing error 111 but continues to the steamVR environment ok, head tracking and controllers work fine.
Vr Tutorial dies before running and Destinations eventually locks up after a few seconds.
Logs etc attached
dumps.zip
Excited to see this happening now !
For reference, in the attached set of minidumps, assert_20170222140855_1.dmp is a SIGSEGV outside a library (strange?). The a first crash dump is a SIGSEGV in vrmonitor. The second and third crash dump is a SIGSEGV in vrcompositor.
Exactly the same problem here on fedora 25, recommended nvidia beta driver, nvidia 970 gtx, intetl 6700k. Also appear a message that not compatible headset is detected, but i can ignore it and still works. Tutorial doesn't start and destinations crash soon after start.
Btw, when starting steamvr all the time says im on extended mode, i change it to direct, then it says it need to reboot, but never does. When i start it again, it says the same. After few tries on settings seems i activated direct mode, because this message doesnt appear again. But it works almost at same way, now tutorial windows doesnt dessappear after a while, but it not show anything.
@serk7 I think that one is on the list of "Known Issues : The VR status window isn't currently aware of direct mode being enabled or not, so the "enable direct mode" and "disable direct mode" buttons should not be used; direct mode is automatically enabled where supported"
@aronschatz Would you mind trying disabling asynchronous reprojection and interleaved reprojection as shown in the screenshot and report back if that makes any difference in Destinations hanging?
It still hung for me after a min, then consumed cpu cycles until exiting VR
Thank you ryantux, its obvious it was in direct mode, without the beta drivers was working without direct.
There's a currently a hang in NVIDIA configurations that can result in a full system lockup; we're looking into it. If the compositor hangs you should try killing all vr-related processes as soon as possible or you might lose your hand on the system.
https://gist.github.com/aronschatz/63e0bd64503111f4664a3758ff5bd45d
@Plagman That's the behavior I've noticed. The system starts chugging resulting in a VR lockup, then it continues to take down the entire system.
assert_20170222090339_21.tar.gz
I'm not sure if this file is from the crash or not since it completely freezes the system.
For reference, the attached assert is a DUMP_REQUESTED in crashhandler.so.
seems all of us have 970 gtx.. turbo from asus? xD
I think this should be expanded to include #7; the symptoms seem similar. Additionally, I'm on Arch and a GTX 1070(M). https://gist.github.com/greyson/4db4ad7ef9fa9e177952da9bf524efc2
I don't think #7 is related other than the VR system crashes or something. The root cause seems very different.
@serk7 I have an eVGA 970GTX, but I don't think the brand really matters.
After updating steam to the latest Beta I was able to remain in Destinations for much longer before the system locked up again.
There was bad flickering in the right eye during in game menu with async and interleaved turned on however most of the environments felt ok.
The menus seemed fine with just async on but the environment felt laggy. Also my right eye felt constantly out of focus.
IPD setting doesn't show in HMD when adjusting .
Running on Gainward 980GTX 4GB
For reference, the four attached minidumps are DUMP_REQUESTED in crashhandler.so.
SteamVR updated to the latest (1487886215). I've tried doing the suggestion that @danginsburg said in a previous post.
In short, there's no crash anymore.
After turning those settings off (or updating SteamVR, not sure what the cause is), Destinations started up and still presented to chug and lag pretty heavily. After some time, it started to clear up and performance was more reasonable. It was now playable, but performance wasn't on par with Windows.
I re-enabled those two settings and Destinations still hasn't crashed, although the performance seems mixed. The view jumps from time to time and just seems a bit laggy (drunk vision, at times). I will agree with @ryantux that the right eye seemed to jump around alot.
I think this is good progress. Since I'm not seeing the crash anymore, I'm willing to close this if needed. But, I'd still log another bug with the jumpiness of it. Let me know what to do.
The March 10th build of SteamVR is exhibiting the same issue. Destination now crashes almost all the time and beings to take down the system once again. I haven't fiddled with the settings, but it seems like a regression. This is with the .13 Nvidia driver.
I upgraded my computer and have fresh installed Kubuntu 16.10 (kept the /home partition, though).
New System Info: https://gist.github.com/aronschatz/467c618cb37145953d3e8047afd8d8ea
This bug is still happening with the SteamVR beta as of March 15th.
This is still happening. Now a compositor window is showing, too. Never showed before.
Yep, this is happening for me as well.
Nothing extracted yet.
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.