• 0 Posts
  • 3 Comments
Joined 1Y ago
cake
Cake day: Jul 01, 2023

help-circle
rss

To add to that, back in the day you had to find out what engine a particular game used as there were huge compatibility issues with certain engines and others ran a fair amount slower via Wine. Some engines, however, ran incredibly well under Wine.

That said, there were some cool things you could do in Wine like define a pseudo monitor to run your game on. Example, back in 2010 (before widescreen monitors were more common) I had a triple head setup on Linux. I could specify in Wine an arbitrary monitor size (like say 2560x1024) and run games “full-screen” centered on my setup while having other windows open on the edges of my real desktop.

Even games that officially didn’t support multiple monitors and on Windows (would force themselves to one screen and black out the other ones) ran well via Wine with this setup.

It was a bit involved to get working the first time though!

Played through the HL2 games, Supreme Commander, Rift: Planes of Telara, and even Wow that way (though WoW had other issues with non 4:3 displays).


Before Proton there were many projects that were helping run windows games and apps on Linux. Many of these were massive undertakings:

Wine (translate windows API calls to Linux API calls)

Wine tricks (automates the installation of many Window app dependencies)

Crossover and their work on wine & wine bottles (a mini windows drive environment for each program)

Loki’s early work on SDL to simplify sound and input for Linux and other *nix targets.

Mono (open source implementation of . Net a library used by a fair amount of windows apps (also includes Moonlight - the open source implementation of MS Silver light)

DXVK a impressive and efficient Direct X 10 & 11 to Vulcan translation layer (later incorporated D9VK - Direct X 9 to Vulcan) which also helps older games run better in Windows in addition to adding compatibility for Linux

And many other pieces I’m forgetting now, make up Proton. Valve did an awesome thing in packaging all the community developed components, put some of those devs on their payroll, and even paid Crossover to work on the project that ultimately became Proton.

Now with Proton, what would require lots of individual steps and separate downloads (setup a separate wine environment for each application, add dependencies, install DXVK, install needed open source frameworks, add any registry tweaks needed, etc) is now mafically automatically handled behind the scenes in one step by one tool by just installing a Windows game on Linux via Steam (though Proton can work without Steam as well).

Since all the work is open sourced, the community is able to have their own version of Proton with newer fixes and components that Valve could not distribute themselves due to licensing: Glorious Eggroll.

There were many attempts in the past to make an all-in-one tool to handle setting up wine and other compatibility tools (Lutris, Transgaming, PlayOnLinux, etc). So Valve wasn’t necessarily the first, they just offered a well put together, funded, and easy to use implementation.