FitGirl repacks are often the smallest, but her installers are awful: so fragile that they often fail in Wine with error messages that don't make sense. (For example, "not enough memory" on systems with ample RAM.)
Exporting these environment variables before running the installer sometimes avoids the failures:
WINEDLLOVERRIDES=isdone,unarc=n,b
WINE_LARGE_ADDRESS_AWARE=0
PROTON_FORCE_LARGE_ADDRESS_AWARE=0
Recent releases of GE-Proton may handle FitGirl installers better than Wine-GE-Proton, Kron4ek, or other more standard Wine builds. It can generally be used like normal Wine outside of Steam/UMU, although this will lose some Proton functionality like game-specific fixes. It's best to generate a new Wine prefix when switching a game from another Wine build to GE-Proton, since different support files will be generated and a different username ("steamuser") will be seen by Windows programs. The Wine executable in GE-Proton is files/bin/wine
instead of the bin/wine
that you might be used to.
I have read that these things might also help in some circumstances:
- In winecfg, try setting the Windows version to "Windows XP". Try other versions as well if that one doesn't help.
- Run the installer from within the Wine command prompt, which can be started by running
wine cmd
- Run the installer from within the Microsoft command prompt, which can be installed in a Wine prefix using Winetricks by running
winetricks cmd
- Untick any installer options for updating DirectX or Visual C++ redistributables. The former are replaced by DXVK and vkd3d-proton. The latter can be installed after the game install, if needed, using Winetricks.
- Tick the installer option to limit RAM use.