UnsupportedShow Details
Unknown
Works great out of the box. Might have some minor framedrops, but only in the menu
Running Steam through Flatpak in Fedora Silverblue (computer with amd gpu). Native version of the game didn't work with my Xbox Controller. It was solved after I switched to Proton.
Only detected after switching from native to proton.
CPU at 5W and GPU at 400 is enough for locked 60fps - battery showed 3hs of play
Works great out of the box
Local couch multiplayer and combined local multiplayer + online players works great
I've ocassionally had to try a few times to get online multiplayer to connect, but I think that's more an issue with the game's backend than proton.
Slight haze effect, but with a tweak in the game settings, it was fixed
Worked fine on steam deck. Playing online might make things hard to see on the small screen but solo works well in handheld and multiplayer works well on the tv. Since it works well on steam deck, I assume it works amazingly on pc just as well if not better.
tested on usb-c hub with hdmi, 2 players with x360 controllers. everything was fine
Not sure why Steam says it's unsupported. It's definitely easier to play on a big screen (trash bags can be a bit hard to find) but still doable on the deck's screen.
It always gives a "not responding" error on launch but it goes away after the game gets to the main menu and everything works fine
works as expected
It runs great!
Sometimes the mouse is moved and you must minimize and maximize the window again
Installed and played great. No fullscreen, alt-tab, or controller problems to speak of. The only issues I experienced were:
- Some early access bugs
- Most of the fun comes from multiplayer and nobody is online. Ever. I played literally 1 online session in 4 hours. And it lasted 15 minutes. I spent a lot of time waiting for players to join, but nobody ever showed up. You can still solo levels, but without other players, it feels dead.
But performance wise, this was a platinum experience. Not a single Proton issue to speak of.
This was with v0.9.0b5
