Hi Kron4ek,

I've just tried it and ccache helps a lot for the 2nd build of wine in the 32-bit chroot. It speeds up build time a lot.

inside both chroots

apt-get install ccache -y

To update environment variables CC, CXX, CROSSCC, CROSSCXX

Please update to your needs accordingly. Idea is to add ccache before calling gcc or mingw64

for i in 32 64
do

    case ${ARCH_TYPE} in 
    amd64)
            echo $i | grep -q 64 && { _cflags=" -march=x86-64 -msse3 -mfpmath=sse -O2 "; cross_cc="x86_64-w64-mingw32-gcc"; cross_cxx="x86_64-w64-mingw32-g++"; }
            echo $i | grep -q 32  && { _cflags=" -march=i686 -msse2 -mfpmath=sse -O2"; cross_cc="i686-w64-mingw32-gcc"; cross_cxx="i686-w64-mingw32-g++"; }
            ;;
    esac

export CC="ccache gcc-9"
export CXX="ccache g++-9"
export CROSSCC="ccache ${cross_cc}";
export CROSSCXX="ccache ${cross_cxx}";
export CFLAGS=" ${_cflags} -pipe -ftree-vectorize"
export CXXFLAGS="${CFLAGS}"
export LDFLAGS="-Wl,-O1,--sort-common,--as-needed"
export CROSSCFLAGS="${CFLAGS}"
export CROSSLDFLAGS="-Wl,-O1,--sort-common,--as-needed"

done

It seems the Proton builds ignore the prefix environment variable. No matter what I set and however I set it, Proton always uses the default ~/.wine prefix.
WINEPREFIX=/path/to/custom/prefix /opt/wine-4.11-3-proton-amd64/bin/winecfg
shows as if launched as:
WINEPREFIX=~/.wine /opt/wine-4.11-3-proton-amd64/bin/winecfg
Tested with your builds of Proton 4.2-8 and 4.11-3, behaviour is as expect with standard wine using your build of 4.15.

Is this issue related to https://github.com/ValveSoftware/Proton/wiki/Proton-FAQ#how-does-proton-manage-wine-prefixes ?

First of all: since wine-tgk is basically wine + proton + various hacks, is VKD3D present or I was wrong thinking that tgk is wine + proton?

Asking because err:module:open_builtin_so_file failed to load .so lib "/usr/lib/wine/x86_64-unix/d3d12.dll.so"

Can you add this build variant for older games?

Some games have cutscene videos, that work with vanilla wine on *Ubuntu 20.04, provided you have the required libs installed.

Ultra Street Fighter IV, for example. Videos will play with vanilla wine, provided you have the following libs installed:
gstreamer1.0-libav:i386
gstreamer1.0-plugins-bad:i386
gstreamer1.0-plugins-base:i386
gstreamer1.0-plugins-good:i386
gstreamer1.0-plugins-ugly:i386
gstreamer1.0-x:i386
libgstreamer-plugins-bad1.0-0:i386
libgstreamer-plugins-base1.0-0:i386
libgstreamer-plugins-good1.0-0:i386
libgstreamer1.0-0:i386

But videos won't play with your wine builds because winegstreamer is disabled on compilation.

I tested your wine-wayland test build on KDE neon User Edition 5.20.2, and it opens two black windows during wine-boot, and nothing happens for quite some time, and I have to kill them both which ruins the whole wine-boot process.

KDE neon = Ubuntu LTS + the latest KDE Plasma

Steps to reproduce:
mount up, press forward key, try using right mouse button to control the camera.
Results:
camera ends up under my raptors tail, real fast
Expected results:
camera rotates to desired location

Is there an environment variable to disable raw input and use staging input instead?

On high CPU-usage scenarios, enabling FSYNC will add a strange delay, basically you keep pressing W (for example) but when you stop wine will think that the key is still pressed, for a few second or just half a second... it's a bit randomic

Hi!

I see, the proton build uses the name "steamuser" as the username, while the other builds usually use the name of the user logged in to the system ($USER). For compatibility reasons, would it be possible for the proton build to use $USER as well?

Thanx

log of the error.docx
In wine64 side everything works except graphic problem on some games like rise of the Tomb rider and watch dogs 1 I don't know if it is my gpu or wine but my main problem is on wine32 (./wine) it opens winecfg,cmd,and regediter but on others it throws use Truetype font please install a version of freetype greater than or equal to 2.0.5.
I have installed it but I don't know how to install 32bit version

My spec
Intel core i5 3340m
Intel hd 4000
4gb ram
10 gb swap virtual memory

Could you add the unofficial Proton builds, GE to you collection?

I'm not good guesser

Would it be possible to provide a "complete" proton package?
Currently the proton archives "only" contain the wine part of the proton packages (so basically the 'dist' subdirectory ('files' in proton experimental)), and the proton files from the proton main dir are missing.
It would be very convenient to be able to download a package and use it directly instead of merging it with some existing proton files manually, and also would ship its own version

Hey Kron4ek!
It has been a while, I hope you're fine.
I just found your Wine-Builds project via this imho very important fix and would like to thank you for providing those packages - it is always good to have a choice :)
If you don't mind I'd like to also add support for both your wine and proton packages into my steamtinkerlaunch.
Keep up your great work! 👍

I want to ask some questions about your improved-wine releases.

• Do your improved builds support vkd3d?
• There is 2 different hacks for Media Foundation that install native windows dlls. Can your proton_mf_hacks.patch replace these two hacks?!

First issue: Steam (windows version) won't create the shortcut as .desktop files like wine-staging used to do, so far this issue occur both on 6.5 and 6.6.
Second issue (the worst so far): when installed, steam (could be everything else) creates a shortcut on the application menu, the usual .desktop file. Basically I had to change a line from wine start /Unix "/home/gabriele/.wine/drive_c/Program Files (x86)/Steam/steam.exe" to Exec=wine "/home/gabriele/.wine/drive_c/Program Files (x86)/Steam/steam.exe".
The bad thing is that this issue led to a manual creation of a "/opt/wine-staging/bin/wine %U" argument so I could launch applications and games through double-click.
Could those problem be related to the fact that you simply have to copy the files instead of installing wine?

EDIT: Stupid brain, I just figured something out: "winemenu something" is disabled by your build config, so the first problem is that, while the second problem relies on a wine 6.5 bug, still not solved in wine 6.6, but I think that the change I had to make is related to the first problem

Hi Kron4ek,

When using your builds wine-5.19-staging-tkg-amd64.tar.xz and wine-5.20-staging-amd64.tar.xz, DualShock 3 & 4 controllers are able to be detected and used in games through Lutris.

When using wine-5.20-staging-tkg-amd64.tar.xz DualShock 3 & 4 controllers are not able to be detected or used in games through Lutris.

System
OS: Debian Sid
Desktop Environment: KDE
Kernel: 5.9.0-1

Thank you for the service you provide!

There is something weird about wine-staging 5.13. This version didn't reach Ubuntu at all, the latest version is wine-staging 5.12, and that didn't happen before, and I can build wine 5.13 successfully, but patchinstall.sh always fails to add staging patches.

Also, you didn't add a new release for wine-staging as you always do. What is wrong with wine-staging 5.13?!

I have a few questions in mind that I don't have an answer for

1- How can I use Fsync with your Proton build version 4.11?

2- Do I need to use your FAudio builds with it to be able to use FAudio? Or is it like normal Wine builds that use FAudio installed in my system?

I use KDE Neon (Ubutnu 18.04), and I use this external repository for FAudio
https://launchpad.net/~cybermax-dexter/+archive/ubuntu/sdl2-backport

So... I'm using your build since 2 months and only a few days ago I realized: fsync is not being used, I'm a fool.
I set the variable in .bashrc so everything uses it, no man's sky (pure vulkan game, no DXVK) is still slow as hell.
Then I realized something: if I run wine NMS.exe fsync will start, steam will start and the game will open, in the fastest way I could possibly imagine, before that first try it was slooooooowwwwwwww. Yes I own the game so steam is required.

BUT if I open steam, through the shortcut and then open the game inside steam, fsync will not start, that's because that shortcut has wine /start /unix something path to "steam.exe" and it breaks everything.
I connect every game to steam, so I can create a shortcut through it, so the icon will be present and my friends can see me online while playing and maybe join me.

How can I fix it?
Keep in mind that every shortcut is like this env WINEPREFIX="/home/gabriele/.wine" /opt/wine-staging/bin/wine C:\\\\windows\\\\command\\\\start.exe steam://rungameid/15531102088879669248 basically that start.exe is stupidly broken in my honest opinion

Basically I'd like to know how to use the new implementation of Futex present on xanmod-kernel (5.16 kernel future patch)

I use your own binaries for the 2 past years now. I thank you for sharing them
Can you please share Proton 5.0.9 when you get free time.
Hope you enjoy your Summer.
Be safe
Regards

The command proton_use_seccomp=1 %command% is required by the new Denuvo games, and it works with Proton, but I need to use Steam in order for that to work.

I simply want to use this command with your Proton builds outside of Steam. How can I do that?

I can't use winetricks with the latest wine-staging-improved build (wine-staging 5.8)

It gives me this error message:

wine cmd.exe /c echo '%AppData%' returned empty string, error message ""

I tried to remove WINEPREFIX that I use with wine-staging-improved, and create a new one, but still gets the same error message.

Do you think you would be able to upstream patches from https://github.com/varmd/wine-wayland for wayland support?

Hello,
Thanks for providing the build_wine.sh script. I'd like compile staging-tkg without the fshack patch. Would that be possible?

Thanks

Could you please add this patch to your wine-builds? >>> https://github.com/Frogging-Family/community-patches/blob/master/wine-tkg-git/Do_not_fail_if_LDR_MODULE.Flags_is_modified.mypatch

It helps to run some games that normally don't run on wine, and building custom wine build on Ubuntu is so hard, because dependencies are so problematic, and hard to resolve.

If you don't like adding this patch to your improved-wine build just close this issue, and thank in advance whatever you decided to do it or not.

Every time I launch Guild Wars 2 with wine from your release "wine-6.17-staging-tkg-amd64" an error notice appears (see screenshot attached). I doesn't affect the functioning of Guild Wars 2, it's just annoying...

Linux distribution:

$ cat /etc/os-release
NAME="Linux Mint"
VERSION="19.3 (Tricia)"
ID=linuxmint
ID_LIKE=ubuntu
PRETTY_NAME="Linux Mint 19.3"
VERSION_ID="19.3"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.linuxmint.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=tricia
UBUNTU_CODENAME=bionic

Winetricks version (installed with Linux Min/Ubuntu package manager 'sudo apt install winetricks'):

$ apt list winetricks
Listing... Done
winetricks/bionic,bionic,now 0.0+20180217-1 all [installed]

$ winetricks -V
20180217 - sha256sum: 1b156c616174f41df79d72a90c52eb2b110c63a6e8ecb865d303a8f9f0908924

The "script" I use to launch Guild Wars 2:

#!/bin/bash

WINEPREFIX=/home/pat/wine_for_gw2

WINE_CMD=/home/pat/wine-6.17-staging-tkg-amd64/bin/wine64

GW2_PATH=${WINEPREFIX}/drive_c/Program\ Files/Guild\ Wars\ 2
GW2_EXE_PATH=${GW2_PATH}/Gw2-64.exe

# Actual launch...
WINEPREFIX=${WINEPREFIX} WINEESYNC=1 WINEDEBUG=-all __GL_DEFAULT_LOG_ANISO=0 __GL_LOG_MAX_ANISO=0 __GL_FSAA_MODE=0 __GL_THREADED_OPTIMIZATIONS=1 __GL_SYNC_TO_VBLANK=0 __GL_YIELD=NOTHING LOGFILE=/dev/null ${WINE_CMD} "${GW2_EXE_PATH}"

Screenshot of error:

Backtrace of error (from "Show Details" of error window):
backtrace_20211227.txt

Hi Kron4ek,

Your Proton 6.3-3 is broken and may not work for all games. You may got something like.
Killed Process

Culprit are the 3 latests commits in Wine from Proton.
You may have to reverse them

cd /opt/Sources/Proton-Experimental-6.3/wine/
git format-patch -r -n3 a80652ca4c8d69591e3242019e487502510323ea
patch -R -Np1 -i /opt/Sources/Proton-Experimental-6.3/wine/0001-server-Do-not-cancel-process-sigkill-in-kill_process.patch
patch -R -Np1 -i /opt/Sources/Proton-Experimental-6.3/wine/0002-server-Add-sigkill-timer-even-if-msg_fd-is-closed.patch
patch -R -Np1 -i /opt/Sources/Proton-Experimental-6.3/wine/0003-ntdll-Close-server-socket-before-calling-exit.patch

Hope it helps
Regards

configure: libcups 64-bit development files not found, CUPS won't be supported.
configure: libnetapi not found, Samba NetAPI won't be supported.

These would probably be solved by installing libcups2-dev and samba-dev (respectively) in the environment(s).

When I try to compile and add custom patches first I add: export DO_NOT_COMPILE="true" Then run: sudo ./build_wine.sh

Then when its downloaded I set: export DO_NOT_COMPILE="false" and: export CUSTOM_SRC_PATH="/home/malik/src" then again run: sudo ./build_wine.sh

It will delete everything in /home/malik/src then finish.

wine-6.0-rc4-staging-tkg-amd64 seems to have lost something in wine-6.0-staging-tkg-amd64. On the rc4 version things are pretty good on one PC (30 minutes play time without a problem) and frequent game freezes on another PC with different hardware (though same Nvidia GPU) and same software, Kubuntu 20.10.

Anyway, if I play cyberpunk with the 6.0 version (not rc4) the screen goes black for several seconds, then returns to normal for a few seconds and keeps repeating this behaviour. Game does not work at all on 5.13 experimental.

Running Warframe through Lutris with a custom runner pointing to wine-6.6-staging-tkg-amd64/bin/wine64 and in the launcher options, dx12 experimental is available. Switch runner to wine-6.7-staging-tkg-amd64/bin/wine64 and the launcher no longer has a dx12 experimental option, just dx11. World of Warcraft through Lutris with the 6.7 runner works fine with dx12. I just checked using wine-6.7-staging/bin/wine64 and wine, and have the same issue. Any ideas on what I can try or is this an upstream issue introduced in the current build of wine?

Rockstar Games Launcher fails to update

Can you add the pipe_nowait patch from Proton?
It is necessary for Rockstar Games Launcher.

wine-mirror/wine@abb1ce1

https://bugs.winehq.org/show_bug.cgi?id=47843

I am on Xubuntu 20.04
I am using your builds for the 2 past years.
This is the first time when I ran winecfg that I met wine errors.
I did it to initiate an empty WINEPREFIX
My Xubuntu is almost up-to-date
I did the same test with the build from Wine-Tkg from https://github.com/Frogging-Family/wine-tkg-git/releases
Got the same errors while running to winecfg
Downgraded to your build to wine-tkg-staging 5.14...winecfg ran successfully while initating an empty WINEPREFIX
From my perspective, either there is something wrong with my OS or there is a real error with 5.15.
Regards

Did any of proton patches that you add manually to improved-wine builds has been added to the latest wine 5.0?

I am asking this question, because the announcement of the latest wine introduced new features that include enhancements for input devices, and fullscreen applications.

I am so thrilled about your builds, because it can be used with Playonlinux. Could you please join this discussion >>> PhoenicisOrg/phoenicis-winebuild#73

I want to use your builds instead of Wine-staging that is installed on Ubuntu. I mean installing not just using any of them.

I encountered 2 issues with the latest Wine-tkg that do not exist with latest Wine-staging, or Wine-tkg 5.20.

1- I encountered an issue with Detroit Become Human, and Cloudpunk, these games do not see the save games, and want to start a new one (the save game exists inside the wineprefix).

2- I encountered another issue with many games, these games are run with WineD3D instead of DXVK (DXVK is installed inside the wineprefix).

I get this error when I use the latest improved wine-staging build (5.6) when running Moon Of Madness:
wine client error:77: read: Bad file descriptor

• I don't encounter this issue when using wine-staging installed on my machine.
• I don't get this error when running other games using improved wine-staging build, only with this game.

Hi there,
this is not really your bug, but I thought it might be a good idea to mention it here, as you might be interested as well
and for sure would find the reason much faster than me. Sorry, if opening this issue is unappropriated!

I stumbled over a possible wine bug (no idea if it is already known somewhere) where any wine version/variant
above wine-6.17.$COMMITX doesn't detect valid directories as directories (at least in Vortex Mod Manager).
I tried to sum up the problem on my steamtinkerlaunch issue ticket here

If interested, any help/pointer would be great. If there's anything I can do to help, please let me know!

Just added this:
EDIT: Wait what!

- wine-6.17.r0.g5f19a815 ( TkG Staging Esync Fsync ) from wine-6.17-staging-tkg-amd64 by @Kron4ek works but the same version from proton above doesn't? Let me retest!

Sorry for the noise...

when I I try to run "sudo ./create_ubuntu_chroots.sh" I am guessing I run this first I get this output can you help.

mount: /opt/chroots/bionic32_chroot/sys: mount point does not exist.
mount: /opt/chroots/bionic32_chroot/dev: mount point does not exist.
mount: /opt/chroots/bionic32_chroot/dev/pts: mount point does not exist.
mount: /opt/chroots/bionic32_chroot/dev/shm: mount point does not exist.
mount: /opt/chroots/bionic32_chroot/dev: mount point does not exist.
cp: cannot create regular file '/opt/chroots/bionic32_chroot/etc/resolv.conf': No such file or directory
Chrooting into /opt/chroots/bionic32_chroot
chroot: cannot change root directory to '/opt/chroots/bionic32_chroot': No such file or directory
Unmount chroot directories
umount: /opt/chroots/bionic32_chroot: no mount point specified.
umount: /opt/chroots/bionic32_chroot/proc: no mount point specified.
umount: /opt/chroots/bionic32_chroot/sys: no mount point specified.
umount: /opt/chroots/bionic32_chroot/dev/pts: no mount point specified.
umount: /opt/chroots/bionic32_chroot/dev/shm: no mount point specified.
umount: /opt/chroots/bionic32_chroot/dev: no mount point specified.
Unmount chroot directories. Just in case.
umount: /opt/chroots/bionic64_chroot: not found
Mount directories for chroot
mount: /opt/chroots/bionic64_chroot: mount point does not exist.
mount: /opt/chroots/bionic64_chroot/proc: mount point does not exist.
mount: /opt/chroots/bionic64_chroot/sys: mount point does not exist.
mount: /opt/chroots/bionic64_chroot/sys: mount point does not exist.
mount: /opt/chroots/bionic64_chroot/dev: mount point does not exist.
mount: /opt/chroots/bionic64_chroot/dev/pts: mount point does not exist.
mount: /opt/chroots/bionic64_chroot/dev/shm: mount point does not exist.
mount: /opt/chroots/bionic64_chroot/dev: mount point does not exist.
cp: cannot create regular file '/opt/chroots/bionic64_chroot/etc/resolv.conf': No such file or directory
Chrooting into /opt/chroots/bionic64_chroot
chroot: cannot change root directory to '/opt/chroots/bionic64_chroot': No such file or directory
Unmount chroot directories
umount: /opt/chroots/bionic64_chroot: no mount point specified.
umount: /opt/chroots/bionic64_chroot/proc: no mount point specified.
umount: /opt/chroots/bionic64_chroot/sys: no mount point specified.
umount: /opt/chroots/bionic64_chroot/dev/pts: no mount point specified.
umount: /opt/chroots/bionic64_chroot/dev/shm: no mount point specified.
umount: /opt/chroots/bionic64_chroot/dev: no mount point specified.
rm: cannot remove '/opt/chroots/bionic64_chroot/opt/prepare_chroot.sh': No such file or directory
rm: cannot remove '/opt/chroots/bionic32_chroot/opt/prepare_chroot.sh': No such file or directory

Hello Kron4ek,
First of all thanks for your work.
Now I am building my own packages using your shell scripts.
There are available on my own website http://www.davidgis.fr/blog/index.php
Recently I discovered this backport for gcc-9.3.0 and mingw64 8.0.0
https://launchpad.net/~cybermax-dexter/+archive/ubuntu/mingw-w64-backport.

I took decision to give it a try and it seems to be really interesting instead of using the old gcc 8.4.0. - mingw 7.0.0
I built my wine builds on my own chroots + gcc 9.3.0 + mingw64 8.0.0. And it works like a charm on my two laptops based on Xubuntu 20.04

I am sharing my own notes just in case you are interested...

Inside chroots
Amd64

To fix libgcc-s1 issue before installing MinW64

wget http://mirrors.xmission.com/ubuntu/pool/main/g/gcc-10/libgcc-s1_10-20200411-0ubuntu1_amd64.deb
wget http://mirrors.edge.kernel.org/ubuntu/pool/main/g/gcc-10/gcc-10-base_10-20200411-0ubuntu1_amd64.deb
dpkg -i gcc-10-base_10-20200411-0ubuntu1_amd64.deb
dpkg -i libgcc-s1_10-20200411-0ubuntu1_amd64.deb

Then Install the PPA

apt-get install software-properties-common
add-apt-repository ppa:cybermax-dexter/mingw-w64-backport
apt-get update

After this line I didn't really remember what I did but maybe something lije below

apt-get install g++-mingw-w64-i686 g++-mingw-w64-x86-64 gcc-mingw-w64-base gcc-mingw-w64-i686 gcc-mingw-w64-x86-64

i686

To fix libgcc-s1 issue before installing MinW64

wget http://mirrors.xmission.com/ubuntu/pool/main/g/gcc-10/libgcc-s1_10-20200411-0ubuntu1_i386.deb
wget http://mirrors.edge.kernel.org/ubuntu/pool/main/g/gcc-10/gcc-10-base_10-20200411-0ubuntu1_i386.deb
dpkg -i gcc-10-base_10-20200411-0ubuntu1_i386.deb
dpkg -i libgcc-s1_10-20200411-0ubuntu1_i386.deb

Then install this PPA

apt-get install software-properties-common
add-apt-repository ppa:cybermax-dexter/mingw-w64-backport

I didn't remember what I did...maybe a 'apt-get update + apt-get upgrade'

To Install GCC-9.3.0

You can refer to this link
https://www.ultralinux.org/post/how-to-install-gcc-compiler-on-ubuntu-18-04/

I tried your latest wine-improved build, and it gives me this error:
FATAL ERROR: Please update your driver: VK_EXT_full_screen_exclusive is required.

and I tried the latest proton build, and it gives me this error:
FATAL ERROR: Please update your driver: VK_KHR_get_surface_capabilities2 is required.

I tried switching from Kisak PPA to Obiaf PPA, I tried also switching from RADV to AMDVLK, and amdgpu-pro, but it makes no difference.

I tried updating vulkan-loader to the latest version from Vulkan SDK PPA using these commands:

wget -qO - http://packages.lunarg.com/lunarg-signing-key-pub.asc | sudo apt-key add -
sudo wget -qO /etc/apt/sources.list.d/lunarg-vulkan-bionic.list http://packages.lunarg.com/vulkan/lunarg-vulkan-bionic.list
sudo apt update
sudo apt dist-upgrade

but vulkan-loader got updated to version 1.2.131.2

I tried to build vulkan-headers, and vulkan-loader myself, but I always get multiple compilation errors when trying to build it.

I tried sed commands that you mentioned in this comment ValveSoftware/Proton#3654 (comment)

and I was able to reach the main menu, and start a new game, but the game freezes while loading, and it spams errors about RAW inputs, I don't remember the whole error line.

I had the same loading issue with Doom 2016, and I fixed back then by switching from Vulkan to OpenGL, but I was able to run Life is Strange 2 (native), and Wolfenstein II: The New Colossus on the same machine.

I don't think that this issues is related to your wine builds, I am just hoping that you can help me with this issue.

System specification:

CPU: Intel Core I5 4200M
GPU: AMD HD Radeon 8750M
OS: Kubuntu 19.10
Kernel: 5.4.28-xanmod1

Right now the compiled binaries require libjpeg8 in order to run, without that being installed you get messages like:

00fc:err:wincodecs:jpeg_decoder_create Failed reading JPEG because unable to find libjpeg.so.8

However, libjpeg8 isn't available any more on many distros (neither Fedora nor recent Debian versions have it). Would it be possible for the binaries to be built using libjpeg 6.2 instead? libjpeg-turbo62 seems to have much wider availability...

wine-6.0-rc2-staging-tkg-amd64.tar.xz could launch the game but frequent freezing this newer version (rc3) has no picture so cannot launch.

FYI

commit cab4dbb3c982861cc5623c1833bfb590462592f1 (HEAD -> master, origin/master, origin/HEAD)
Author: Tk-Glitch [email protected]
Date: Mon Oct 25 18:20:39 2021 +0200

Proton-tkg: makepkg: WARNINGS

commit 70f854f86de2393a3ff2cadea3160fecb09786c4
Author: Tk-Glitch [email protected]
Date: Mon Oct 25 18:13:22 2021 +0200

Allow restoring staging's mfplat support patchset along with adequate reverts.

Thanks to GE for helping out

Title

First, thanks for including AMD FSR in your Wine builds.

I have 2 questions about AMD FSR if you do not mind:

1- You said in release note that is WINE_FULLSCREEN_FSR_STRENGTH controls sharpening, 0 is the maximum, and 5 is the minimum. Is it a typo, or is it right this way?

2- How can I control resolution?

How do we contact your group?
What is your official mail?