The latest sources and official builds are always available on our SourceForge project page. Here is a handy table with shortcuts:
|Release downloads||Development downloads|
|Source||Tarball||See dev docs|
|Version||0.8.6||0.8.6-git with build number|
The Android and iOS builds are currently unmaintained.
Getting the games
You will need one of the original Infinity Engine games or the free BG II demo. If you’re not using Windows, here are some ideas on how to complete the install. GemRB comes with its own demo, but it is trivial.
Due to low interest, GemRB does not support the EE versions of the games, though there has always been considerable feature overlap.
After you have the games, you can also install any mods. They should work out of the box, but any that modify the EXE files could lack the functionality those hacks achieved. Installing the fixpacks is highly recommended.
The downloads do not come with installers, so just unpack them and run GemRB. MacOS is the only exception with its bundle. On Windows make sure you have the Visual Studio 2013 Redistributable (2017 for development builds), as GemRB will fail to start without two of its DLLs.
If you downloaded the sources instead, follow the compilation instructions. GemRB can even run from the build dir without installing.
GemRB uses a settings file primarily to know where to look for the game data.
GemRB.cfg.sampleto a new file named
GemRB.cfgin the same folder.
- The only thing that always needs to be changed is the path to
the game’s data files (
GamePath, very seldomly
CDx). It is crucial you get this right.
- If you’re running from a binary package, set
- The only thing that always needs to be changed is the path to the game’s data files (
If you are curious, read the detailed explanation of all the configuration options. The configuration filename is arbitrary, but check the note in the last section.
Setting the paths can be tricky, so carefully read any errors that gemrb prints to the output or GemRB.log file before exiting. See this old video for a walkthrough on how to fix the encountered problems and set up the paths properly.
The default config file
GemRB.cfg.sample is preconfigured as if you unpacked the archive into
If you haven’t, edit it with a text editor, change
.\plugins and remove the hash
# in front of it.
You will know GemRB is set up correctly once you can see the main game
screen. If that doesn’t happen, check the end of the log for errors and fix the
configuration file as needed. Usually the game path is set wrong, but also IWD2
doesn’t work at the preset resolution (change to
gemrb binary, specifying the desired configuration:
gemrb.exe -c torment.cfg.
If you named the configuration file
GemRB.cfg and put it in the same folder as the binary,
that file will be used automatically and you don’t need to specify anything — you can just
click on the program.
If you’re using a touch screen, read this page for the gesture information.