I thought this might be useful as more and more people have gotten their Frames (me included), and many more will be getting theirs.

Me and many others have run into some problems using their Frame, so a thread listing common problems and their solutions is a no-brainer.


Right eye ghosting

This is a known issue. It manifests as “ghosting” of bright parts of the image (menus and text usually) but only in the right eye view, and only when streaming wired or wireless. It persists regardless of streaming, framerate or projection settings. It affects not just the Frame, but other headsets like the Quests as well.

The fix is currently in the beta branch, update SteamVR on both your host system and the Frame to fix it.

Dongle not detected

The wifi chip in the dongle requires kernel 7.2 or newer. I was on the LTS kernel on my Endeavour OS install, so that was one part of the problem.

Valve has a troubleshooting script for linux users available, which for me revealed that my system had no regulatory region set.

On arch this is fixed by installing the wireless-regdb package, which provides region data. Then setting your region in /etc/conf.d/wireless-regdom by uncommenting your country.

After a reboot, the dongle shows up!

Dongle doesn’t pair

For some reason, pairing does not seem to work when attempting it from the streaming toggle button inside the Frame.

However, if I navigate to the “Remote Play” section in settings on my Frame, and do it from there, it works immediately.

Streaming stutter

My streams did not start off perfect. I’ve done many things to improve it, most of which are relevant to my particular router and hence not applicable to everyone.

But in general, it seems that for 6Ghz, 160Mhz channel width works better than 320Mhz. Also having ANY other device on the same connection can cause stutter. I also improved things by disabling some power saving features on the router side.

I’ve not messed with the dongle much, as I have a far more powerful router with much better coverage of my play space. Using it for the 6Ghz connection did not seem to work better than the router for me, but I’ve seen others get the best result by using ONLY the dongle, and disabling the LAN+WiFi stream entirely.

SteamVR desktop mirroring does not work

This seems to simply be broken on linux?

I’m using WayVR for this instead. You can add it to Steam so you can launch it from the Frame after starting a stream from your PC.


Other problems or solutions to bring up? Comment please!

  • MentalEdge@sopuli.xyzOP
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    5 hours ago

    You should create separate SSIDs for 6GHz and 5GHz, you want to stick to one or the other for the WiFi link. When using multi-link, the dongle will switch to whichever is not being used by the WiFi connection (Or always 6GHz, if the option to reserve it for the dongle is enabled). You are not using two 6GHz connections, it’s always 5+6GHz, as the Frame can only do two different connections at the same time. (Maybe that’s why you incorrectly assume 3 frames is the maximum in a room?)

    Your router connection being a tad worse is probably because the frames are using 5GHz there (assuming the dongles are on 6GHz), and doing so on the same router? You’ll probably get better results disabling multi-link, and using only the dongles.

    Transmit power is not the final say on the router side, check for features like “airtime fairness” and “transmission bursting” that trade latency for other things.

    You can absolutely have more than 3 frames in a room, though for that kind of setup, you’d want to configure each of them to use specific, non-overlapping 6GHz channels (which is tricky as the dongles use hidden SSIDs that can’t see each other, and therefore avoid channel overlap). And you would need to use the dongle for this, as otherwise you’d need to get one router for each Frame, to enable them being on different channels.

    You’d also want to disable multi-link, as again, to use it effectively you’d need both a dedicated router for each headset, as well as a dongle, in order for all connections to use separate channels.

    But, this means that at 160MHz channel width, you can have up to 7 (in the US) Frames in the same space, (and technically also give each a 5GHz multi-link connection) each using an entirely separate and dedicated 6GHz connection. You might even be able to drop to 80MHz and do 14 Frames. The bandwidth should be sufficient.

    Though when this saturated, you’d have so many people and their devices around, that people’s phones and PCs scanning for WiFi will cause interference. It might become necessary for people to put their other devices in airplane mode to stop them sending hotspot queries in the 6GHz range.

    Vive trackers operate at much smaller datarates, and use the 2.4GHz range, they should not interfere with Frame streams.

    • JelleWho@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      2 hours ago

      Yhea we know we’ll what the limits of the Vive trackers are xD, I needed to reprogram some smart home stuff to be able to go thought the blackout of us going in VR, having 10 trackers was already enough for more than half of packages being lost, and going to 20 there is just no wifi anymore.

      Starting to learn the ins and our of the Frame. I will try and play around a bit more with the 5Ghz and 6Ghz on the AP, I could get our second AP online too and try just using one AP for each heatset. But that would mean moving it around. We will see how testing goes.

      • MentalEdge@sopuli.xyzOP
        link
        fedilink
        arrow-up
        1
        ·
        2 hours ago

        Do note that in good conditions, multi-link really isn’t needed, and if one of the connections is bad, disabling it can actually improve things.

        You can manually set the channels for the dongles, you have to enable custom in Remote Play settings inside the Frame, there you can set a custom SSID, channel, etc.