Press Play. It will run estella.exe with your system wine.
(Without the appropriate binfmt config, it will fail silently.)
Signs that it is running with system wine:
you might see the typical "updating /home/$USER/.wine" popup
files are created in ~/.wine/drive_c/users/$USER/AppData/Roaming/estella/ instead of Steam/steamapps/compatdata/$APPID/...
there are wine-related processes but no Proton processes
Obviously this is the dev/publisher error, but it also seems like it shouldn't be allowed to happen on the client side. Neither outcome (running with system wine or failing silently) is good.
Testing without the wine binfmt config
On mainstream distros[^1], there is probably a file installed at /usr/lib/binfmt.d/wine.conf (or a similar name), handled by systemd-binfmt.service. (see man binfmt.d and man systemd-binfmt)
The game that previously ran with system wine should now fail.
To re-enable, delete /etc/binfmt.d/wine.conf and restart the service.
[^1]: On Fedora, /usr/lib/binfmt.d/wine.conf is provided by wine-systemd, which is a hard dep (requires) of the full wine package (via wine-desktop). However you won't have it if you only install the minimal wine-core.
On Debian, `/usr/lib/binfmt.d/wine` is provided by `wine-binfmt`, which is a soft dep (suggests) of `wine`
On Arch, `/usr/lib/binfmt.d/wine.conf` is provided by `wine`.
If a Windows depot is wrongly marked for Linux, it may unexpectedly run using the system wine instead of Proton.
E.g. the Estella demo at the time of writing has only 1 depot containing only a Windows build, but it is marked for both Windows and Linux https://steamdb.info/depot/4195921/ (this has since been fixed)
Steps to repro
winepackage).(Without the appropriate binfmt config, it will fail silently.)
Signs that it is running with system wine:
~/.wine/drive_c/users/$USER/AppData/Roaming/estella/instead ofSteam/steamapps/compatdata/$APPID/...Obviously this is the dev/publisher error, but it also seems like it shouldn't be allowed to happen on the client side. Neither outcome (running with system wine or failing silently) is good.
Testing without the wine binfmt config
On mainstream distros[^1], there is probably a file installed at
/usr/lib/binfmt.d/wine.conf(or a similar name), handled bysystemd-binfmt.service. (seeman binfmt.dandman systemd-binfmt)To test disabling it:
The game that previously ran with system wine should now fail.
To re-enable, delete
/etc/binfmt.d/wine.confand restart the service.[^1]: On Fedora,
/usr/lib/binfmt.d/wine.confis provided bywine-systemd, which is a hard dep (requires) of the fullwinepackage (viawine-desktop). However you won't have it if you only install the minimalwine-core.