Version 2.0

[R1kaB3rN]

Potential/non-exhaustive list of features that I think would make for a good umu-launcher v2.0 release:

• Build the Steam Linux Runtime from source.
• Customize the Steam Linux Runtime environment.
• Add environment variable to allow clients to control the Steam Linux Runtime variant (e.g., sniper. soldier, etc.)
• Add support/detection for a Steam Input-related solution.
• Add environment variable to opt into auto falling back to winevulkan instead of DXVK. Helpful for cases when users cannot meet DXVK's Vulkan requirements, while still getting the latest fixes for games.
• Add environment variable to opt into a single wine prefix model.
• Add support for delta updates for compatibility tools instead of extracting from tar archives.

In particular, I think the first 4 are important.

Also, maybe:

• Obsolete creating Zenity windows.
• Obsolete reading from TOML configurations.
• Making python-xlib an optional dependency.
• Remove python-filelock dependency.

[beh-10257]

another suggestion you can even create a notification instead of zenity
just a notification saying downloading protonGE9-41
and than download complete or whatever

[R1kaB3rN]

another suggestion you can even create a notification instead of zenity just a notification saying downloading protonGE9-41 and than download complete or whatever

A lot of clients already support this in some form. While we could enable the feature behind an environment variable, I think that feature is a bit out of scope for this tool and would be distracting of its purpose. It's also not clear to me how really useful it would be

[R1kaB3rN]

So for new features, ideally, I think it should be things only umu-launcher is in a unique position to do (e.g., configuring the container environment) or would want to standardize for the client because it would be non-trivial to implement for them

[R1kaB3rN]

Right now, we currently make an exception when downloading Proton as Lutris didn't do it at the time. It's not anything special at the moment, and we could easily get rid of that code as Lutris is now doing it. However, with delta updates, we can keep that role of managing Proton and standardize having only 1 Proton on the user's system. The client will just need to allow the user to subscribe to that model

[Tiagoquix]

To add to the list: remove relations with ~/.steam/root/compatibilitytools.d/ and use only UMU-managed copies of Proton (be it GE or the UMU Proton itself).

[GloriousEggroll]

To add to the list: remove relations with ~/.steam/root/compatibilitytools.d/ and use only UMU-managed copies of Proton (be it GE or the UMU Proton itself).

not sure what you mean by this. it's confusing. We still want umu to place downloaded proton builds into that folder so that they can be used by steam if needed.

[Tiagoquix]

see #362 (comment)

[NBAB42Bq]

My feature request would be:

• Add an update-flag for updating just the steam runtime

Currently I have an update-script which runs 'umu-run "" > /dev/null' when I update my system so that I can directly dive into gaming and don't need to update steamrt first. But I would appreciate something like 'umu-run --update' without this unnecessary Protonfixes-output in the terminal...

[GloriousEggroll]

guys please this isn't the place for feature requests. this is planning being done by us internally. if you have a feature request open a new ticket so it can be properly discussed on its own.

@Tiagoquix We dont want to isolate UMU-Proton from steam. It can still be used with steam games.

[NBAB42Bq]

Hey, sorry. I will open a new ticket :)