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

×
Community
Darkest Dungeon*WARNING*, non-steam and/or linux users = second class customers for devs(22 posts)(22 posts)
(22 posts)
Pages:
1
2
This is my favourite topic
Posted January 12, 2020
avatar
Myozhen: Mods are definitely not well supported in the GOG version of Darkest Dungeon.

You can see the posts about localization.exe not working at all with the GOG version. 'localization.exe' is needed to compile localization files if people want to make a mod or modify text in game. People have contacted the devs and received no reply for that problem. I have investigated it, here are the findings:

You can go to the 'colours' directory and copy 'base.colours.darkest' to 'colours.darkest' in the same directory. After that you can run localization.exe . Copying to colours.darkest makes the included localization.exe work. Trying to run Darkest Dungeon after that will make it crash.

So why does it crash?

It crashes because the localization.exe included in the '_windowsnosteam' directory was updated on the Monday 23 November 2015. It is a truly ancient version of that executable and produces significantly different output to the latest version included with Steam. It does not work with current versions of Darkest Dungeon whether they are on Steam or not. The version included in Steam was updated on Tuesday 5 September 2017.

If you copy the '_windows' directory from the Steam installation into the GOG Darkest Dungeon base directory and then run localization.exe from that, it works perfectly.

So Red Hook have ignored the requests to get localization.exe working on non-steam versions. All they had to do was put the steam version in the '_windowsnosteam' directory and call it done, no need to actually change any logic in the executable. (Okay, they could remove the steam_api.dll dependency in it which seems to be there for no reason at all). Yes, the fix was that easy.

------

Also developers limiting steam workshop downloads while having their game sold on other platforms is terrible for people on other platforms. I would suggest that they allow downloads for people who don't own the game on Steam. IIRC they have the ability to allow that. I had that problem owning Party Hard on GOG and not being able to download user created levels for it. That sucked.
Now at least the localization.exe is working in the _windowsnosteam with no problem for me...
To solve the mod problem, i just ran Darkest.exe in _windowsnosteam Directly...

Running it with the GOG shortcut mods does not work, but running it directly from the exe does work...
I am using Version 24839 (from GOG of course).
Posted June 29, 2020
avatar
Myozhen: Mods are definitely not well supported in the GOG version of Darkest Dungeon.

You can see the posts about localization.exe not working at all with the GOG version. 'localization.exe' is needed to compile localization files if people want to make a mod or modify text in game. People have contacted the devs and received no reply for that problem. I have investigated it, here are the findings:

You can go to the 'colours' directory and copy 'base.colours.darkest' to 'colours.darkest' in the same directory. After that you can run localization.exe . Copying to colours.darkest makes the included localization.exe work. Trying to run Darkest Dungeon after that will make it crash.

So why does it crash?

It crashes because the localization.exe included in the '_windowsnosteam' directory was updated on the Monday 23 November 2015. It is a truly ancient version of that executable and produces significantly different output to the latest version included with Steam. It does not work with current versions of Darkest Dungeon whether they are on Steam or not. The version included in Steam was updated on Tuesday 5 September 2017.

If you copy the '_windows' directory from the Steam installation into the GOG Darkest Dungeon base directory and then run localization.exe from that, it works perfectly.

So Red Hook have ignored the requests to get localization.exe working on non-steam versions. All they had to do was put the steam version in the '_windowsnosteam' directory and call it done, no need to actually change any logic in the executable. (Okay, they could remove the steam_api.dll dependency in it which seems to be there for no reason at all). Yes, the fix was that easy.

------

Also developers limiting steam workshop downloads while having their game sold on other platforms is terrible for people on other platforms. I would suggest that they allow downloads for people who don't own the game on Steam. IIRC they have the ability to allow that. I had that problem owning Party Hard on GOG and not being able to download user created levels for it. That sucked.
avatar
rallymoose: Now at least the localization.exe is working in the _windowsnosteam with no problem for me...
To solve the mod problem, i just ran Darkest.exe in _windowsnosteam Directly...

Running it with the GOG shortcut mods does not work, but running it directly from the exe does work...
I am using Version 24839 (from GOG of course).
Hello, can you explain what does work for you when running from the darkest.exe and does not when running from the shortcut?

As far as I know, after a clean install of the newest version 24839-GOG if I run the localization.exe, the affected files (base game) are changed and you cannot run the game anymore.

I don't know how exactly one has to call the localization.exe to generate the loc files for a mod without changing the other loc files. I tried removing temporarily the localization folder and just putting the localization folder of a mod; the generated loc files aren't working for me.
Posted December 01, 2021
So in order to make most class mods work correctly for gog version, I've to buy steam version too and download > _windows folder?

The exe in current version, after copying to _windows and activate localization.bat, it appcrashes,

(still at version 24839)

Just bought the steam version, install it and the localization.exe would run without error, but the blue strings for mods still exist. Even replacing the darkest.exe (which makes the program run by steam client) would still have the blue strings remain.

Would have to copy all the dlc file to the steam version just installed and launch by steam version to remove the blue strings error.

The steam version is at 25688 and lots of things differ, likely from the exe.
Post edited December 01, 2021 by sorrowofwind
Posted April 18, 2022
I never use mods.
Posted May 17, 2022
I did not know, that the developers abandoned the GOG version. Sadly I cannot install an translation for my motherlauguage. :(

I had to ask for a refund.
Thank you for you rapid help, GOG support team!
Posted June 03, 2023
Thanks for the Heads-Up! Was waiting to buy but, this is just scummy.
Posted 3 days ago
I think it's accurate to say that the 'localization' shipped with the Gog version doesn't work, and 'just use nexus mods' isn't a good answer, they're missing half the mods for this, at least and they've gone way down hill.

That being said I'm going to work on the other thread and see if _windows localization exe from steam can unpack the steam mods localizations properly, because that's my missing link. I found the other thread that explains that cleanup process so that's where I'll head to next.
Post edited 3 days ago by siegeshot
Pages:
1
2
This is my favourite topic
Community
Darkest Dungeon*WARNING*, non-steam and/or linux users = second class customers for devs(22 posts)(22 posts)
(22 posts)