updated conclusion

This commit is contained in:
2026-07-21 16:28:12 +09:00
parent 3033b6bea9
commit c5f57d6305
+1 -1
View File
@@ -13,7 +13,7 @@ I have a Steam Deck OLED (512GB) and I pretty much like playing games with it. T
And for reasons I won't disclose because I don't exactly know myself, I picked Arknights: Endfield to be my controller-native game to play on the Deck. I imagined that with the outrageous mobility of your Steam Decks, it'll be fully possible to enjoy the unnecessarily complicated modern mobile game while lying in bed, connected to WiFi. And for reasons I won't disclose because I don't exactly know myself, I picked Arknights: Endfield to be my controller-native game to play on the Deck. I imagined that with the outrageous mobility of your Steam Decks, it'll be fully possible to enjoy the unnecessarily complicated modern mobile game while lying in bed, connected to WiFi.
That's where things started to go wrong, fortunately. That's where things started to go wrong, fortunately.
**Spoiler / TL;DR**: It's the wireless NIC being shit. **Spoiler / TL;DR**: It's the IPv4-over-IPv6 having a tiny MTU, and SteamOS somehow handling that (PMTUD) strangely.
## Running a Windows-oriented modern online game on SteamOS was not a problem ## Running a Windows-oriented modern online game on SteamOS was not a problem
So I won't go too deep into this. As simple as booting every relevant Windows exe through Steam using Proton. Then you could have the game executable running. So I won't go too deep into this. As simple as booting every relevant Windows exe through Steam using Proton. Then you could have the game executable running.