- cross-posted to:
- hackernews@lemmy.bestiver.se
- cross-posted to:
- hackernews@lemmy.bestiver.se
This was a fun one. Here’s my newest post on how to dramatically reduce Godot’s build size.
Some sacrifices were made… But the end result is a Godot project that works exactly the same, albeit with slightly worse performance. Hope this can help others in achieving tiny build sizes!
But, why?
100mb are already negligible. I want a reasonable size (less 20GB) and ok performance.
@Gladaed @popcar2 web, mobile, and as always, less space and optimization is always a good thing.
Wasting time on metrics that don’t matter is waste. I get and agree with mobile/web constraints. I did not consider them.
@Gladaed @popcar2 because every bloated 100gb game is a mix of a thousand different assets/executables/libraries where the developer thought “why optimize, 100MB is nothing”.
Often with little more than symbol stripping, removing unneeded files, and basic lz compression you can cut most game sizes in half, reduce load times, and free up terabytes of space on your system.
The article begins by talking about web exports. The default there is 42MB, which is kind of a lot for the web
Edit: Of course, compressed it is ~9, which isn’t so bad, I suppose.
For mobile this is a legit difference imo
Also what raptor said.
@Gladaed @popcar2
See https://mastodon.gamedev.place/@popcar2/114144232496373416