Issue with Valve Index

Smorty [she/her]@lemmy.blahaj.zone · 1 month ago

Go use NewPipe! Its Foss!

Smorty [she/her]@lemmy.blahaj.zone · 1 month ago

Gay pirates are the best kinds of pirates 💞

Smorty [she/her]@lemmy.blahaj.zone · 2 months ago

OP is not asking for windows

Smorty [she/her]@lemmy.blahaj.zone · 4 months ago

Dear fellow scholars

Smorty [she/her]@lemmy.blahaj.zone · 4 months ago

Ok this one is really impressive. I’d say this is the most realistic looking AI image I’ve seen yet.

Smorty [she/her]@lemmy.blahaj.zone · 4 months ago

Consume children. OBEY!

Smorty [she/her]@lemmy.blahaj.zone · 4 months ago

She must be saving “yo!”

Smorty [she/her]@lemmy.blahaj.zone · 4 months ago

As an AI language model, I am unable you create images of things which will never happen

Smorty [she/her]@lemmy.blahaj.zone · 4 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

Smorty [she/her]@lemmy.blahaj.zone · 4 months ago

Oof… Yeah that’s interesting. One might call it prompt engineering

Smorty [she/her]@lemmy.blahaj.zone · 4 months ago

Ok fair, sorry. I just don’t know any rap…

Smorty [she/her]@lemmy.blahaj.zone · 4 months ago

Uh a man after midnight

Smorty [she/her]@lemmy.blahaj.zone · 4 months ago

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

Smorty [she/her]@lemmy.blahaj.zone · 4 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.

Smorty [she/her]@lemmy.blahaj.zone · 4 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 ?

Smorty [she/her]@lemmy.blahaj.zone · 4 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).

Smorty [she/her]@lemmy.blahaj.zone · 4 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…

Smorty [she/her]@lemmy.blahaj.zone · 4 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

Smorty [she/her]@lemmy.blahaj.zone · 4 months ago

Where can I find that vrcompositor log?

Smorty [she/her]@lemmy.blahaj.zone · 4 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?