Issue with Valve Index

Smorty [she/her] · edit-2 9 months ago

Issue with Valve Index

Atemu · 9 months ago

The vrcompositor failed to initialise. Check the vrcompositor log in the Steam log files directory.

Smorty [she/her] · 9 months ago

Where can I find that vrcompositor log?

Atemu · 9 months ago

Your Steam directory has a log (or logs?) sub-directory and that contains a vrcompositor.txt

Smorty [she/her] · 9 months ago

Thank you for telling me. When the “display not found” error does not occur, it actaully lists the valve index display as an option as shown here:

vrcompositor.txt

Sat Mar 02 2024 23:45:48.724644 [Info] - Looking for direct display through Vulkan WSI
Sat Mar 02 2024 23:45:48.953899 [Info] -  - Vulkan output 0: 1280x1024 resolution, 380x300 dimensions - FUS B19-5 (DVI-D-0)
Sat Mar 02 2024 23:45:48.953972 [Info] -  - Vulkan output 1: 2880x1600 resolution, 0x0 dimensions - Valve Corporation Index HMD (DP-0)
Sat Mar 02 2024 23:45:48.954003 [Info] -  - Vulkan output 2: 1920x1080 resolution, 1210x680 dimensions - GRUNDIG TV (DP-5)
Sat Mar 02 2024 23:45:48.954030 [Info] - Tried to find direct display through Vulkan WSI: 0x56529d5fb9c0
Sat Mar 02 2024 23:45:48.954791 [Info] - Trying to match desired rate of 90.003006Hz.
Sat Mar 02 2024 23:45:48.954814 [Info] - 4 modes on display:
Sat Mar 02 2024 23:45:48.954830 [Info] -  - 0: 2880x1600@90.003006Hz
Sat Mar 02 2024 23:45:48.954844 [Info] -  - 1: 2880x1600@79.999001Hz
Sat Mar 02 2024 23:45:48.954873 [Info] -  - 2: 2880x1600@120.019005Hz
Sat Mar 02 2024 23:45:48.954901 [Info] -  - 3: 2880x1600@144.000000Hz
Sat Mar 02 2024 23:45:48.954915 [Info] - Selected mode 0.
Sat Mar 02 2024 23:45:49.417402 [Info] - Acquired xlib display!

Then afterwards, some [Info]s later, I get these errors:

Errors

Sat Mar 02 2024 23:45:50.099391 [Info] - HMD driver recommended: 2016x2240 90.0Hz HiddenArea(24.88%) = 610 MP/sec
Sat Mar 02 2024 23:45:50.099411 [Info] - GPU speed being set at first generation HMD resolution 382 MP/sec
Sat Mar 02 2024 23:45:50.099426 [Info] - Raw ideal render target scale = 0.63
Sat Mar 02 2024 23:45:50.099588 [Info] - New result of GetRecommendedRenderTargetSize for current app: 900x1000
Sat Mar 02 2024 23:45:50.099625 [Info] - Creating samplers
Sat Mar 02 2024 23:45:50.099723 [Info] - Creating util resources
Sat Mar 02 2024 23:45:50.100647 [Info] - Creating constant buffers
Sat Mar 02 2024 23:45:50.105007 [Info] - Creating systemlayer textures (w=1592,h=1772)
Sat Mar 02 2024 23:45:50.106200 [Info] - Creating/Updating distortion surfaces (mesh resolution 49)
Sat Mar 02 2024 23:45:50.167374 [Info] - Warp mesh (left eye) covers 82.12% of its viewport (shrink wrap saved 1.87%)
Sat Mar 02 2024 23:45:50.167774 [Error] - ASSERT: "unSize &lt; 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.226694 [Error] - ASSERT: "unSize &lt; 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.294548 [Info] - Warp mesh (right eye) covers 81.97% of its viewport (shrink wrap saved 1.97%)
Sat Mar 02 2024 23:45:50.295023 [Error] - ASSERT: "unSize &lt; 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.295504 [Error] - ASSERT: "unSize &lt; 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.396356 [Error] - ASSERT: "unSize &lt; 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.400858 [Error] - ASSERT: "unSize &lt; 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.401612 [Error] - ASSERT: "unSize &lt; 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.402094 [Error] - ASSERT: "unSize &lt; 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.405972 [Error] - ASSERT: "unSize &lt; 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.407084 [Error] - ASSERT: "unSize &lt; 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.407499 [Error] - ASSERT: "unSize &lt; 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.408178 [Error] - ASSERT: "unSize &lt; 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.408412 [Error] - ASSERT: "unSize &lt; 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.408676 [Error] - ASSERT: "unSize &lt; 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.408907 [Error] - ASSERT: "unSize &lt; 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.

They seem to target one specific line in some vulkan renderer c++ script. Then this is the very last error I get before it just keeps on printinig infos:

Sat Mar 02 2024 23:45:50.643309 [Error] - Unflushed events requested in CGpuTiming::GetDeltas!

So it really does detect the display, it just seems to have some undefined software issue… This would be the full files contents, in case there is some stuff which is vitally important. The SteamVR window itself does not even mention anything being wrong. It just sits there, happily rendering that image meant for the hmd. Do you see something in these logs? I am unfortunatly still at a loss…

@[email protected] · 9 months ago

The warnings you see are caused by https://github.com/ValveSoftware/SteamVR-for-Linux/issues/616. Maybe disabling async reprojection will help you too

Atemu · 9 months ago

deleted by creator

@[email protected] · 9 months ago

Listen, ill be real with you, its basically unusable and unreliable in most scenarios. The technical reason for this is due to Wayland vs X11 and other underdeveloped display technology. Normal gaming just got good enough after years of work. And before anyone tells me that the Index does work on Linux, it sure does just not well at all.

I have since sold my Index but when I used it, 80% of it was on windows. Be on the lookout for something called the Valve Deckard. I believe thats when Linux VR will finally be ready.

Smorty [she/her] · 9 months ago

… I’ll also be real with you and tell you something terrible. I installed Windows just to test if it works there and it did not. The same red lights, the same error. This seems like either my graphics card has some problems with it, or the headset is simply faulty. Unfortunatly I did not purchase this one new, but used, so no warrenty. It was for “only” 400€, and it came with perfectly functioning base stations and controllers. It’s “just” the headset display which does not work. You think it would make more sense to purchase a new headset specifically or to sell all the base stations and controllers to purchase a simple htc vive 1 ?

@[email protected] · 9 months ago

I would get a brand new headset from valve if I were you cause its going to be worth more to sell all of your stuff as a complete set in the future if you need to vs an old vive with that stuff.

Would only cost you a hundred more than you bought the used one for and its worth it cause Index is still the best VR experience you can get at the moment imo.

Smorty [she/her] · 9 months ago

You mean I should buy only the headset new, right? I think that makes loads of sense. Unfortunately right now the headset is not available.

@[email protected] · 9 months ago

Oh damn yeah it must not be available in your country right now sorry. I just assumed if it was available for us mericans it would be for everyone else :(

@StefanT · 9 months ago

Honestly I doubt it that Deckard will change that much. First the basics must be fixed. My Index is also laying around collecting dust. Worked okay-ish at first but is mostly unusable at the moment.

@[email protected] · 9 months ago

Try using distrobox arch. I did that on nixos and after some troubleshooting I got it to work.

ffhein · edit-2 9 months ago

When you say you got a new cable, you mean an original tether cable, which is connected directly to the graphics card without adapters or extension cables?

Also, are you using Nvidia’s closed source drivers or Nouveau?

Smorty [she/her] · 9 months ago

Yes exactly that. I got a new cable, the one which goes from headset into the graphics card. I am using the latest Nvidia-driver package from apt, so yes the proprietary one. No extension cables anywhere.

ffhein · 9 months ago

Any possibility to verify that the headset’s power adapter is working? E.g. multimeter

I saw someone suggesting a headset firmware reset for this issue, but others are saying they had to RMA their headset when they got solid red lights on it :(

Smorty [she/her] · 9 months ago

Unfortunately I don’t have a multimeter. As I said, the tracking works perfectly and even the IPD adjustment works. It’s just the display which does not seem to work The headset also gets warm while in “use” even though it doesn’t display stuff. How would I got about resetting the firmware?

ffhein · 9 months ago

I only have a Vive, but according to reddit this how you do it :) https://www.reddit.com/r/ValveIndex/comments/c8wvft/how_to_reset_hmd_back_to_factory_firmware/

And just brainstorming here, I think I’ve had problems in the past where I had multiple high resolution + high framerate monitors, though it might’ve been on my work computer where I had a docking station… What other monitors are you using? Have you tried lower framerates? My last graphics card was a GTX1080 which is similar to yours, but I don’t remember if that one had any peculiarities with VR. Back then I dual booted Windows for VR since it didn’t work well enough on Linux

Smorty [she/her] · 9 months ago

Hmm, very interesting. I held down the button when plugging it in, and it resulted in the infamous blinking red lights. Then steamVR indeed told me to enter my password for some sort of setup. I did that, but I stead on installing some firmware or something, it just started StaemVR like usual, but this time not the headset, nor the base stations show up. It has a small error window over it, which says that it could not detect any headset. This is easily resolved by just replugging the index power cable, but that just gets me back to where I started (all devices show up as they should and SteamVR just pretends that everything is working perfectly, while nothing is being displayed in the headset).

@[email protected] · edit-2 9 months ago

For me it does something similar most of the time

I plug the headset in, start streamvr, and it falls to connect to the headset display, with red lights on the headset

What fixes it for me is just hitting quilt vr on the steamvr window, unplugging the headset, plugging it back in and then starting steamvr

Then it usually works

In my experience after reboots, or after extended periods of time without running vr, I have to do this dance to get it to work, I don’t know why

I’m running an RTX 3090 with the proprietary drivers on Arch KDE X11, with the native (non flatpak) steam package

@[email protected] · 9 months ago

SteamVR has weird issues like that sometimes but restarting it or logging out and back in has always fixed it for me (aside from that one time I had to replace the headset cable)

@[email protected] · 9 months ago

What graphics card are you using? What driver is installed for it?

How do you have the USB’s plugged in for the headset and lighthouses?

Smorty [she/her] · 9 months ago

The lighthouses I only have plugged in to the wall. They magically connected to steam VR, and both appear as green. As said before, the tracking works perfectly, even for the knuckles controllers. I have a GTX 1060 with 6GB of VRAM. I’m using the latest version of the Nvidia-driver package (It’s something like 525 or somethin). I don’t think I need to plug the lighthouses right into the PC…

@[email protected] · 9 months ago

I have an original Vive and the only time I had to plug the lighthouses into the PC was to update the firmware through Steam.

Rest of the time I also only had them plugged into power.

@[email protected] · 9 months ago

I see you noted how you’re running gnome and what video card, but not how you’re running Steam, so I’ll ask:

How is Steam installed on your system? I know some people use a flatpak-based install but one of the potential issues with Flatpak (also Snap) is permissions to certain locations or devices can sometimes require extra config.

If you’re currently running from Flatpak, perhaps try the direct install from .DEB instead

Smorty [she/her] · 9 months ago

I am using the apt version of steam, so that should be fine

@[email protected] · edit-2 9 months ago

It should show up in the output of xrandr. At least my Vive does. Could you share that?

I believe in the past I was able to turn the display on with xrandr and extend the desktop to it. That would at least prove that the hardware works.

Smorty [she/her] · 9 months ago

The output of the xrandr command is this:

Output of xrandr

Screen 0: minimum 8 x 8, current 3200 x 1080, maximum 32767 x 32767 DVI-D-0 connected 1280x1024+1920+0 (normal left inverted right x axis y axis) 376mm x 301mm 1280x1024 60.02*+ 75.02
1024x768 75.03 60.00
800x600 75.00 60.32
640x480 75.00 59.94
HDMI-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 disconnected (normal left inverted right x axis y axis) DP-5 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 160mm x 90mm 1920x1080 50.00*+ 60.00 59.94 29.97 25.00 23.98 60.00 50.04
1600x1200 60.00
1360x850 60.00
1360x768 59.80
1280x1024 75.02 60.02
1280x960 60.00
1280x768 59.87
1280x720 59.94 50.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
720x576 50.00
720x480 59.94
640x480 75.00 59.94 59.93

@[email protected] · 9 months ago

Hmm, nothing there looks like an index display. My vive looks like:

DisplayPort-1 disconnected (normal left inverted right x axis y axis)
   2160x1200     89.53 +
   1920x1200     89.53
   1920x1080     89.53
   1600x1200     89.53
   1680x1050     89.53
   1280x1024     89.53
   1440x900      89.53
   1280x800      89.53
   1280x720      89.53
   1024x768      89.53
   800x600       89.53
   720x480       60.00    59.94
   640x480       60.00    59.94

Perhaps there’s a good reason for that, but this seems like a dead-end.

@[email protected] · 9 months ago

I use a Valve Index on GNOME as well, so here’s a few things:

VR doesn’t work yet on GNOME Wayland, you need to select GNOME on Xorg when logging in
Sometimes the LEDs are red and the headset doesn’t get detected, just unplug the cable and plug it back in
You might also need to press on the cable where it connects on the headset sometimes, it can become a little loose
Use CoreCTRL to manually set the GPU performance profile to high, it doesn’t do that automatically for some reason and there’s a huge performance difference
If you have the issue that moving your head makes it look like the image is jumping back and forth, go into the per-application video settings of the game from SteamVRs menu and turn on Legacy reprojection
- This only happens when I have very low FPS, the CoreCTRL thing fixed it for me without having to use this option
There’s an older SteamVR version for Linux you can select as a beta option for SteamVR in Steam but I’d actually not recommend using it, it only works when games use Proton 5 and there are newer games that don’t work with a Proton verison that old. A lot of the issues the regular SteamVR version had are fixed now and it works pretty well for me.

Smorty [she/her] · 9 months ago

What exactly do you mean by “press”? In which direction? I have plugged the cable into the headset until it kinda clicked, like a thump, so I thought that would be enough. So yeah, press in which direction? Also I have tried all the steamVR versions, so yeah that’s likely not the issue

@[email protected] · 9 months ago

It’s just in case you have issues with the headset not getting detected, the cable can become a little loose and you might need to press it into where it connects to the headset