It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
shmerl: (…)
Check this bug report, it includes a workaround for the GOG build: Vampire.exe process keeps lingering.

Beware that loader.exe won’t hold your terminal until you quit the game, it returns immediately after starting the vampire.exe process. If this is something that could cause problems for you, ./play.it uses the following workaround:
# Keep hold of the terminal until the game process actually ends,
# instead of returning as soon as the game is started
sleep 10s
pidwait --euid "$USER" --ignore-case vampire.exe
(this is called right after the WINE command in the game launcher script)
avatar
vv221: Check this bug report, it includes a workaround for the GOG build: Vampire.exe process keeps lingering.
Interesting, thanks.

I noticed that if I run the game from the terminal myself, not from a .desktop launcher I made for it, this bug doesn't happen. I guess the issue is somehow related to what the terminal provides since it's similar to your workaround.
Post edited June 15, 2025 by shmerl
If anyone uses Cheat Engine with unity/mono games this commit dda9f35c8d82bdd2e78315f5f4c044ecc6d03bc3
causes that to fail. You can tell by attaching cheat engine to a suitable game mono will appear in the menu bar click on activate mono features after some time with wine 10.16 you will get a dialog saying failure to launch and the lua engine dialog will print Library Injection failed or invalid module. No idea if it affects all cheat engine injection of just mono was just what I noticed.

You can revert it (git revert -n dda9f35c8d82bdd2e78315f5f4c044ecc6d03bc3) and everything seems fine again no idea if that will cause issues with debugging or the like. Its in 10.16 git describes the commit as wine-10.15-322-gdda9f35c8d8 part of this merge request https://gitlab.winehq.org/wine/wine/merge_requests/9078

edit - Has been fixed
Post edited November 03, 2025 by Cusith
avatar
Cusith: You can revert it (git revert -n dda9f35c8d82bdd2e78315f5f4c044ecc6d03bc3) and everything seems fine again no idea if that will cause issues with debugging or the like. Its in 10.16 git describes the commit as wine-10.15-322-gdda9f35c8d8 part of this merge request https://gitlab.winehq.org/wine/wine/merge_requests/9078
If it causes an actual regression, you should report a bug.