Keyboard is always registered as an input affecting split-screen games.

[mikeymop]

Describe the bug

This issue is made apparent with games like Sackboys Great Adventure.

Traditionally this should be launched without the keyboard plugged in to correctly register a controller as player one.

Many issues can be remediated by removing the keyboard and remapping the controllers in steam input.
It seems in Bazzite, even with the keyboard unplugged, that a keyboard is registered as an input.

What did you expect to happen?

Launching a game without a keyboard plugged in and a controller connected will default the controller to player one.

Output of rpm-ostree status

Will provide shortly.

Hardware

CPU: Ryzen 5 5500g
GPU: rx5500

Extra information or context

No response

[jsnyder]

I'm also experiencing this. It's also not clear to me in the game how to switch out the first player at all.

Does this have something to do with still having PS/2 ports on the motherboard for a keyboard?

[mikeymop]

I don't think so as the machine I am using does not have PS/2 ports.

What may be happening is that the keyboard may be mapped to steam as the Steam Deck controls.

On the Steam Deck with Sackboy I also am forced to leave player 1 on the steam deck.

However on desktop Linux it works as expected for this game.

[jsnyder]

Are you saying that on a bog standard Steam Deck it sticks you with a keyboard player? I don't remember that happening before (re-installing on my actual Deck now).

I'm also not sure what you mean by the keyboard being mapped to steam. Is that essentially reflecting that the Steam Deck has it's built-in controls and therefore this version of Steam needs a replacement for that and that's set up as keyboard?

I have had issues with different games sometimes either getting stuck only taking keyboard input. It's kind of like some of the auto-input switching I've seen in other contexts like on Windows steam isn't working quite right. Where if you hit a key/use the mouse you see all the in-game key/button layout help switch between modes.. now that doesn't happen and sometimes you get stuck with keyboard even though a controller is connected (this could be a separate issue).

I don't actually know a ton about how these input layers work on the various platforms and also Desktop vs Game Mode vs Big Picture for what to dig in on to resolve this.

[jsnyder]

Yeah, this does not happen on my stock standard Steam Deck (OLED):

(Nothing plugged in)

[dosubot]

Hi, @mikeymop. I'm Dosu, and I'm helping the bazzite team manage their backlog. I'm marking this issue as stale.

Issue Summary

• Split-screen games incorrectly register a keyboard as an input even when unplugged.
• You clarified that your machine lacks PS/2 ports, suggesting a mapping issue with Steam Deck controls.
• Another user, jsnyder, noted the issue doesn't occur on their standard Steam Deck, indicating a potential configuration discrepancy.

Next Steps

• Could you confirm if this issue is still relevant with the latest version of the bazzite repository? If so, please comment to keep the discussion open.
• If there is no further activity, this issue will be automatically closed in 14 days.

Thank you for your understanding and contribution!

[mikeymop]

Hey, because there is not yet a follow up.

I've tried again over the weekend on both games that affect me:

• Moonstone Island
• Sackboy: A Big Adventure

Both default to the keyboard as player one, even if no keyboard is plugged in when launching the games.

There is a workaround that works once per boot, where I start the game, and add a third controller while the game is running.

This exposes the "switch controller ordering" in Steam input ui. With which I can set the desired controller to n+1 where n is the highest numbered virtual controller port in Steam Input.

If I relaunch the game, with the extra controller, them default pot will be n+1 and I need a fourth controller to expose the port assignment and set player one to the next highest virtual port.