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.
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?
Quite the opposite. Linux is currently frequently matching Windows in performance when running games through Wine/Proton. Targeting Linux native avoids this translation layer, and can result in better performance or less CPU overhead for the same performance (which is noticable especially on devices like the Steam Deck).
Yes, because of the tooling. If you make a game in Unity, and build for Windows, ““things just work””. If you then build for Linux, you can face any number of random engine issues, like bad controller support, broken mouse grabbing, etc.
Valve has thought about this, and designed the Steam Linux Runtime. This does effectively the same thing as Flatpak, except it pulls in the system native graphics drivers. Steam Linux Runtime provides effectively a full (minimal) Linux distribution that game developers can target, ensuring their games keep running, even on more modern systems.
Gaming on Linux has always been a chicken and egg problem. Gamers see there’s no games on Linux, so they stick to Windows. Developers see there’s no Linux gaming market, so they stick to Windows. With Valve’s Proton, they interrupted this cycle. Most games now work on Linux, but game developers haven’t switched yet. For them to switch, there needs to be a market of Linux users, and the tooling needs to be sufficiently developed for Linux, ensuring the same (or better) quality as the Windows versions of games. This includes game engines, common libraries (like online multiplayer frameworks or voicechat), and possibly development software, 3D modeling software like Blender, the Adobe suite, etc.