Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
Ever since 1993 the Wine Project (and hence Proton) has played the Catch up game. And just when things start working smoothly, comes an update that disrupts compatibility, because of how Windows changes when handling this or that, that has not been quite implemented in core Wine (that is better to use an older version) except for that particular game or applications that requires the change in order to be functional. I has been this way for all these years. The saving grace being this time, that not only Code Weavers are working on it, but also Valve and Collabra, meaning more man power allocated to these edge cases before they get normalized, in this ever evolving Windows APIs implementations.
Some components are already shared, like shader caches and common Proton runtime stuff.
There are multiple reasons why Valve decided to have this part modular and separated between games.
1. Isolation of dependencies like DirectX, Visual C++ redistributables, game specific DLLs and registry tweaks. If everything is shared in a single WINE prefix, one game dependencies can break anothers... So isolating them helps to avoid DLL hell
2. Stability and compatibility within each prefix, on initial first time setup. Proton handles game specific hacks and/or overrides, like DXVK, Esync and so on, which can be locked at specific version for specific game.
3. Troubleshooting when something breaks is easier with this architecture. You can delete just one game prefix and let Steam to regenerate it. You can debug single game without affecting other games. If you have a shared prefix, this would be debugging nightmare.
4. Version control, as different games can work with different Proton version. This would not work when having a shared prefix.
5. Easier cleanup and management when uninstalling a game. It deletes it's prefix and keeps your system tidy. If there was a global prefix, stuffs would pile up unless tracked manually and removed by hand.
So I think the way they do things now is pretty good and having a global prefix would make things worse.
The first distro that makes a universal wineprefix is gonna be the one that overtakes Ubuntu. When you can just download an exe and download click it and it'll just work, if its a mod or a patch it automatically picks up the game instead of ♥♥♥♥♥♥♥ with winetricks, if its a launcher you can just install it once directly just like Windows instead of having to separately install (and waste space) and be annoyed with constantly having to login separately for each game (and run out of trusted logins so end up having to log in every single time for every instance) and ♥♥♥♥ with Bottles this and Lutris that, oh you wanna install a game while another is already running on a non-Steam launcher? Too bad most won't let you login on two instances at once which you are kinda forced to do by default on linux.
Cross-windows software interaction is like one of my biggest complaints about wine due to everything being designed around being isolated for no real good reason, most things just run on Proton Experimental or latest stable anyways, no reason to separate them unless theres something very broken about wine and separating it is the workaround instead of fixing the actual issue.
One of the most annoying things could be fixed by this it would increase compatibility so much, I have to reboot for old games way more to Windows than new games, at least new games work out of the box on linux, old games where I need to run flawless widescreen or mods or patches alongside the game? Too bad Steam refuses to allow multiple processes to properly run in one of its wineprefixes, unless I guess you were to do some crazy ♥♥♥♥ to put your mod or whatever as a mandatory dependency like a launcher in the games exe so Steam can't refuse to run both.
Such an easy fix for so many issues but everyone who could actually change it has probably convinced themselves for decades that everything is fine the way it is and has been since day one.
While I agree that an option would be fine, having the prefixes separated is the most safe bet in terms of compatibility (no game interferes with the other) and ease of use (just install and play).
I just want to be able to use flawless widescreen for example.
These shouldn't be complicated to fix and would greatly enhance compatibility with mods and old games and various edge cases like this.