It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Whenever I look at the available downloads for this game I see what makes perfect sense: a download for the game (Windows installer) and two patches ('patch 1.0.57+ to 1.0.74' and 'patch 1.0.74 to 1.0.81+).

When these are downloading I can see these same names appear in the GOG downloader. The problem shows up when I navigate to the actual file that has been downloaded... there are no files with those name in that directory. Instead I see all of my previous downloads for this game (prior installers, prior patch files, etc.) along with the two files I just downloaded, and I have no way to tie the name of the patch to the name of the file.

Somewhere on the download page there should be details connecting the given descriptive name with the actual file name. This is especially important considering the file name contains a version string which seemingly has no relation to the game version it is applying or changing.
If you turn off the downloader and hit the web link for a patch you can get the associated file name, and then cancel the download.
Including the game version in the file name (or at least the install screen when running the patch) would be nice, though.
Post edited July 29, 2014 by Raze_Larian
@vuldin
I also have a major problem with version numbers not having the same name as the patches. It's annoying, stupid, and there is no valid reason in the public eye, for them to be named two completely different things. There are also just way too many patches for this game (The list below isn't even complete). On top of that, it doesn't even say anyrhing such as (This will update (Insert name) from (Insert Number) - (Insert Number) when installing them.

I had to do a little digging to locate the following information, but it got ridiculous even for me. I couldn't find what the name of the patch itself was on some of them. Sorry I did the best I could

So this should help you: out somewhat
Anything that has the word ENGINE in it, is the tool kit.

1.0.53 - 1.0.57 - Unsure
patch_divinity_original_sin_2.3.0.7.exe is actually patch version 1.0.57
is actually patch version 1.0.57 - 1.0.63 - Unsure
is actually patch version 1.0.63 - 1.0.67 - Unsure
patch_divinity_original_sin_2.4.0.10.exe is actually patch version 1.0.57 - 1.0.67
1.0.63 - 1.0.74 - Unsure
patch_divinity_original_sin_2.5.0.11.exe is actually patch version 1.0.57 - 1.0.74
patch_divinity_original_sin_2.6.0.13.exe is actually patch version 1.0.74 - 1.0.81
patch_divinity_original_sin_2.6.0.13.exe is actually patch version - 1.0.81
Post edited July 30, 2014 by tx3000
@tx3000
Thanks for the details, and I'm glad to see others see the same issue and would like to see a solution. Luckily the solution to this bug is simple: include file names on the download page. Bonus points would be to make these versions match between what GOG calls the download and what is included in the file name.

I ended up going by modified date in order to find the file I had just downloaded, then I compared the file sizes to what was on the download page and was able to piece together which ones were which. Either route we have to take given the current situation is still a pain.
avatar
Raze_Larian: If you turn off the downloader and hit the web link for a patch you can get the associated file name, and then cancel the download.
At the risk of stating the obvious, this procedure is clumsy, time consuming, and error prone. GOG, hear my plea: Give us file names with version numbers, and modification dates, and checksum of some kind. Having an authoritative SHA1, MD5, or even CRC32 for each file would save lots of effort for manual downloaders, and probably spare some of the wear on your servers.

Love ya! Thanks :)
avatar
Raze_Larian: If you turn off the downloader and hit the web link for a patch you can get the associated file name, and then cancel the download.
avatar
posipil: At the risk of stating the obvious, this procedure is clumsy, time consuming, and error prone. GOG, hear my plea: Give us file names with version numbers, and modification dates, and checksum of some kind. Having an authoritative SHA1, MD5, or even CRC32 for each file would save lots of effort for manual downloaders, and probably spare some of the wear on your servers.

Love ya! Thanks :)
everyone should vote here for it: http://www.gog.com/wishlist/site/add_version_number_to_gog_releases_eg_earth_2140_release_12
I had already voted for it, but took the opportunity to add a nice, lengthy comment. :)
This has frustrated me lately. With the most recent patch (1.0.74+ to 1.0.107) not working for me, I can't tell from the filenames whether I missed a patch or if the new patch just plain doesn't work.

It's also not helpful that GOG remove access to old patches and just update the base installer periodically (I understand that this is convenient for new purchasers of the game, but I'd rather not be forced to re-download an 8GB+ file to get to the latest version in the event that I didn't download a patch fast enough before they removed it).
Indeed patch process is to be improved.

Imarion
The patches seldom work unfortunately. They usually get to the end and then report an error and I need to dl the entire archive again.
Downloading a new version of a games installer every so often is absolutely unacceptable.
I am sure I am not alone when I say that random downloads of 8Gig+ to keep a game updated will simply cripple my internet usage allowance.
If this will be GOG's policy then they say goodbye to any more of my money.