Haven't read all of the other linked threads, so if this is already mentioned, sorry.

What OS are you experiencing this bug on? It is entirely possible that this is not a bug that GOG introduced, but rather something unique to Vista or Win 7 brought it to light. What hardware is this running on? Again, it could be certain hardware, like processor type or graphics card model/drivers that are generating the error. There is definitely not enough info gathered here to say with any certainty that this has anything to do with GOG's release in particular.

Hey, no problem at all.

In my case it is Windows XP (running on over 5 years old PC ) so it is edition of Windows that should not generate any errors (=should be 100% compatible). Also game was originally released not so long time ago so there should not be needed any work to make it run on modern PCs but I can see some suspicious file goggame.dll in game directory which can suggest that KB's code was changed a little before release on GOG.

I do not know about overlapping numbers (case of "showflyingdead" bug) but in my eyes garrison / reserve bug has nothing common with hardware as it seems to be UI programming error.

Weird thing is that so far GOG version users are confirming its existence and also users of other versions have no such problems.

All I can suggest is to continue to have people test the same build number as the GoG version with a boxed edition, and then, a massive push to open support tickets if this is real. Otherwise, nothing will get done.

Usually, nothing will ever get done anyways because support dies down, and GoG will just release another broken game.

Well the thing is that other releases (Steam, boxed Polish edition) are so far working ok. So it is not problem of developer I think? But yes, we need more confirmations.

Also, I think it will be easy to find and compare 1.7 versions, but I think GOG's build number (35396) is pretty unique.. :(

Thank you very much for the report!

So for now we have:
GOG ver 1.7(35396) - garrison & reserve do not work properly
Steam ver 1.7(35234) - ok
GG ver 1.7(35234) - ok
Polish retail ver 1.6.5(???) - ok

GOG's internal build is different from Steam/GG - maybe this is causing some errors? But also it seems to be newer (bigger number) version so I do not think some patch to actually downgrade it exists?

edit: OR maybe GOG used some "wrong" patch on KB:L before release? Isn't "showflyingdead=2" setting characteristic for KB:Armored Princess? (I am not so sure about this but every other version of KB:L had "0" here and every game.ini I saw from KB:AP seemed to have "2" here)

i've sent an info to GOG's support.

If anyone else is able to check this bug on his/her version please do so. The more reports the better.

Thank you for doing this, Lexor! I appreciate your efforts. I own the GOG and Steam versions of this game, so I'm going to see if I can reproduce the previous reports.

That would be awesome - to compare both versions on the same PC! Cant wait to see the results! :)

Maybe even we'll find out differences in files to create some patch?

Okay, I've reproduced the bug in the GOG version (1.7 build 35396). I'm going to download the Steam version now and see what happens.

Thanks for info :) Now I wonder if its possible to install both versions at the same time? Probably not... Anyway it would be good to do directory scans (names/number of files, their sizes etc) of both versions to see the differences.

Unfortunately, I don't think you can install the two different versions simultaneously. I tried doing that with a different game, but Steam recognized that a non-Steam version was already installed and wouldn't let me proceed with the installation. I can save the two main executables for comparison, but I'm not sure how much that would help since the Steam version will probably look rather different due to its connection to the Steam client/DRM and not just because of the different build number.

Ah yes, you are right. :(

Still maybe it could be some idea to make simply backup of current installed version to some other directory (by just coping files) before uninstall. Exes could be really different but files like *.kfs should not I think?

Ditto.

I've been eying this game for awhile and am curious about how this all shakes out. Does this bug get in the way with the enjoyment of the game in any significant way?

As I said before: But if this is the one bug how I can be sure that this "new" version have not introduced any others, not so clearly visible? Do not forget also about "showflyingdead" bug but it can be easily corrected by editing game.ini file.

The other thing that comes here into my mind is one of the quests from Furious Paladin (NPC). I remember (from Polish version I've played) that after I've blessed all crypts (and before taking next quest about destroying monuments) he has got his shop refilled with new units to buy as reward, but when I played GOG version now his shop remains empty (I've bought out all units before finishing this quest). But this just could be just my bad luck?