protontricks VS flatpak

Just played games on Linux for the first time. It's way easier than I originally thought since Proton is integrated into Steam client. Can even run non-Steam games through Steam client but had to use protontricks to add dependencies like Visual C++ redistributables.

We'll be needing Protontricks to install those packages into our Proton session of our game (each steam game has their own one). You can install it here https://github.com/Matoking/protontricks.

Try to run the mod manager in the game prefix by using protontricks.

ALSO if a mod has some kind of external dependency, like if it specifically mentions needing VisualC or .NET Runtime, Protontricks will be a lifesaver for installing these into Proton prefixes. Might not need it often, but could come in handy to know anyways.

I'm learning a bit more about Proton. You can install Protontricks and then run protontricks 824270 and it should install stuff for you.

You can try protontricks with protontricks 1730590 winhttp (1730590 is The Entropy Centre's Steam App ID, that I just looked up on protondb)

That might be a problem, you could try to install native d3dx9 and xact to the game's wine prefix using winetricks or protontricks. I'd try d3dx9 on it's own first.

But I suspect that you'd find it much easier and more convenient to just use protontricks for this.

install it in the game's proton instance with protontricks

Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.

No, it looks like you have to do it on an application basis.

https://github.com/flatpak/flatpak/issues/2913

Flatpak

> CLI tools do not implement auto-complete themselves. What you are seeing are auto-complete scripts for your shell that make network connections.

nit: This is incorrect. Robust auto-complete scripts call the actual program to provide completions.

That is what Flatpak does. It is Flatpak itself that makes the network connections.

https://github.com/flatpak/flatpak/blob/main/completion/flat...

Not that it would make any differencen if it was implemented in Bash seeing as the Bash script is also provided by Flatpak.

The only performance impact I know of is with the seccomp filter in CPU-bound tasks: https://github.com/flatpak/flatpak/issues/4187

Skimming through the recent comments, there might be a way to optimize some of it.