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: (this is called right after the WINE command in the game launcher script)

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.

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

If it causes an actual regression, you should report a bug.

I made a thread in a game specific forum, but I figured I might as well crosspost it here since game specific forums are all but dead. https://www.gog.com/forum/solasta_crown_of_the_magister/solasta_in_linux_with_wine (I was going to just make a new thread in general about it, but I figured I would do a quick search for wine and this came up and seemed active not too long ago. Not sure if this is the best place for this, but oh well, here I am.)

I will quote the whole post here to save people a click:
"Does anyone know anything about this: https://appdb.winehq.org/objectManager.php?sClass=version&iId=40218 ? It is an older posting but the alt-tab problem still exists even with the latest version of Wine. The listed workarounds didn't work for me (or I just didn't understand them correctly). Not a major problem because the game is still fully playable, but it is a pretty major annoyance. Would love to find a way to fix it.

And anyone who comes to this thread to say anything like "Just use Lutris (or whatever other launcher)" can consider themselves smacked with a rolled up newspaper and go away. If I wanted to use some stupid launcher I wouldn't be asking this question, now would I?"

Try running Wine in native Wayland mode, it can help with a lot of Alt-Tabbing problems that plague winex11.

It can be enabled by simply setting DISPLAY= (i.e. setting DISPLAY variable to empty) or unsetting it altogether, i.e.

unset DISPLAY

when you run the game.

Obviously, you need to be in the Wayland session of your desktop environment for that (I assume you are, unless you are using something uncommon).

I've been using winewayland for quite a while and it's really good.

Does it handle games which expect to set the screen resolution in a reasonable manner? (I'm particularly concerned about games that don't support "modern" resolutions.)

In general it does, but there is one outstanding issue with KDE Plasma in particular, which I hope they (KDE / KWin developers) should fix this year.

See here:

* https://bugs.kde.org/show_bug.cgi?id=461063
* https://bugs.winehq.org/show_bug.cgi?id=57456

Thanks, but someone already gave me a working solution in my other thread. I will keep this in mind though should I run into similar problems in the future.