Linux Gaming

18951 readers

13 users here now

Gaming on the GNU/Linux operating system.

Recommended news sources:

Related chat:

Related Communities:

Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.

founded 5 years ago

MODERATORS

poVoq@slrpnk.net

Quintus@lemmy.ml

mudle@lemmy.ml

[Solved] Is streaming to the deck supposed to "just work"? (lemmy.ml)

submitted 6 days ago* (last edited 5 days ago) by slackness@lemmy.ml to c/linux_gaming@lemmy.ml

10 comments fedilink hide all child comments

Solution: tried native steam and worked instantly. Fiddled around with flatpak permissions and discovered steam need all devices access (rather than just input) for the controls to work when streaming to the deck.

I wanted to stream Expedition 33 to my deck. The game launches just fine but it won't recognize anything but the touch screen and I see MnK controls are active.

So I connected a controller to my PC, launched the game there, then started streaming from the deck. But as soon as the deck is connected the game goes back to MnK inputs and again nothing but the touch screen works.

The PC is running Steam Flatpak and Proton Experimental. With default Steam Input settings (which I think cannot be disabled when using Steam Play anyway).

I cannot run the game using Proton GE, just getting a black screen with audio.

So is Steam Play supposed to be a plug and play experience and I'm unlucky?

top 10 comments

sorted by: hot top controversial new old

[–] zaphodb2002@sh.itjust.works 6 points 6 days ago (1 children)

It's pretty janky in my experience. I use sunshine, works a lot better.

[–] tkohldesac@lemmy.world 3 points 6 days ago

Sunshine is the way. Steam Remote “works”… technically… But Sunshine/Moonlight is way better.

[–] HER0@beehaw.org 1 points 6 days ago

The Steam Deck compatibility notes for the game specifically say that it isn't good at handling multiple controllers:

This game does not default to external Bluetooth/USB controllers on Deck, and may require manually switching the active controller via the Quick Access Menu

I think it is likely that this problem comes from the game, not a problem with streaming sending the inputs. You can try testing this in another game with more flexible controller support to narrow it down.

[–] ProfessorOwl_PhD@hexbear.net 1 points 6 days ago (1 children)

It should be pretty plug and play, but it looks like some controller settings can mess up the deck's input.
Trying going into the game properties and setting Steam Input to disabled in the controller tab, then restarting the game. Also worth checking if it's happeneing with all your games or just E33 in particular.

[–] slackness@lemmy.ml 1 points 6 days ago (1 children)

Looks like that setting does not sync between devices. Am I supposed to adjust it on the remote machine or the deck?

[–] ProfessorOwl_PhD@hexbear.net 1 points 6 days ago

Should just be the remote machine.

[–] MentalEdge@sopuli.xyz 1 points 6 days ago (1 children)

Sunshine is what I use, too. You can set it up to adapt your monitor resolution to the deck upon connecting, and set it back to normal upon disconnect. Very handy.

You definitely can turn off steaminput with proton. Per-game, too.

[–] slackness@lemmy.ml 1 points 6 days ago (1 children)

You can but it lists the state under different conditions which includes: Remote Play: Enabled, always required

[–] MentalEdge@sopuli.xyz 1 points 6 days ago

Ah. I guess steam uses it to emulate a gamepad to transmit the controller inputs over.

[–] Fizz@lemmy.nz 1 points 6 days ago

Its supposed to but doesnt.