search

DavidoTek / ProtonUp-Qt

Install and manage GE-Proton, Luxtorpeda & more for Steam and Wine-GE & more for Lutris with this graphical user interface.
https://davidotek.github.io/protonup-qt
GNU General Public License v3.0
1.18k stars 39 forks source link

Include Non-Steam games when checking if a version is used #224

Closed FolkSong closed 1 year ago

FolkSong commented 1 year ago

I had an issue where I deleted a certain ProtonGE version because it was listed as "unused", then found that a non-Steam game stopped working because in fact it was using that version.

I'm talking about programs that are directly added to Steam through "Games->Add a non-Steam game to my library", not Lutris or Heroic or anything. This is on Steam Deck in my case, but I imagine it's the same anywhere.

If this is not possible then I suggest adding an obvious warning on the main screen that the "unused" label may not be correct.

[Not part of request but just FYI] Incidentally there seems to be an issue with Steam where if you delete the ProtonGE version being used, it won't let you change to a different one, the normal option to choose compatibility tool is greyed out. So the only way to recover is to reinstall the original ProtonGE version, after that you can change it like usual.

sonic2kk commented 1 year ago

Can't re-create this issue on my Linux PC, Non-Steam Games show up in the version check for me and in the "About compatibility tool" dialog.

image

As you are on Steam Deck, are you still using v2.7.7 (i.e. Flatpak), or are you using the AppImage to get the latest v2.8.0? As far as I know, the Flatpak has not yet been updated to v2.8. Support for Non-Steam games was added in v2.8, following #176.

FolkSong commented 1 year ago

Ah, yes after checking I see that I am on 2.7.7, installed through KDE Discover which comes pre-installed on the Deck. I hadn't noticed that it wasn't the latest, I'll close this.

Thanks for catching that!

sonic2kk commented 1 year ago

Should hopefully work once v2.8 is released as Flatpak, keep an eye on the Discover updates section. Feel free to re-open if the issue is not solved in 2.8 :-)