-
Notifications
You must be signed in to change notification settings - Fork 25
GOG Galaxy
Q: How do I get GOG Galaxy/GOG Galaxy 2.0, OSOL, and Steam to play nicely with each other?
A: During the normal instructions for setting up OSOL, check the following:
- Make sure you're using the full path to
GalaxyClient.exe
as yourLauncherPath
- Grab the GOG
gameId
from the first line ofgoglog.ini
(digits only, e.g.:1495134320
from[1495134320_dircopy]
) in the root directory of your installed GOG game - Use the
gameId
you copied to change yourLauncherArgs
to look something like this example:LauncherArgs=/command=runGame /gameId=1495134320 /path=D:\Games\GOG Games\The Witcher 3 Wild Hunt GOTY\bin\x64\witcher3.exe
- Set your
AutoGameLaunch=False
in the OSOL .ini file (found in the directory you ran OSOL from)
Q: GOG Galaxy doesn't cloud sync my game saves when I'm launching from OSOL. What gives?
A: This is an intentional feature in GOG Galaxy; if an executable is running inside the game directory it will not cloud sync. The solution is to not put the OSOL executable inside the directory of the Game when launching GOG Galaxy through OSOL.
Q: I'm trying to run The Witcher: Enhanced Edition Director's Cut and I can't seem to run the game without the Witcher launcher. Help!
A: Look for the real game executable under <your path to The Witcher>\system\witcher.exe
instead of using the launcher .exe in the root game directory.
These instructions are up to date as of version v1.09h on 12/20/2021.