Posted September 01, 2017
high rated
This thread is for news, FAQ and discussion pertaining to my Wine wrappers. Feel free to post here if you need help with any of them or have any questions.
Latest update (2020/03/28): Wrappers are now available for The Bard's Tale Trilogy, Batman: Arkham Asylum, Batman: Arkham City, and Wasteland Remastered. Thanks to sunshinecorp for donating the key for Wasteland Remastered :)
For a full list of release threads and an archive containing all wrappers, see this post.
Don't use Linux? Check out my Linux Mint beginner's guide/page1 if you're interested & consider trying it :)
***** About this project *****
The goal of this project is to provide an easy way for getting the supported games running on Linux using Wine, without any Wine knowledge being required and offering an experience as close as possible to playing a native game.
Saves are stored in their own subdirectory under $XDG_DATA_HOME or ~/.local/share (or optionally in the game directory) rather than being scattered around the Wine prefix or somewhere in your Documents directory or so. They can be set up to use other paths by setting an environment variable named WINEWRAP_UDATA_ROOT with the desired location.
Fixes for common issues are included where possible. Where there are hardware-specific issues and the solutions may cause issues with other hardware, I try to have the wrappers detect if the affected hardware is currently in use and automatically apply or revert the fixes as necessary (this behavior can be overridden by the user).
The wrappers are also designed to offer a high degree of customisability and user choice/control to facilitate things like using mods and third party tools/utilities, however in general no mods will be included by default. I do make exceptions for things like widescreen & performance/stability fixes though.
***** How it works *****
You simply run the build script to create the wrapper. If the game's installer files are not alongside the wrapper build files then the path to them will need to be specified either by passing it as an argument to the build script with -respath="<path>" or by setting an environment variable named WINEWRAP_RESPATH containing it. You can change the path to build the wrapper in and the name of the wrapper directory with the -buildpath= and -dirname= arguments. The build path can also be set with the WINEWRAP_BUILDPATH environment variable.
The output will be a directory containing the game set up within a preconfigured Wine prefix, along with its own copy of Wine, extracted game icons, documentation, and start script(s). From there simply run the start script to play.
Running the start script with no arguments will have it present a menu with various options. From here you can run the game, create a shortcut, access the advanced options menu etc. - this will vary slightly from game to game.
Creating a directory named "userdata" in the game directory will result in settings/saves/etc being kept there instead of your home directory.
There are some dependencies common to all of the wrappers: Wine's dependencies, icoutils, and innoextract - others may also be necessary depending on the game. Innoextract will be downloaded if your system's version is outdated or not installed.
For more automated use by other scripts etc., the wrapper build scripts return different exit codes on failure. The exit codes are:
01: Script was not run with Bash or was attempted to be used on a Windows filesystem
02: Wrapper directory already exists
03: Unrecognised argument specified
04: Wine version not specified
05: Missing one or more dependencies
06: Missing wrapper resource and/or installer file(s)
07: Failed to download Wine package
08: Checksum failed for Wine package
09: Failed to download Winetricks
10: Failed to download an additional resource file
11: Checksum failed for an additional resource file
12: Checksum failed for wrapper resource and/or installer files
13: Failed to unpack Wine
14: Failed to create Wine prefix
15: Failed to unpack installer
16: Failed to unpack resource archive
17: Failed to create tarball
***** FAQ *****
Do these wrappers require PlayOnLinux or Lutris?
No. These wrappers download & use the Wine packages provided by PlayOnLinux (website: https://www.playonlinux.com) and Lutris ( https://lutris.net), but PlayOnLinux and Lutris are not required. I recommend checking out PlayOnLinux and Lutris if you want to try getting things running in Wine yourself though. I also wrote a PlayOnLinux guide along with my Linux Mint guide.
The build script for <game> appears to expect an outdated installer
I try to keep the wrappers updated to use the newest installers, but GOG don't always post changelogs or update notices so it's possible that I might miss them occasionally. First check that you have the latest classic installer and not the Galaxy installer; some games have two sets of installers, with the Galaxy installer being presented by default, and it's very easy to miss the Galaxy-free "classic" installer if you're not aware of this. To show the classic installers, click on the "More" button on the download page to bring up the menu and select the classic installers option. Only classic Galaxy-free installers are supported by my wrappers.
If you've checked this and have found a case where one of my scripts is expecting an outdated installer then post here or in the relevant release thread to let me know and I'll fix it as soon as I can.
It isn't working & there are messages like: "Wine cannot find the ncurses library (libncurses.so.5)"
Check that you have installed all of Wine's dependencies. Note that most of the wrappers are 32-bit, so 32-bit dependencies will be required. On Linux Mint just installing the wine package should install both the 64 and 32 bit versions.
Users of Mint 19.x or Ubuntu 18.04 (or other Ubuntu 18.04-based distros) can try my common dependencies meta-package, which should install the required dependencies as well as dependencies that are commonly required for many other games.
It runs but there are graphics issues
Make sure that you're using recent graphics drivers. For users of Ubuntu, Mint and other Ubuntu-based distros, you can use these PPAs to update your graphics drivers:
Kisak's Stable Mesa PPA (for users of the open graphics drivers)
Proprietary GPU Drivers PPA (proprietary drivers for Nvidia users)
Regarding multiplayer... ?
I generally don't test multiplayer (it's just me working on these) so it may or may not work. If not, then you could try using Winetricks to install native Windows versions of certain components that may be required. If you find that something requires additional components for multiplayer to work then let me know & I'll see about updating the wrapper to include them by default.
Do you take requests?
Yes, but I can't guarantee that I'll be able to get something running acceptably, or at all. It also depends on me actually having the game in question: In order to support and encourage official Linux releases I will usually wait for non-Linux games to become sufficiently discounted/cheap enough before I consider buying them for use with Wine (and they *must* be DRM-free), and I recommend that others do likewise. Save your full/high price purchases for games that officially support Linux :)
If you're particularly keen on playing a particular game you could try getting it running yourself using the GOGWrap generic wrapper (see towards the end of this post), or something like PlayOnLinux.
Latest update (2020/03/28): Wrappers are now available for The Bard's Tale Trilogy, Batman: Arkham Asylum, Batman: Arkham City, and Wasteland Remastered. Thanks to sunshinecorp for donating the key for Wasteland Remastered :)
For a full list of release threads and an archive containing all wrappers, see this post.
Don't use Linux? Check out my Linux Mint beginner's guide/page1 if you're interested & consider trying it :)
***** About this project *****
The goal of this project is to provide an easy way for getting the supported games running on Linux using Wine, without any Wine knowledge being required and offering an experience as close as possible to playing a native game.
Saves are stored in their own subdirectory under $XDG_DATA_HOME or ~/.local/share (or optionally in the game directory) rather than being scattered around the Wine prefix or somewhere in your Documents directory or so. They can be set up to use other paths by setting an environment variable named WINEWRAP_UDATA_ROOT with the desired location.
Fixes for common issues are included where possible. Where there are hardware-specific issues and the solutions may cause issues with other hardware, I try to have the wrappers detect if the affected hardware is currently in use and automatically apply or revert the fixes as necessary (this behavior can be overridden by the user).
The wrappers are also designed to offer a high degree of customisability and user choice/control to facilitate things like using mods and third party tools/utilities, however in general no mods will be included by default. I do make exceptions for things like widescreen & performance/stability fixes though.
***** How it works *****
You simply run the build script to create the wrapper. If the game's installer files are not alongside the wrapper build files then the path to them will need to be specified either by passing it as an argument to the build script with -respath="<path>" or by setting an environment variable named WINEWRAP_RESPATH containing it. You can change the path to build the wrapper in and the name of the wrapper directory with the -buildpath= and -dirname= arguments. The build path can also be set with the WINEWRAP_BUILDPATH environment variable.
The output will be a directory containing the game set up within a preconfigured Wine prefix, along with its own copy of Wine, extracted game icons, documentation, and start script(s). From there simply run the start script to play.
Running the start script with no arguments will have it present a menu with various options. From here you can run the game, create a shortcut, access the advanced options menu etc. - this will vary slightly from game to game.
Creating a directory named "userdata" in the game directory will result in settings/saves/etc being kept there instead of your home directory.
There are some dependencies common to all of the wrappers: Wine's dependencies, icoutils, and innoextract - others may also be necessary depending on the game. Innoextract will be downloaded if your system's version is outdated or not installed.
For more automated use by other scripts etc., the wrapper build scripts return different exit codes on failure. The exit codes are:
01: Script was not run with Bash or was attempted to be used on a Windows filesystem
02: Wrapper directory already exists
03: Unrecognised argument specified
04: Wine version not specified
05: Missing one or more dependencies
06: Missing wrapper resource and/or installer file(s)
07: Failed to download Wine package
08: Checksum failed for Wine package
09: Failed to download Winetricks
10: Failed to download an additional resource file
11: Checksum failed for an additional resource file
12: Checksum failed for wrapper resource and/or installer files
13: Failed to unpack Wine
14: Failed to create Wine prefix
15: Failed to unpack installer
16: Failed to unpack resource archive
17: Failed to create tarball
***** FAQ *****
Do these wrappers require PlayOnLinux or Lutris?
No. These wrappers download & use the Wine packages provided by PlayOnLinux (website: https://www.playonlinux.com) and Lutris ( https://lutris.net), but PlayOnLinux and Lutris are not required. I recommend checking out PlayOnLinux and Lutris if you want to try getting things running in Wine yourself though. I also wrote a PlayOnLinux guide along with my Linux Mint guide.
The build script for <game> appears to expect an outdated installer
I try to keep the wrappers updated to use the newest installers, but GOG don't always post changelogs or update notices so it's possible that I might miss them occasionally. First check that you have the latest classic installer and not the Galaxy installer; some games have two sets of installers, with the Galaxy installer being presented by default, and it's very easy to miss the Galaxy-free "classic" installer if you're not aware of this. To show the classic installers, click on the "More" button on the download page to bring up the menu and select the classic installers option. Only classic Galaxy-free installers are supported by my wrappers.
If you've checked this and have found a case where one of my scripts is expecting an outdated installer then post here or in the relevant release thread to let me know and I'll fix it as soon as I can.
It isn't working & there are messages like: "Wine cannot find the ncurses library (libncurses.so.5)"
Check that you have installed all of Wine's dependencies. Note that most of the wrappers are 32-bit, so 32-bit dependencies will be required. On Linux Mint just installing the wine package should install both the 64 and 32 bit versions.
Users of Mint 19.x or Ubuntu 18.04 (or other Ubuntu 18.04-based distros) can try my common dependencies meta-package, which should install the required dependencies as well as dependencies that are commonly required for many other games.
It runs but there are graphics issues
Make sure that you're using recent graphics drivers. For users of Ubuntu, Mint and other Ubuntu-based distros, you can use these PPAs to update your graphics drivers:
Kisak's Stable Mesa PPA (for users of the open graphics drivers)
Proprietary GPU Drivers PPA (proprietary drivers for Nvidia users)
Regarding multiplayer... ?
I generally don't test multiplayer (it's just me working on these) so it may or may not work. If not, then you could try using Winetricks to install native Windows versions of certain components that may be required. If you find that something requires additional components for multiplayer to work then let me know & I'll see about updating the wrapper to include them by default.
Do you take requests?
Yes, but I can't guarantee that I'll be able to get something running acceptably, or at all. It also depends on me actually having the game in question: In order to support and encourage official Linux releases I will usually wait for non-Linux games to become sufficiently discounted/cheap enough before I consider buying them for use with Wine (and they *must* be DRM-free), and I recommend that others do likewise. Save your full/high price purchases for games that officially support Linux :)
If you're particularly keen on playing a particular game you could try getting it running yourself using the GOGWrap generic wrapper (see towards the end of this post), or something like PlayOnLinux.
Post edited March 28, 2021 by adamhm
