I´m very disappointed that every patch they realize, It never install because I don´t have enough space, I don´t understand how is possible for a 817mb I need more than 100 gb of free space is annoying, sorry for my bad english.

The patch is only 800mb but they need to modify a lot of data with it so that's why they need the extra space. In general, I'd recommend having at least 100gb free on every hard drive you have (if they are 1tb or larger, at least) as it can have a minor boost in speed for installations, defragging, etc. This is especially important on older, larger drives but not quite as big of a deal for SSDs.

That extra space is not listed anywhere in system requirements.

70GB for game alone is neat.

100GB for offline installer on top of that doesn't feel right already.

Extra 385GB for an update is pure baloney.

My entire HDD is 1TB. I'm not ready to dedicate half of that space to a game which obliviously and thoroughly defies each and every core concept of PC gaming.

Especially since that extra requirement arrived long after release (and game purchase).

As I said, these patches are moving a lot of data. It's annoying, no doubt, and I think GOG would be wise to add some better statistics for download, disk usage, etc when updating games, but it does make sense. It doesn't ACTUALLY take that much space, it just needs that much free to move stuff around.

Totally agree, something is messed up with how the GOG patcher utilities work. Sure, it's good that you don't need to download the entire game again and can actually apply a patch, but this bizarre space requirement has also hit me to the point that I just gave up and grabbed the entire game again anyway...

The thing is, the entire game unpacked is < 70 GB, so the worst case should be that the patch requires 70GB on top of that to do it's merging. There's no way it should require the space it actually does, that's just absurd.

I perfectly understand your concern, but please keep in mind that the patch doesn't modify the files as they appear in the game folder. It has to unpack the compressed files first, modify them and then pack them again into the format recognizable by the game. It all takes disk space. Uncompressed files would eat 200-300 GB of free space just to install the game.

Well if it's done that way then no wonder it takes so much space. Would be more efficient to merge the changes in as they're being unpacked, surely? The issues going this route would be the risk of potentially trashing someone's installation if there's an error in the process, and making it difficult (or nigh impossible) to revert - which IMO is something I'd be willing to accept. Of course that will mean using a different set of unpacking/patching tools... and the whole thing may not be that viable if unpacking of compressed files is required, only for them to need to be recompressed...

But what would hopefully be doable and useful: it should probably be mentioned somewhere how much space these patches actually require before we download them (at least in the changelog section if nowhere else - e.g. prominently at the top, though ideally on the same page where the dl link is), if at all possible. In my case I would have then just decided to download the full installer instead, since I'm in the same boat as others here - I don't have enough space for this patching process, but at the same time feel there's still enough space on my drive that I won't be upgrading it just yet.

Potentially trashing someone's installation.
Or HDD.
Or CPU.
Or whatever.

Alas, if the patch needs more space on HDD than unpatched game needs - why not forcing full game redownload?
Or initiating game folder repair?
Or downloading diffs between packed unpatched game files vs packed patched game files?

You're not expecting different end users having different checksums of same files of same game version, do you?

I believe it appears to be more a case of GOG using tools that in the case of patching Cyberpunk at least require:
- the files already on the disk to be uncompressed to a temp folder
- the files from the installer to be unpacked and possibly uncompressed further to a different temp folder
- these two files then merged into a third file
- this third file then recompressed and copied into the Cyberpunk directory
- all temp files erased to get our massive GB back

BTW I agree that they could most likely easily use a tool that unpacks, repacks and merges on the fly, or as you state do a binary merge (tbh binary merges can be a pain - if the project contains a lot of files, then the most logical thing would be to just straight up replace individual files. Cyberpunk has 90% of its content in the archive directory, which is split into 31 files. The problem is these are all "archive" files, and large patches no doubt replace stuff in a whole bunch of these...

Hopefully they only patch one archive file at a time - but it wouldn't surprise me if these 16GB archive files expand to 50GB, which is then tripled if they do a bunch of copying and then re-archiving...