search

ZeroK-RTS / Zero-K-Infrastructure

Website, lobby launcher and server, steam deployment, .NET based tools and other vital parts of Zero-K infrastructure
GNU General Public License v3.0
53 stars 52 forks source link

Fresh Steam install is too large #2752

Closed GoogleFrog closed 3 years ago

GoogleFrog commented 3 years ago

A fresh steam install is 5.1GB.

There are 145 maps included in a fresh install. The campaign only uses 71 maps and there are 24 matchmaker maps, a lot of which overlap with the campaign maps. A lot of extra maps are being included from somewhere, perhaps the popularity thing that @DeinFreund added a while ago?

470MB would be saved by removing the following maps:

I think the inclusion of Twin Lakes Park, Boulder Beach and the large FFA maps shows that the automated popularity system isn't working properly, or I don't know where maps come from. As far as I know maps come from three places:

Reducing install size is important because a long install gives potential players more time to forget what they are doing and wander off.

DeinFreund commented 3 years ago

I never touched Steam depot generation, but for what I can tell it simply keeps adding maps and never removes the old popular maps, thus ballooning in size.

Licho1 commented 3 years ago

Deployment is automated and based on map labeling - just re-label maps to fix that. But I dont think 5gb is much.. just finished downloading 97GB of destiny 2. Took couple of days on my village connection but I didnt forget.

GoogleFrog commented 3 years ago

@Licho1 as far as I know it isn't purely based on map labeling since @DeinFreund added a popularity metric.

Licho1 commented 3 years ago

Oh I see.. ok..

DeinFreund commented 3 years ago

I repeat, I did not touch steam depot generation. Map selection has been untouched ever since its original implementation.

DeinFreund commented 3 years ago

Maps should be cleared before generation now, which hopefully fixes this.