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.9.0||0.9.0-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 short.
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 in a game folder and run GemRB. MacOS is the only exception with its bundle. On Windows make sure you have the Visual Studio 2017 Redistributable (32-bit), 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.
Consider changing settings only after running GemRB for the first time. In this case you can skip this whole section.
GemRB uses a settings file primarily to know where to look for the game data when not running from within a game folder or when the path is not passed to it. The other reason you might want to edit it is to change other settings like resolution, input tweaks or debugging toggles.
Edit the shipped
GemRB.cfg: the only thing that always needs to be changed (unless you installed
GemRB in a game folder) is the path to the game’s data files (
GamePath). It is crucial you get
this right to be able to use the configuration.
If you are curious, read the detailed explanation of all the configuration options. The configuration filename is arbitrary, but check the note in the Options section.
You can create a config file with only the keys that you want to change. For example, you can set just the
Height resolution options if the game and engine data is found some other way (eg. in Linux AppImage packages).
Run it as any other program. :)
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.
gemrb binary, optionally specifying the desired configuration:
gemrb.exe -c torment.cfg
or game path:
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.
How to run the GemRB demo?
The quickest way, without any configuration, is to just run GemRB without any parameters. It will run the demo if it can’t find any other game data. So make sure you haven’t unpacked it in a game dir and voilà!