Steam Hardware

23,318 readers

2,787 active

107 users here now

A place to discuss and support all Steam Hardware, including Steam Deck, Steam Machine, Steam Frame, and SteamOS in general.

As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title

The following is a list of suggested flairs:
[Deck] - Steam Deck related.
[Controller] - Steam Controller related.
[Machine] - Steam Machine related.
[Frame] - Steam Frame related.
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.

If your post is only relevant to one hardware device (Deck/Machine/Frame/etc) please specify which one as part of the title or by using a device flair.

These are not enforced, but they are encouraged.

Rules:

Follow the rules of Sopuli
Posts must be related to Steam Hardware or Steam OS in an obvious way.
No piracy, there are other communities for that.
Discussion of emulators are allowed, but no discussion on how to illegally acquire ROMs.
This is a place of civil discussion, no trolling.
Have fun.

Link to our Matrix Space

founded 5 years ago

moderators

Moxvallix@sopuli.xyz

Fubarberry@sopuli.xyz

Frame Troubleshooting (sopuli.xyz)

submitted 3 days ago* (last edited 1 day ago) by MentalEdge@sopuli.xyz to c/steamdeck@sopuli.xyz

23 comments fedilink hide all child comments

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

Edit: follow up post

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!

you are viewing a single comment's thread
view the rest of the comments

[–] vividspecter@aussie.zone 3 points 3 days ago* (last edited 3 days ago) (1 child)

It's interesting that an unset region for the dongle causes issues, as it has generally not been a problem with wifi adapters in the past for me. Must be something specific to this adapter, or it's interaction with the Frame.

EDIT: It seems that 6GHz is disabled in the world domain, according to this NixOS wiki article, so that would explain the benefit of setting the region.

permalink

fedilink

source

hideshow 1 child comment

[–] MentalEdge@sopuli.xyz [S] 3 points 3 days ago* (last edited 3 days ago)

6GHz is not globally legal. That part of the spectrum is used for other stuff, too, not just wifi. Unless software (and in some cases hardware) can verify in some way that they are in a region where that spectrum is allowed to be used, they won't put out a single signal in that range. Phones and laptops often check whether other 6GHz devices are around. If they are, they will usually allow you to at least connect to 6GHz networks, simply assuming that if devices that create such networks are nearby, then they must be legal wherever you are.

But the dongle CREATES the 6Ghz network. That's why it needs to be extra sure. That is also why the warning on the Arch wiki page I linked about ABSOLUTELY NOT setting your region to anything other than what it actually is, is so serious.

permalink

fedilink

source

parent