Skip to content
This repository has been archived by the owner on Sep 3, 2021. It is now read-only.

Proton and the game being in different libraries fails #17

Closed
Sanaki opened this issue Sep 14, 2018 · 1 comment
Closed

Proton and the game being in different libraries fails #17

Sanaki opened this issue Sep 14, 2018 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@Sanaki
Copy link

Sanaki commented Sep 14, 2018

I have two steam libraries, one on my HDD and one for particularly read-heavy games on my SSD. Because of how valve set it up, proton installs to the last library you installed to rather than letting you pick or targeting your primary library. In my case, Proton landed on my SSD, in /usr/local/steam/.... As far as I can tell, there's no way to configure protontricks to locate proton in one library when the game itself resides in another (such as ~/.steam/steam/...). I manually moved proton back to my main library for the time being, but having to move it each time I need to use protontricks... well, will make me not use it.

EDIT: And while I could likely remedy this for myself with a symlink (both partitions are ext4), people with libraries on filesystems that don't support symlinks properly won't have that luxury.

@Sirmentio Sirmentio added bug Something isn't working enhancement New feature or request help wanted Extra attention is needed and removed bug Something isn't working labels Sep 15, 2018
@lucifertdark
Copy link

Thanks Sirmentio, Protontricks is essential & much appreciated. 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants