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

×
avatar
user deleted: I think i remember asking GOG support back in 2017 if they'd get the latest updates for this game and iirc they said they're working on it but no ETA. 2 years later still nothing...
Well its been 4 years now and no new patches from Capcom. last one was in 2017 that fixed the save corruption bug when switching modes.
Time to spam Capcom to fix the GOG version which could be the best version if they really wanted.

- They need to fix the pawns system
- Add the new languages
- Fix the misc bugs they fixed on the steam version
- Add back the berserk equipments.
- Add borderless full screen

All we need is some support send tickets to Capcom guys.
avatar
MasterDarkseid: All we need is some support send tickets to Capcom guys.
Rather to General Arcade. The one who's responsible for the GOG port.

See details below.

https://generalarcade.com/project/dragons-dogma-dark-arisen/
avatar
自在猫: Rather to General Arcade. The one who's responsible for the GOG port.

See details below.

https://generalarcade.com/project/dragons-dogma-dark-arisen/
General Arcade is responsible for Galaxy SDK integration into GOG version. Ppl behind PC port (there is only one) are QLOC, as stated in credits - while GA didn't even get this.
Attachments:
avatar
zadymek: General Arcade is responsible for Galaxy SDK integration into GOG version. Ppl behind PC port (there is only one) are QLOC, as stated in credits - while GA didn't even get this.
Interesting. That's a new to me. Thanks for the info!

I did some research based on that one. As you said, QLOC is not specifically responsible for the GOG port but instead of the general PC port.

https://q-loc.com/dragons-dogma-dark-arisen-for-the-pc/

A post stating the Steam version has the same credit roll approves that.

https://steamcommunity.com/app/427190/discussions/0/350541595107941600/?l=italian#c350541595120107033

So if I'm correct, QLOC has done their job porting the game to PC, otherwise we wouldn't have the up-to-date version on the other storefront. Thus all the files and contents should already be ready for the outdated GOG version to use.

And Starkrun made a post of GOG=Steam patch here (You knew it :D). The said patch didn't crash the game, but based on the replies seems unfortunately it didn't fix the pawn system and some broken quest still hadn't been resolved. Which sounds to me is likely the different versions of the excusable files not being totally compatible with the new contents to be blamed. Also which is supposed to be the work of GA to accomplish (if I'm not mistaken with what SDK does).

Edit: or Capcom, if they didn't, for not providing the patched files since it is them who have the ownership.
Post edited March 17, 2024 by 自在猫
avatar
自在猫: I did some research based on that one. As you said, QLOC is not specifically responsible for the GOG port but instead of the general PC port.
Fun fact: if we're to believe the in-game manual, that refers to features exclusive to Steam, the game on both storefronts is a Steam version.
avatar
MasterDarkseid: Time to spam Capcom to fix the GOG version which could be the best version if they really wanted.

...
- Add borderless full screen

All we need is some support send tickets to Capcom guys.
Just found this thread while searching for borderless fullscreen. True Fullscreen works, the game just doesn't remember the settings correctly. It still says "Fullscreen ON", but after a reload I always have to switch to OFF (+ return) and then back to ON (+ return) for it to work.

Is this the bug you are referring to? Certainly a bit annoying, but not a game stopper. I guess this can't be too hard to fix?

I'm still very new to the game, so I can't comment on the other things yet...

EDIT

I only had to edit the link that is created on the desktop during installation (as administrator: right mouse button -> Properties). Strangely enough, the "Execute" (not quite sure, in German it's called "Ausführen in") field was set to "Normal Window". Change to "Maximized" here will solve the issue.
Post edited April 02, 2024 by Rubinstein