Posted December 07, 2018
high rated
I've put together a Wine wrapper for Rites of War, allowing it to be played on Linux almost like a native game & with no Wine knowledge required.
Simply run the build script to create the wrapper. If the 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. The start script also includes options for creating a shortcut, configuring the wrapper etc.
(to uninstall simply delete the game directory and any shortcuts you created, and the game's user data directory in ~/.local/share if you don't want to keep your saves & settings)
User data is stored under ~/.local/share/wh40k_rites_of_war
Full details are in the readme.txt and release notes. Here is the download link:
wh40k_rites_of_war_wine.tar.xz
(37.4 kB, SHA256: 80fc3bc23e423c089d0dec8b7ddb2f978214104bae349140eccc45552ce5ae57)
Last updated 2021/07/11
The wrapper uses Proton 5.0-9. Wine and Winetricks will be downloaded automatically if not present; to avoid redownloading for other scripts the downloaded Wine package will be stored in ~/.cache/winewrap
This wrapper also uses dgVoodoo2 and will use Vulkan by default, however you can set it to use OpenGL instead by setting PROTON_USE_WINED3D=1 when running the start script (although doing this may result in graphical glitches).
The only issues I've encountered so far are very minor and can be ignored: the game complains about the desktop's bit depth on startup and certain text has a purple outline (but it is still legible). However if anyone encounters any other problems then post in this thread, Adamhm's Linux Wine Wrappers - News, FAQ & Discussion and/or The "Judas™ does this run in Wine" thread v1.173.
For more of my Linux Wine wrappers check out post 3 in this thread: Adamhm's Linux Wine Wrappers - News, FAQ & Discussion
Simply run the build script to create the wrapper. If the 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. The start script also includes options for creating a shortcut, configuring the wrapper etc.
(to uninstall simply delete the game directory and any shortcuts you created, and the game's user data directory in ~/.local/share if you don't want to keep your saves & settings)
User data is stored under ~/.local/share/wh40k_rites_of_war
Full details are in the readme.txt and release notes. Here is the download link:
wh40k_rites_of_war_wine.tar.xz
(37.4 kB, SHA256: 80fc3bc23e423c089d0dec8b7ddb2f978214104bae349140eccc45552ce5ae57)
Last updated 2021/07/11
The wrapper uses Proton 5.0-9. Wine and Winetricks will be downloaded automatically if not present; to avoid redownloading for other scripts the downloaded Wine package will be stored in ~/.cache/winewrap
This wrapper also uses dgVoodoo2 and will use Vulkan by default, however you can set it to use OpenGL instead by setting PROTON_USE_WINED3D=1 when running the start script (although doing this may result in graphical glitches).
The only issues I've encountered so far are very minor and can be ignored: the game complains about the desktop's bit depth on startup and certain text has a purple outline (but it is still legible). However if anyone encounters any other problems then post in this thread, Adamhm's Linux Wine Wrappers - News, FAQ & Discussion and/or The "Judas™ does this run in Wine" thread v1.173.
For more of my Linux Wine wrappers check out post 3 in this thread: Adamhm's Linux Wine Wrappers - News, FAQ & Discussion
Post edited July 11, 2021 by adamhm