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
Thiev: They are generated alongside everything else, if possible / if it makes sense. If patch would almost the size of a whole game, then it's rather pointless. If patch cannot be generated for some technical reason, it's skipped and the whole process needs to be tweaked a bit to make it work (hopefully) next time.
I guess this mean GOG has now built some tools to automate the entire process even for standalone installers? I assume standalone installers will still be tested before being added to the site but this should speed up deployment then.

Because last time we had any info on this, GOG was basically still doing all of this "by hand" as you would say.
Post edited June 09, 2017 by BKGaming
avatar
BKGaming: Because last time we had any info on this, GOG was basically still doing all of this "by hand" as you would say.
Making tools, testing tools, fixing tools *and* using them all at the same time is 'fun'.
Has anyone explicitly stated we are doing eveything by hand though? Or was it always assumed ;)
avatar
Thiev: I wasn't even forced to push that online update. It was my own decision to put it up earlier.
Really, folks - I have no problem with dutifully waiting until both versions are done and tested. Just no one will play the updated game over the weekend.
Well ok then, If it's an exception for the weekend.
But please, just don't let the other installers constantly lag behind.
avatar
Thiev: Making tools, testing tools, fixing tools *and* using them all at the same time is 'fun'.
Has anyone explicitly stated we are doing eveything by hand though? Or was it always assumed ;)
No, I think it was more assumed by us and "by hand" probably isn't the right saying... what I mean by that is it wasn't really automated. At least based on some of the discussions we had in the update thread. But perhaps Judas was referring to the process of getting the standalone installers onto the site at the same time as Galaxy, not exactly making the installers themselves.

Always interesting when we get some insight into this stuff though. :)
Post edited June 09, 2017 by BKGaming
avatar
Thiev: Making tools, testing tools, fixing tools *and* using them all at the same time is 'fun'.
Has anyone explicitly stated we are doing eveything by hand though? Or was it always assumed ;)
I've always assumed you guys used both hands and both feet, with at least one hand firmly grasping a long sword, and a Kung Fury type red headband tied around your head. Please don't ruin this vision in my mind, it's one of the few things I have left. :)
I am glad to see both are still being produced. I could not get Witcher 2 or 3 to work after downloading them through Galaxy, so if it means waiting a day or 2, so be it.

I have nothing against Galaxy. Don't make it "required" and I will be very happy. Now I have W2 working for the time being, I will reinstall Galaxy.

It would quell plenty of unease on the forum, if you would just tell us "yes" at some point in the future, you will have to use it, or "no" you won't.

have fun, Ian
avatar
tfishell: I'm really hope we'll see some results from the dgVoodoo partnership soon.
avatar
Thiev: I cannot really comment on something that was never officially announced by GOG. It's not my area and I'm not even getting into this discussion.
Darn, okay. I can understand that you can't comment since it hasn't been announced by GOG, but I thought since dgVoodoo was a "tech' thing, it would be your area.
avatar
Thiev: Really, folks - I have no problem with dutifully waiting until both versions are done and tested. Just no one will play the updated game over the weekend.
I gotta say this is the best thread I have ever read.. so much great info...

Love to see GOG employees talking with the users, and as a Galaxy and Manual archivist I am 100% ok with waiting for a patch while Galaxy updates early... keep on doing what you do for us :)
avatar
Starkrun: Love to see GOG employees talking with the users, and as a Galaxy and Manual archivist I am 100% ok with waiting for a patch while Galaxy updates early... keep on doing what you do for us :)
Same here, even though I don't use Galaxy currently and rely only on the offline installers.

I feel the OP was complaining more on principle than something that really affects him. The thread title suggests that some GOG games will not get updates at all to the offline installer (only to the Galaxy version)... yet it was only a case of GOG informing users that while the Galaxy version got updated on Friday, the offline installer will get installed on next Monday.

Oh my god, that can't be legal can it? Someone call the police! All GOG staff not working on weekends? Pffffffffffffffffffffffffffffffffffffffffffffffffft...

If I really was playing games where it is critical to get updates ASAP (e.g. online multiplayer games where all players must use the same version of the game, or in-dev games with lots of serious bugs), then I would probably want to use a client for them anyway, either Galaxy or Steam. If not for other reason but that I don't have to install the frequent updates manually myself, but the client would always keep them updated automatically.

With games which are already stabilized and don't get updated that often anymore, no need for auto-updating, so I am fine with offline installers.

As a matter of fact, I would be fine even if GOG skips some of the less important updates for the offline installers, and gathers them into bigger packages which they then deliver to the offline installers less frequently. So, if some in-dev game is getting updates several times a week or even daily, I am not really expecting GOG to update the offline installers daily. In fact, at that point I start hoping they wouldn't update them constantly. Once a week, or with less critical updates even once a month, is quite fine to me.
Post edited June 10, 2017 by timppu
avatar
Antoni_Fox: So i can only get the latest game updates by going online with GOG Galaxy now... Might as well just buy everything on Steam if we are going to be actively forced to use Galaxy.
You mean that a client that was promoted as a way to get patches earlier is actually getting patches early ?

It's almost as if it's doing what it actually was advertised to do...


avatar
BKGaming: Because last time we had any info on this, GOG was basically still doing all of this "by hand" as you would say.
avatar
Thiev: Making tools, testing tools, fixing tools *and* using them all at the same time is 'fun'.
Has anyone explicitly stated we are doing eveything by hand though? Or was it always assumed ;)
Personally I always considered that the "manually" meant that for the offline installer it had to be initiated / supervised by Gog teams while Galaxy updates were more of a single button push thingy. Not really that it meant that Gog had to manually create all installers by hand ;)
Post edited June 10, 2017 by Gersen
So is it always this "knee-jerky" around here nowadays? O_o
avatar
tammerwhisk: So is it always this "knee-jerky" around here nowadays? O_o
It really is.
avatar
Antoni_Fox: So i can only get the latest game updates by going online with GOG Galaxy now... Might as well just buy everything on Steam if we are going to be actively forced to use Galaxy.
avatar
Gersen: You mean that a client that was promoted as a way to get patches earlier is actually getting patches early ?

It's almost as if it's doing what it actually was advertised to do...
There is nothing wrong with getting patches in early.

The question is, why can't we get the same patches via the other route, at the same time?

Client A is called firefox or chrome or whatever. Client B is called galaxy. Both download files from the internet. Why can't A get the same files at the same time as B does?

It sounds like either the automated process for creating the installers, or the installers themselves, have some unnecessary technical limitation.
Post edited June 10, 2017 by clarry
avatar
clarry: Client A is called firefox or chrome or whatever. Client B is called galaxy. Both download files from the internet. Why can't A get the same files at the same time as B does?
Well from what Gog told us and what I understood (Thiev can probably give is more information on that), with Galaxy they basically have an "installed" (actually more than one as they keep multiple version) reference version of the game on their servers; when the devs want to patch the game they simply update this installed version.

Then Galaxy compare between the installed version on your computer and the reference installed version on Gog server and download the differences. You don't have to create any installer / patcher it's all handled by Galaxy and if you want to rollback you simply tell Galaxy to do the comparison to a specific older version instead of the latest one.

With the offline patches they have to get the changes, create installers, test them, upload them, etc... even if most of this process is probably automatized it's still more work than the Galaxy route and probably requires more involvement from Gog team too.
avatar
clarry: Client A is called firefox or chrome or whatever. Client B is called galaxy. Both download files from the internet. Why can't A get the same files at the same time as B does?
avatar
Gersen: Well from what Gog told us and what I understood (Thiev can probably give is more information on that), with Galaxy they basically have an "installed" (actually more than one as they keep multiple version) reference version of the game on their servers; when the devs want to patch the game they simply update this installed version.

Then Galaxy compare between the installed version on your computer and the reference installed version on Gog server and download the differences. You don't have to create any installer / patcher it's all handled by Galaxy and if you want to rollback you simply tell Galaxy to do the comparison to a specific older version instead of the latest one.
If Galaxy can compare and update files, it must have access to those files and the relevant metadata about them. Why don't we have access to the same files via the browser?

With the offline patches they have to get the changes, create installers, test them, upload them, etc... even if most of this process is probably automatized it's still more work than the Galaxy route and probably requires more involvement from Gog team too.
> get the changes
If galaxy can do it automatically, so can anything else

> create installers
If galaxy can install files automatically, installers can be created automatically

> test them
If galaxy can download untested updates, so can a browser

> upload them
If galaxy can access these files, they are already uploaded, why can't we have them?

I guess I'm more after the files and metadata that are relevant to installing and updating the game, and not so much after the installers that bundle these files up.

But Thiev suggested the process is automated, and honestly I didn't expect anything less?

So I'm curious about the technical side of things.
Post edited June 10, 2017 by clarry
avatar
clarry: Client A is called firefox or chrome or whatever. Client B is called galaxy. Both download files from the internet. Why can't A get the same files at the same time as B does?
Because Client B is directly integrated with the games and client A is not. Client B can be customized to tailor the experience by GOG and client A can not (at-least not to the point where it can be integrated with the games, just server side).