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

×
Every time I verify the game files GOG Galaxy downloads 175MB and installs.

Why is this happening?

Do you also have this?
Attachments:
No posts in this topic were marked as the solution yet. If you can help, add your reply
Not sure exactly what you were taking about. However, in order for GOG to verify your installation, a reasonable expectation is that GOG has to download enough data based on what you wish it to verify. And for a massive game like BG3, whose installation exceeds 100GB, a download of175MB data - less than 0.18% of the total size of the game - seems to be very reasonable.

Nothing unexpected here.
avatar
HenryNY: Not sure exactly what you were taking about. However, in order for GOG to verify your installation, a reasonable expectation is that GOG has to download enough data based on what you wish it to verify. And for a massive game like BG3, whose installation exceeds 100GB, a download of175MB data - less than 0.18% of the total size of the game - seems to be very reasonable.

Nothing unexpected here.
It's not that it downloads files, it makes no difference to me how many gigabytes they have. What I mean is that after installing these 175MB. If I check the files again, the situation will repeat. It will download and install 175MB again.
it will be DX11 files at that size
avatar
ussnorway: it will be DX11 files at that size
I have DX12 istalled by DX12.
it doesn't matter what version you have actually installed the game uses the DX11 files [which are included in a standard DX12 install] the verify is re-downloading them because your system detects that they are missing or Galaxy just can't use them
avatar
ussnorway: it doesn't matter what version you have actually installed the game uses the DX11 files [which are included in a standard DX12 install] the verify is re-downloading them because your system detects that they are missing or Galaxy just can't use them
So, it's probably a Galaxy bug.
It's not bug no... I expect your system is setup to block access