Proton-TKG: Add experimental support for umu-launcher

[Artewar67]

It adds the following things:

Modifies the proton startup script to run correctly with umu-launcher

Adds umu-protonfixes that are needed for the launcher to work.

Changes the version of the Steam runtime library to Sniper

Also another question: I want to change the version of Proton to 9, but there is a question. Are there any problems with this version?

[Artewar67]

To run with umu-launcher you also need to put the environment variable UMU_NO_RUNTIME="pressure-vessel" so that it would start.

[loathingKernel]

To run with umu-launcher you also need to put the environment variable UMU_NO_RUNTIME="pressure-vessel" so that it would start.

This env variable disables the use of Sniper runtime in umu. Umu presently consider this a debugging-only feature. If it is required for proton-tkg to work with umu, it is likely that it is not being built in the runtime correctly.

[Artewar67]

This env variable disables the use of Sniper runtime in umu. Umu presently consider this a debugging-only feature. If it is required for proton-tkg to work with umu, it is likely that it is not being built in the runtime correctly.

The problem is that wine, dxvk and vkd3d are still being built against the system libraries and compiler in our script, and this prevents umu-launcher from running it #1202 Open-Wine-Components/umu-launcher#99

Need to change the build script so that proton-tkg is built against steam runtime. In the meantime, umu launcher support is currently implemented rather poorly and experimentally.

[loathingKernel]

That makes sense. What I find odd is setting the required_tool_appid in toolmanifest.vdf to Sniper. This will cause these builds to not work in Steam as Steam will force Sniper in this case. So I am a bit confused what was the intention here.

[Artewar67]

I apologize for accidentally removing the branch.

[Tk-Glitch]

I apologize for accidentally removing the branch.

No worries :)

[Tk-Glitch]

Proton 9 is quite robust these days, but the tooling is an issue on our end on the build script part. The building approach changed at some point on experimental 8 and until we can properly build against it (I failed to fix this til now, and lower availability hasn't helped) we're enforcing the commit before those breaking changes for the tooling:

wine-tkg-git/proton-tkg/proton-tkg.sh

Lines 968 to 971 in 031bc3e

	# Tooling compilation needs an update for latest BE - Use slightly older tooling for now
	if [ -n "$_bleeding_tag" ] || [[ "$_proton_branch" = experimental_8* ]] || [[ "$_proton_branch" = *9* ]]; then
	git checkout f5e9c76903e4e18e0416e719a6d42d0cb00998aa
	fi

So changing the tooling branch effectively has no effect currently on Proton 8 (exp or be) and 9 (any).

The _nosteamruntime thingy should break more than it fixes in its current form so I'm intrigued. Did you test this successfully against various games?

[Artewar67]

I used proton-tkg from the upstream wine branch and which games worked and which still need something else customized

Two games on Unity: No problems, everything started correctly.

Barony: No problems either

Pacific Drive (UE4): Game crashes because when running umu-launcher proton-tkg VKD3D_FEATURE_LEVEL was set to 12_1 but my video card doesn't support rtx and I had to set 12_0 myself to get the game to start up. Also game need vcrun2019 or vcrun2022

Stalker Anomaly: The game needs to install d3dx* and d3dcompiler_* via winetricks to run.

[Artewar67]

I also found one problem

My patch caused regression and in the file compatibiltytool.vdf the proton version is not written and the default TKGVERSION is left

[Tk-Glitch]

Weird. Will check that out too. Thanks Artewar67!