Basically Larian is working on a native Linux version of BG3, and that got accidentally set as the default even though it’s not yet in a launchable state.
It’s been corrected now, but you may have to restart your deck to get the fix.
I wonder why they’re making a Linux native version? It is one of the ironies of Proton that windows native games are so easy to install it seems a bit pointless? But also making games for Linux is ironically difficult as it’s difficult to support long term as they can break as libraries change over time.
It feels like we need a Flatpak style set up for Linux native games which may help games launch stable long term versions that won’t “break” if newer libraries don’t work with them. Flatpaks “bring your own dependencies” approach is more similar to how windows games often work with their own dlls (even to the point of installing old versions of directx when needed) except without windows annoying set up of spraying dlls all over your hard drive making them difficult to clean up when you uninstall a game.
Although arguably Steam already deals with that on both Linux and Windows currently. But it is proprietary. And maybe Flatpak is already that solution? Maybe Appimage too although not sure how well a 30gb would run from a single file virtual file system? Is it native speeds or have some overhead?
luckyeddy@sh.itjust.works 13 hours ago
This explains a lot. I ended up reinstalling on hotel wifi which was painfully slow. 🥲
xkbx@startrek.website 12 hours ago
I forced it to open with Proton Experimental on my Steam Deck to make it work. I had panicked because restarting it twice didn’t work