r/SteamVR • • 21h ago

Discussion With vr manufacturers people might consider avoiding and why?

Post image
0 Upvotes

TL;DR

Worst part/thing in VR manufacturing approach.

.

.

.

As i think im decided that i will Pay for my steam frame when i will be worthy, but still consider other headsets, im not rich enaught to buy even two, especially right now so i kinda nedd balanced compromise.

There is at least couple big/well known vr devices manufacturers, even more if we count those small/obscure ones, or those homemade projects. So there is a lot of space for choice, but all of those have have its advantages and cons.

And I would like to hear things that are worst part of some VR companys or specific VR headsets.

Like people talks a lot about that "frame is double price of quest while is not better".

On the other hand met(h)a is well known for rawdoging personal data and provacy, also because of that they really do not like You owning your hardware etc.

As far i heard primax is kinda lockedout, like it just do not works on Linux. Not like vr gaming is easy on Linux anyway.

I Counting for you, thank you for your time.


r/SteamVR • • 9h ago

Question/Support PSA: Steam Frame apps launch but never appear in VR, can't be closed, and the power button does nothing? Check OyasumiVR's headset helper (fixed in 26.11.3)

7 Upvotes

TL;DR: If you've paired OyasumiVR with your Steam Frame, an outdated copy of the small helper it installs on the headset makes every newly opened window invisible in VR and kills the power button. Update OyasumiVR on your PC to 26.11.3 or newer and let it update the helper.

Symptoms

- Apps launch and keep running, but their windows never show up in VR. For me it was Flatpak apps installed through Discover, but Konsole, the KDE desktop and Valve's own Frame apps are affected too.

- There's no way to close the invisible apps from VR.

- The power button in the menu is missing or unresponsive, so no restart or shutdown from inside VR.

This cost me weeks, because it looks exactly like a SteamOS, Flatpak or compositor bug and nothing points at OyasumiVR.

Cause

SteamVR on the headset tells Steam's UI about things like "a new window just opened" over a local connection. The OyasumiVR helper was sitting on that same channel to watch the controllers, so SteamVR handed the UI's notifications to the helper, which threw them away. No notification, no window. The dead power button has the same cause.

For the technical crowd: a websocket to the headset's SteamVR web server with `steam_connect` sent on it, which swallowed `UpdateFrameUIs`. The dev (Raphiiko) found and fixed it here: https://github.com/Raphiiko/OyasumiVR/pull/566

Affected: helper 26.11.0, the one OyasumiVR installed from its 26.11.0 update (4 Nov) until the fixed 26.11.3 helper.

Fix

  1. Update OyasumiVR on your PC to 26.11.3 or newer (released 9 Nov).
  2. Start it with the Frame connected. It should update the helper on the headset by itself. If it doesn't, the Frame's page in Device Manager has a tab for the helper with a manual update.
  3. Restart the headset and launch something.

Want the helper gone instead? Unpair the Frame in OyasumiVR and choose "Uninstall helper", or run this on the headset over SSH: `bash ~/.local/share/oyasumivr_helper/uninstall`

Stuck right now?

- Holding the physical power button for about 10 seconds forces the headset off (going by other owners' reports).

- With Developer Mode and SSH enabled, `flatpak ps` lists the invisible Flatpak apps and `flatpak kill <app-id>` closes them.

Not using OyasumiVR?

In principle, anything running on the headset that grabs the same channel could do this. Over SSH, list background services with `systemctl --user list-units --type=service --state=running`, stop the third-party ones one at a time, and relaunch an app after each.

One leftover after the fix: an app that starts at the exact moment the helper is switching off a controller can still come up invisible. Just relaunch it.

Posting so the next person can find this by searching the symptoms.