I find installing 3rd party compatibility tools cumbersome on the steam deck, steamtinkerlaunch is no exception. Protonup-qt is a massive help. Could steamtinkerlaunch be added to the sources?

https://github.com/frostworx/steamtinkerlaunch

Opened as a draft as I need to see how this impacts switching STL versions + some other extra testing, and I have some other concerns listed below.

I noticed on my PC that ProtonUp-Qt detects my Non-ProtonUp-Qt install of STL (as expected, not a bug or anything imo) but then had the idea that it could be neat if ProtonUp-Qt could see and manage non-root local installs that were not installed by ProtonUp-Qt. There's an arguably valid case that someone might've locally installed STL and would want it to be managed. Since ProtonUp-Qt can currently manage setting STL in the Games List no matter how a user has installed SteamTinkerLaunch in the past.

This PR in its current form makes an initial attempt at this. In the remove_steamtinkerlaunch method I added stl_symlink_path which is either the target for the SteamTInkerLaunch symlink in the compat folder, or None. Then when removing the SteamTinkerLaunch installation we check if that path exists and if it does and if its writable (avoids trying and failing to remove installs in /usr/bin). The regular STEAM_STL_INSTALL_PATH value is moved to an elif block.

I need to do some more testing and I also have a few points I want to raise.

1. This function is, by design, called when a user tries to switch STL versions. This would essentially reinstall SteamTinkerLaunch from its existing location (which is being removed) to ~/stl. This makes sense to me and is what I would consider expected behaviour, but perhaps we should do one of two things:
   • Warn/inform the user (so do this check when they try to update and make them confirm)
   • Preserve the existing SteamTinkerLaunch installation folder between updates (and perhaps ask the user if they want to have their install folder be at ~/stl/prefix). The latter has a few problems around ProtonUp-Qt always being able to "know" where STL is installed. I'm slightly less keen on this idea and I would opt to do the former if it's necessary to tell the user this. The number of users with an STL install like this is probably low, most users I see usually have STL at /usr/bin based on their logs
2. Maybe we should warn users with system-wide STL installs earlier when they try to remove SteamTinkerLaunch. When they press "Remove" maybe we should prompt them and say "Cannot remove SteamTinkerLaunch as it is installed in an unwriteable/system directory", or something to that effect. Probably in 99% of cases, an unwritable SteamTinkerLaunch install will be in a system directory, but there could be an esoteric case where a user has SteamTinkerLaunch in a folder that they have restricted permissions on for some reason.
3. I am not sure if there are any limitations regarding this with Flatpak, since SteamTinkerLaunch could honestly be anywhere on a user's system. It could be in /home/gaben/Downloads/steamtinkerlaunch-master, or it could be 30 folders deep in another drive.

Despite the last two, I would be in favour of keeping SteamTinkerLaunch listed no matter where it is installed on a user's system, as there is the useful case of setting the compatibility tool in the games list.

There is still some work to do but I'd like to hear any feedback. Thanks so much for your continued work on fixing up STL support, I was going to leave a comment about this in the STL discussion issue but I figured I'd actually try and give back a little. No rush on this PR though, we can work through any feedback as and when it comes through and go from there :-)

Thanks!

Implements #86.

Overview

Adds Frostworx's SteamTinkerLaunch utility as a ctmod to allow for streamlined installation and uninstallation across distros and on Steam Deck. Stable releases and the latest git (gated behind ProtonUp-Qt's "Advanced Mode") can be installed. Stable releases show a list of versions in its dropdown whereas the git release shows branches in the interest of potential future-proofing. Currently, SteamTinkerLaunch only has a master branch, but if there are any very experimental features that a user wants/needs, they will be able to install it.

SteamTinkerLaunch Flatpak installation (only for Flatpak Steam) is also supported.

Note: I am not the creator of SteamTinkerLaunch, I just contribute to it every so often and try to help out with the community around it.

SteamTinkerLaunch is installed following the "manual (non-root)" installation method, but we do all the heavy lifting for the user to get them set up, such as setting up the language files and adding SteamTinkerLaunch to PATH. We also manage full uninstallation of SteamTinkerLaunch. This not only makes a manual non-root install a few button clicks, but also makes uninstallation a single click! There's no worry of bloating up your Steam Deck for example with a bunch of miscellaneous files, or having to fumble around with the on-screen keyboard to edit your path.

Features

• Steam Deck support
• Very fast installation with all manual steps taken care of
• Can be easily uninstalled
• Can be updated without clearing the $HOME/.config/steamtinkerlaunch folder, which is important as that's where Vortex/MO2 mods live.
• SteamTinkerLaunch is automatically set as a compatibility tool *and added to all of the user's shell PATHs, meaning SteamTinkerLaunch can be used as a launch option from Steam for Native Linux games. Currently the user will have to enter the absolute path as just typing steamtinkerlaunch %command% doesn't work. There's probably a way to use something like $(which steamtinkerlaunch) %command% but I haven't found it yet.
• As SteamTinkerLaunch is added to the PATH users can run steamtinkerlaunch commands, taking advantage of some of the command line features like steamtinkerlaunch addnonsteamgame.
• From within ProtonUp-Qt, SteamTinkerLaunch can be set as a compatibility tool via the Game List by selecting the Proton-stl option. This is the internal name for SteamTinkerLaunch.
• Users can see which apps and how many are using SteamTinkerLaunch from the About Compatibility Tool window.

Okay, enough advertising, now onto the technical bits!

How It's Installed

The installation steps on Desktop and Steam Deck are very similar. The main difference is that SteamTinkerLaunch will manage downloading its dependencies itself on Steam Deck, and it will also configure its language files correctly.

1. If not on Steam Deck, Check that all the SteamTinkerLaunch Hard Dependencies are installed.
2. The SteamTinkerLaunch tarball is downloaded from GitHub to and extracted inside of $HOME/stl.
3. If not on Steam Deck, we set up the language files automatically based on a map of locales and corresponding SteamTinkerLaunch language files. We get the user's locale (defaults to en_US) and copy the mapped language text file to $HOME/.config/steamtinkerlaunch/lang.
4. The steamtinkerlaunch script downloaded earlier is given an initial run to set up its $HOME/.config/steamtinkerlaunch configuration structure.
5. Add SteamTinkerLaunch to the Shell path for Bash (.bashrc), Zsh (.zshrc), Ksh (.kshrc) and Fish shell ($HOME/.config/fish_variables) if it isn't already present - Yes, this even works on Steam Deck! Any opened terminal sessions and the like will probably need restarted so they can reload their Shell RC files, but this is general shell behaviour.
   • For every shell, a note is placed above the path line to say that it was # Added by ProtonUp-Qt on %d-%m-%Y %H:%M:%S for transparency.
   • For Bash, Zsh and Ksh, if [ -d "<stl_path>" ]; then export PATH="$PATH:<stl_path>"; fi is added to the appropriate Shell RC files.
   • For Fish shell, the fish_variables file is edited to either prepend the <stl_path> to the fish_user_paths variable, or create this variable if it doesn't exist and set it to<stl_path>.
6. Adds SteamTinkerLaunch as a compatibility tool using its built-in command ./steamtinkerlaunch compat add. This creates $HOME/.local/share/Steam/compatibilitytools.d/SteamTinkerLaunch, which has a couple of .vdffiles and asteamtinkerlaunch` symlink file which points to the download location of the earlier SteamTinkerLaunch download.

The whole thing takes less than 15 seconds to download and install on my laptop. On my Steam Deck it's a little longer, still less than a minute, as SteamTinkerLaunch downloads various dependencies on Deck from the Arch repos and Valve's Arch mirrors. Of course, these times can vary and the main factor here will be internet speed and server speed :slightly_smiling_face:

How It's Uninstalled

The uninstallation steps are virtually the installation steps in reverse. We remove the compatibility tool from compatibilitytools.d, we remove $HOME/.config/steamtinkerlaunch and we remove the entire $HOME/stl folder. We also remove SteamTinkerLaunch from the shell paths, for Fish path we take extra care preserving any existing user paths while also removing the note that the paths were modified by ProtonUp-Qt.

Flatpak Paths

The Flatpak will probably need permission for the following paths:

• $HOME/ - For the Shell RC files and to create $HOME/stl if it doesn't exist.
• $HOME/stl/ - All SteamTinkerLaunch install files live here, included the dependencies it downloads for Steam Deck.
• $HOME/.config/steamtinkerlaunch/ - SteamTinkerLaunch configuration folder, this is where the language files go and where SteamTinkerLaunch config stuff goes.
• $HOME/.config/fish/ - We check if this folder exists (to see if Fish is installed, since we can't use shutil.which('Fish') with ProtonUp-Qt Flatpak) and if it does we edit the fish_variables file to add SteamTInkerLaunch to the Fish shell user paths.
• $HOME/.local/share/Steam/compatibilitytools.d/ - Where SteamTinkerLaunch sets up its compatibility tool folder and creates the symlink.

Testing

Right now I have only tested when running my fork of ProtonUp-Qt from source on my laptop (Arch Linux running KDE Plasma Wayland Session) and on my Steam Deck. I have not tested running via an AppImage or via Flatpak. I also have not tested installing SteamTinkerLaunch Flatpak for Flatpak Steam, as I don't have Flatpak Steam installed on any of my systems.

For testing AppImage, I think it would be a case of following the instructions to build an AppImage and then trying it out. For Flatpak though, I'm totally lost :sweat_smile:

Considerations

There are some concerns I have currently:

How To Deal With SteamTinkerLaunch Dependencies In ProtonUp-Qt Flatpak

Following discussion in #86, I'm not sure how to handle conveying to the user that SteamTinkerLaunch has a number of dependencies that need to be satisfied before it'll work. To mitigate this I have included a list of the Hard Dependencies in the Description field, also including a message that on Steam Deck the dependencies are managed.

Installing Versions Incompatible With Steam Deck

A realization I had is that a user might, for any reason, try to install an older version of SteamTinkerLaunch on Steam Deck. However, only SteamTinkerLaunch >= v10.0 support Steam Deck. I was wondering if maybe we should show a warning prompt when the user is on Deck tries to install an unsupported version of SteamTinkerLaunch.

Feedback

This ended up being a fair bit more complex than I initially intended, so please let me know if there's anything I messed up or anything that could be implemented better. I did my best to implement all the functionality needed to install SteamTinkerLaunch in the most efficient way I could, but I'm happy to clarify any decisions I made and change anything to meet the code standards of the project.

The commits aren't squashed yet as I wanted to do that after discussion and code review... and I might need some help with how to do that :sweat:

Huge thanks for all the patience, guidance and advice. It was vital and is very much appreciated :smile:

Describe the bug
WHen double-clicking Flatpak ref, we get an error "Failed to Install/ File not supported" When Running the AppImage, we get empty dialogues

To Reproduce
Steps to reproduce the behavior: FlatPak

1. On Debian 11, xfce, chrome as a regular user (not as root) visting https://flathub.org/apps/details/net.davidotek.pupgui2
2. Clicking install,
3. See the file download,
4. Right-click the file, Go to Permissions->Allow this file to run as a program, Close
5. Double click the file
6. See error

Appimage

1. Visit https://github.com/DavidoTek/ProtonUp-Qt/releases/
2. Download the AppImage file
3. As above, Allow to run as program
4. Double click the AppImage file

Expected behavior
The above files should install or run Proton

Screenshots
Flatpak: Appimage:

Desktop (please complete the following information):

• OS: Debian 11 Bullseye
• Version [e.g. ProtonUp-Qt 2.5.0 AppImage or Flatpak] net.davidotek.pupgui2.flatpakref 2.7.4

Additional context
Do not have Steam or Wine etc installed before starting

Terminal output

Paste the output of running ProtonUp-Qt from the Terminal here.
AppImage: ./ProtonUp-Qt*.AppImage
gwhiz@ip-172-31-40-67:~/Downloads$ ./ProtonUp-Qt-2.7.4-x86_64.AppImage 
ProtonUp-Qt 2.7.4 by DavidoTek. Build Info: Official AppImage by DavidoTek.
Python 3.8.2 (default, Mar 13 2020, 10:14:16) [GCC 9.3.0], PySide 6.2.4
Platform: Linux-5.10.0-18-cloud-amd64-x86_64-with-glibc2.29
Second instance of ProtonUp-Qt found!
gwhiz@ip-172-31-40-67:~/Downloads$ 

Flatpak: flatpak run net.davidotek.pupgui2
flatpak run net.davidotek.pupgui2
ProtonUp-Qt 2.7.4 by DavidoTek. Build Info: DavidoTek Flathub build.
Python 3.9.9 (main, Nov 10 2011, 15:00:00) [GCC 11.3.0], PySide 6.3.2
Platform: Linux-5.10.0-18-cloud-amd64-x86_64-with-glibc2.33
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, wayland-egl, wayland, xcb.

/app/bin/net.davidotek.pupgui2: line 3:     3 Aborted                 python3 -m pupgui2 "$@"
gwhiz@ip-172-31-40-67:~/Downloads$ 

besides the interface is not consistent with the system for me to select a proton version I have to keep pressing the right mouse button if I release the option and sectioned, this behavior is not common .

Describe the bug
When I launch the app and select add versions, it sits on "fetching releases" for quite a while, and when it does fetch them and I hit install, it adds it to the active downloads but never actually downloads them, and the progress bar doesn't pop up.

To Reproduce
Not sure if reproducible, but

1. Launch the app
2. Make sure "Steam" is selected
3. Hit "Add Version"
4. Wait
5. Hit install
6. Nothing happens after adding to active downloads

Expected behavior
Fetches versions pretty instantaneously like I have seen in a lot of videos, and install it pretty instantaneously as well Screenshots
If applicable, add screenshots to help explain your problem.

Describe the bug
When I install Proton-GE in another directory besides /home/me/.steam/root/compatibilitytools.d it will not show up in Steam.

To Reproduce
Steps to reproduce the behavior:

1. Launch Steam and go to Settings->Downloads->Steam Library Folders
2. Add a drive if you haven't yet (I added /media/Games/Steam/)
3. Install a Windows game onto the new drive (This will create the /media/Games/Steam/steamapps/common/ folder if it does not exist)
4. Close Steam
5. Launch ProtonUp-Qt and install a version of Proton-GE to your new drive (I installed it on /media/Games/Steam/steamapps/common/ which were other version of Proton from Steam get installed)
6. Launch Steam and try to change a specific games Proton version to Proton-GE

Expected behavior
In the dropdown menu of selection Proton runners for your Steam game, you should see the Proton-GE version installed from ProtonUp-Qt

Desktop (please complete the following information):

• OS: Linux Mint 20.3
• Version 2.6.5 (AppImage)

For my personal use, I've made a bunch of new graphics that look better in the Steam UI than the current icon. I'm not a pro designer or anything like that. They are CC-BY-SA 4.0 licensed. You may use them if you want.

Steam grid, horizontal:

Steam grid, vertical / Poster:

Icon (small):

Logo / Icon (big):

Created in Inkscape on Steam Deck. Graphics have no intend of being scientifically accurate at all.

Describe the bug
May be two bugs...

I was running protonupqt successfully for 2 months but when I went to check for new proton updates today the app would not open the game list when the button was pressed. I rebooted and it was the same. I'm using the dec 8 preview build on my steamdeck.

Next I attempted to remove and reinstall. The discover app aborts the install, complaining about the flatpak having a bad commit signature key with a bad date associated. Removing local data from previous install did not resolve.

To Reproduce
Steps to reproduce the behavior:

1. Open app

2. Click 'show games list

3. Nothing happens

4. Search app in Discovery, install

5. See error

Expected behavior
Loads games list for proton selection.

Installs via discovery without error.

Screenshots
N/a

Desktop (please complete the following information):

• Platform: Steam Deck
• System: SteamOS 3.4 preview Dec 8
• Version: ProtonUp-Qt 2.7.6
• How did you install ProtonUp-Qt?: Discover app store

Additional context
Add any other context about the problem here.

Terminal output

Open the Terminal app and type one of the following commands and press Enter (The app is called "Konsole" on Steam Deck):

If you installed ProtonUp-Qt via Flatpak (Discover on Steam Deck), type:
flatpak run net.davidotek.pupgui2

If you have downloaded the AppImage, navigate to the folder containing the AppImage file and type:
./ProtonUp-Qt*.AppImage

Try to replicate the bug and paste the text output of the command here afterwards.

Describe the bug
On the Steam Add Version section of the application, it crashes when double clicking the version list.

To Reproduce
Steps to reproduce the behavior:

1. Open the Add version dialog
2. Double click on the version list
3. gnome-shell crashes

Expected behavior
List should open and immediately close as the first click invokes the list and the second re-selects the current version.

Screenshots
https://streamable.com/6w9lmy

Desktop (please complete the following information):

• Platform: PC
• System: Nobara 36
• Version: ProtonUp-Qt 2.7.6
• How did you install ProtonUp-Qt?: Flatpak

Additional context
On the same setup, gnome-shell doesn't crash under X11 or if the AppImage is used. Additionally, disabling Wayland windowing system under Flatseal so the app uses XWayland instead also prevents this from happening.

Terminal output

$ flatpak run net.davidotek.pupgui2 
ProtonUp-Qt 2.7.6 by DavidoTek. Build Info: DavidoTek Flathub build.
Python 3.10.6 (main, Nov 10 2011, 15:00:00) [GCC 12.1.0], PySide 6.4.0.1
Platform: Linux-6.0.9-202.fc36.x86_64-x86_64-with-glibc2.35
Loading locale en / en_US
Loaded ctmod GE-Proton
Loaded ctmod Wine-GE
Loaded ctmod Boxtron
Loaded ctmod Kron4ek Wine-Builds Vanilla
Loaded ctmod Lutris-Wine
Loaded ctmod Luxtorpeda
Loaded ctmod Proton Tkg
Loaded ctmod Roberta
cat: /etc/lsb-release: No such file or directory
Loaded ctmod SteamTinkerLaunch
cat: /etc/lsb-release: No such file or directory
Loaded ctmod SteamTinkerLaunch-git
Loaded ctmod DXVK
Loaded ctmod DXVK Async
Loaded ctmod DXVK (nightly)
qt.pysideplugin: Environment variable PYSIDE_DESIGNER_PLUGINS is not set, bailing out.
qt.pysideplugin: No instance of QPyDesignerCustomWidgetCollection was found.
Gamepad error: No gamepad found```

Implements #73

Overview

Adds support for downloading vkd3d for Lutris. Like with manual DXVK version downloads, this has to be entered manually in the Advanced Options for a Lutris game, but this is general Lutris usage and would apply if this was done manually as well :-)

Two sources are added here: vkd3d-proton (the project used by Valve in Proton) and vkd3d-lutris (a fork of this project with seemingly minimal changes, at least at the time of writing) - The latter is just a Lutris fork of upstream vkd3d-proton simply called "vkd3d" - This is slightly further behind than regular vkd3d-proton, and releases as a .tar.xz instead of a .tar.zst like vkd3d-proton does.

The benefit of having both is the ability to use the latest vkd3d release from upstream vkd3d-proton and using it "raw", in case there are any changes in the downstream Lutris build. Upstream is on v2.7, Lutris is on v2.6. A brief skim of the commits appears like there are no real changes in the fork, maybe they just host separately for packaging? I am not sure of the reason, but both should work. The folder structure is identical.

This change does not impact Steam, as this is irrelevant to Steam.

Implementation

Two Ctmods

I considered taking a similar approach to what I did with SteamTinkerLaunch: Having one "main" ctmod for vkd3d, and then having a separate one for vkd3d-lutris. Since I thought the code would be much the same, just different URLs.

It turns out the URLs are different, and some of the code needed for vkd3d-proton was different. The release asset extensions are different and the extraction and paths would be different. Since they are in reality two separate repositories, I figured having two separate ctmods made the most sense in the end and would be cleaner as there wouldn't be a bunch of conditional checks.

Zstandard Library

Okay, the main "problem" with this implementation. Upstream vkd3d-proton is releases as a .tar.zst file, and this is not supported by the Python tarball library. There is a stale request for this upstream, but I wouldn't hold my breath on this. And even so, ProtonUp-Qt does not use the latest Python version, so a version bump would be required to make use of that.

To implement this, I used the Zstandard Python library and mostly followed an implementation from a GitHub Gist. It basically uses this Zstandard library to extract the tar data to a temporary tarfile, which is then extracted properly using the tarfile library.

The problem is that this adds an extra dependency. Creating a PR that adds an extra dependency is probably not very helpful, and I am really sorry about that. I did investigate to see if there was a way to do this without pulling in an extra dependency, but that is how I came across the upstream Python issue.

If there is a way to fix this, I would be happy to remove this dependency.

Remaining Issues

The only remaining issue with this PR is that the vkd3d downloads don't show up in the compatibility tool list. I figure the Lutris runner vkd3d directory just needs to be added somewhere in the code, but I couldn't figure out where to put it.

Apart from this issue, I am happy with the state of the PR and think it's ready for review.

Phew, I was meant to take a break but I couldn't resist trying to tackle this :sweat_smile: As always, feedback is appreciated! :-)

Add a game list for the Heroic Games Launcher.
The game list could be implemented in a similar way as the Steam game list.

Details

(As of December 2022)

Configuration for the Flatpak version of HGL can be found in ~/.var/app/com.heroicgameslauncher.hgl/config/heroic
Additional configuration for Legendary is stored in ~/.var/app/com.heroicgameslauncher.hgl/config/legendary

{
	"games": [
		{
			"runner": "sideload",
			"app_name": "sPZQ5kmzYj5KnZKdxE2bR1",
			"title": "Test Title",
			"install": {
				"executable": "test",
				"platform": "Windows"
			},
			"folder_name": ".",
			"art_cover": "file:///app/bin/heroic/resources/app.asar/build/assets/heroic_card.dae295a6.jpg",
			"is_installed": true,
			"art_square": "file:///app/bin/heroic/resources/app.asar/build/assets/heroic_card.dae295a6.jpg",
			"canRunOffline": true
		}
	]
}

{
	"games": [
		{
			"runner": "gog",
			"store_url": "https://gog.com/en/game/akalabeth_world_of_doom",
			"developer": "Richard Garriott",
			"app_name": "1207666073",
			"art_cover": "https://images-1.gog-statics.com/56262850671fd7232b8ff46deba530007ff7a437fab0ddd67147f8d41aa6bca0.jpg",
			"art_square": "https://images.gog.com/511cf474562bdaf2c8b9eec1a0c94e1eb5cf4e3900a618516adff2ebd89118e0.jpg?namespace=gamesdb",
			"cloud_save_enabled": false,
			"extra": {
				"about": {
					"description": "In the game, the player character visits Lord British and is instructed by him to kill certain monsters. The final mission is to kill a balrog, and after this has been accomplished, Lord British proclaims that \"thou hast proven thyself worthy of knighthood\".",
					"longDescription": ""
				},
				"reqs": []
			},
			"folder_name": "",
			"install": {
				"is_dlc": false
			},
			"is_installed": false,  /* comment: install status */
			"namespace": "akalabeth_world_of_doom",
			"save_folder": "",
			"title": "Akalabeth: World of Doom",
			"canRunOffline": true,
			"is_mac_native": true,
			"is_linux_native": true
		}
	],
	"totalGames": 1,
	"totalMovies": 0,
	"cloud_saves_enabled": true
}

{
  "sPZQ5kmzYj5KnZKdxE2bR1": {
    "autoInstallDxvk": true,
    "autoInstallVkd3d": true,
    "preferSystemLibs": false,
    "nvidiaPrime": false,
    "enviromentOptions": [],
    "wrapperOptions": [],
    "showFps": false,
    "useGameMode": false,
    "language": "",
    "wineVersion": {
      "bin": "/home/user/.local/share/Steam/compatibilitytools.d/GE-Proton7-43/proton",
      "name": "Proton - GE-Proton7-43",
      "type": "proton"
    },
    "winePrefix": "/home/user/Games/Heroic/Prefixes/TitleTest"
  },
  "version": "v0",
  "explicit": true
}

{
  "5b60142e120c4f2d88027595c21d4a04": {
    "app_name": "5b60142e120c4f2d88027595c21d4a04",
    "base_urls": [
      "https://fastly-download.epicgames.com/Builds/Org/o-bthbhn6wd7fzj73v5p4436ucn3k37u/c5a7ca9faed74eb99c1a7291eec2a2ff/default",
      "https://epicgames-download1.akamaized.net/Builds/Org/o-bthbhn6wd7fzj73v5p4436ucn3k37u/c5a7ca9faed74eb99c1a7291eec2a2ff/default",
      "https://download.epicgames.com/Builds/Org/o-bthbhn6wd7fzj73v5p4436ucn3k37u/c5a7ca9faed74eb99c1a7291eec2a2ff/default",
      "https://download2.epicgames.com/Builds/Org/o-bthbhn6wd7fzj73v5p4436ucn3k37u/c5a7ca9faed74eb99c1a7291eec2a2ff/default",
      "https://download3.epicgames.com/Builds/Org/o-bthbhn6wd7fzj73v5p4436ucn3k37u/c5a7ca9faed74eb99c1a7291eec2a2ff/default",
      "https://download4.epicgames.com/Builds/Org/o-bthbhn6wd7fzj73v5p4436ucn3k37u/c5a7ca9faed74eb99c1a7291eec2a2ff/default"
    ],
    "can_run_offline": true,
    "egl_guid": "",
    "executable": "DOOM64_x64.exe",
    "install_path": "/home/user/Games/Heroic/DOOM64",
    "install_size": 120291379,
    "install_tags": [],
    "is_dlc": false,
    "launch_parameters": "",
    "manifest_path": null,
    "needs_verification": false,
    "platform": "Windows",
    "prereq_info": null,
    "requires_ot": false,
    "save_path": null,
    "title": "DOOM 64",
    "version": "2124"
  }
}

essentially this is how the feature works, so whenever the user opens protonup-qt and downloads a newer version of a runner (except proton, I tried that and it won't work with steam unfortunately), let's say wine-ge, we will symlink this newer version to wine-ge-latest (or something similar), then all the user has to do to keep wine-ge updated is just download a newer version of wine-ge. if the user chooses to make the game use wine-ge-latest in heroic or lutris, the symlink will just automatically point it to the newer version.

steps to do it manually:

1. symlink latest wine-ge with name wine-ge-latest (use this name every time you perform the replacement), so for example wine-ge-proton7-34 will be symlinked to wine-ge-latest

an alternative method would be to rename the folders, but with that approach I can imagine things getting very messy, very fast since there is no way to determine the version number

Please fill out following when reporting a new bug:

Describe the bug
When choosing to install a compatibility tool the drop-down list does not populate with available versions

To Reproduce
Steps to reproduce the behavior:

1. Click Add version
2. Choose a comparability tool

Expected behavior
A list of versions of the selected compatability tool should be displayed in the version drop-down list.

Screenshots

Desktop (please complete the following information):

• Platform: Laptop
• System: Pop!_OS 22.04 LTS x86_64
• Version: For example ProtonUp-Qt 2.7.6
• How did you install ProtonUp-Qt?: Flatpak from the Pop!_Shop

Terminal output

Python 3.10.6 (main, Nov 10 2011, 15:00:00) [GCC 12.1.0], PySide 6.4.0.1
Platform: Linux-6.0.6-76060006-generic-x86_64-with-glibc2.35
Gtk-Message: 13:45:56.375: Failed to load module "appmenu-gtk-module"
Gtk-Message: 13:45:56.415: Failed to load module "canberra-gtk-module"
Gtk-Message: 13:45:56.415: Failed to load module "canberra-gtk-module"
Qt: Session management error: None of the authentication protocols specified are supported
Loading locale en / en_CA
Loaded ctmod GE-Proton
Loaded ctmod Wine-GE
Loaded ctmod Boxtron
Loaded ctmod Kron4ek Wine-Builds Vanilla
Loaded ctmod Lutris-Wine
Loaded ctmod Luxtorpeda
Loaded ctmod Proton Tkg
Loaded ctmod Roberta
Loaded ctmod SteamTinkerLaunch
Loaded ctmod SteamTinkerLaunch-git
Loaded ctmod DXVK
Loaded ctmod DXVK Async
Loaded ctmod DXVK (nightly)
qt.pysideplugin: Environment variable PYSIDE_DESIGNER_PLUGINS is not set, bailing out.
qt.pysideplugin: No instance of QPyDesignerCustomWidgetCollection was found.
Gamepad error: No gamepad found.

Can you add a feature to update Custom proton DXVK files

idk if its hard to do, but copy pasting dxvk everytime is becoming painfully tiering, i do a lot of testing so ill love a way and i sure others will also love that feature.

On Ubuntu, there is no .deb package and putting up flatpak support takes terminal commands and too much effort for a new comer to Linux (and Ubuntu is the main destination).

Referring to this partly solved issue (a flatpak was created but snap had a hurdle) https://github.com/DavidoTek/ProtonUp-Qt/issues/3

The technic that provides the same thing (to access those needed files / folders) as in the flatpack package is: https://snapcraft.io/docs/personal-files-interface

"The personal-files interface provides access to the specified files in the user’s home. This interface gives privileged access to the user’s data.

Auto-connect: no Super-privileged: yes "