Installer Steam
connexion
|
langue
简体中文 (chinois simplifié)
繁體中文 (chinois traditionnel)
日本語 (japonais)
한국어 (coréen)
ไทย (thaï)
Български (bulgare)
Čeština (tchèque)
Dansk (danois)
Deutsch (allemand)
English (anglais)
Español - España (espagnol castillan)
Español - Latinoamérica (espagnol d'Amérique latine)
Ελληνικά (grec)
Italiano (italien)
Bahasa Indonesia (indonésien)
Magyar (hongrois)
Nederlands (néerlandais)
Norsk (norvégien)
Polski (polonais)
Português (portugais du Portugal)
Português - Brasil (portugais du Brésil)
Română (roumain)
Русский (russe)
Suomi (finnois)
Svenska (suédois)
Türkçe (turc)
Tiếng Việt (vietnamien)
Українська (ukrainien)
Signaler un problème de traduction
I think for the release of Steam Deck, I will build a similar guide but with minimalist things to do to get Vortex working and link back here for the people interested to go more deeply
Thank you for your feedback :)
OpenAL is certainly not needed anymore for most systems. All recent versions of proton ship an OpenAL library optimized for Wine.
VC Runtime redistributables are not needed anymore. You may need to mark them as installed in the registry, though to fool the applications into not trying to install them.
With DXVK there is rarely a reason to install DirectX. However, on rare occasions you need the DirectX native Shader Pre-compiler libraries. You shouldn't need to install overrides to force this use, DXVK falls back nicely if they are installed (otherwise it falls back onto WineD3D's precompiler libraries, which due to swiss cheese principal may not have the exact same failure.)
I message you from the Steam Deck that I'm fixing formatting issues since the bbcode framework changed
Also fixing little things but from what I tested it is 99% of the commands are compatible and already working with the Steam Deck, that's cool !
@frostwork
Thank you for the advice, the script is now updated with the rename of foreign_install_path to linux_install_path
As far I have tested, linux_install_path can still contain a Windows path symlinking to the Linux OS, so this solves the variable to put in the global script :)
I also tend to create a "share", "local", "source" and "bin" link in my home directory for the appropriate subdirectories, even though these are all in the ".local" tree, and I could get away with just making a non-hidden "local" directory to link to the hidden ".local" directory.
I prefer having them all, but obviously you could just do "local"
(lol @ "forstwork" - not the first time that I read that
Note sure what you wanted to paste with VK_ICD_FILENAMES, this is not something I use in the guide but it is something used by Steam.
Also keep in mind that @forstwork identified something that changed with the proton_evaluatorscript_latest.vdf file so it is very possible the guide is deprecated and requires an update.
I will fully verify and update it soon when I have time, wanted to do this sooner but in August I've been busy finding a new job.
"VK_ICD_FILENAMES": "/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json",
Not sure if rebuilding the guide around my tool is a good idea though, as it should be (imho) a guide for people helping to learn how to roll your own solution.
I doubt my tool will help people learning anything (the wiki might, but I'm afraid there aren't that many actually reading it :)).