this post was submitted on 19 Sep 2024
737 points (97.8% liked)

196

16303 readers
2025 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 1 year ago
MODERATORS
moss@lemmy.blahaj.zone
greembow@lemmy.blahaj.zone
moss@lemmy.world
queue@beehaw.org
funky_rodent@lemmy.blahaj.zone
PeachyMcPeachface@lemmy.blahaj.zone
threegnomes@lemmy.blahaj.zone
greembow@lemmy.world
remotelove@lemmy.ca
Roflmasterbigpimp@feddit.de
qaz@lemmy.world
A_Very_Big_Fan@lemm.ee
qaz@lemmy.blahaj.zone
qaz@lemmy.ca
A_Very_Big_Fan@lemmy.world
qaz@lemmy.dbzer0.com
Qaz@lemmy.ml
qaz@sh.itjust.works
qaz@lemmy.sdf.org
737
efficient game design rule (lemmy.blahaj.zone)
submitted 2 weeks ago by nicknonya@lemmy.blahaj.zone to c/196@lemmy.blahaj.zone
47 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] MoogleMaestro@lemmy.zip 22 points 2 weeks ago (2 children)

Like what else would a .log file be? A video file? A Word Document? An executable?

I think their point is that a 200gb text file is a wild size usage for a crash log, and there's probably accidentally some binary data in that log. There's no way a crash log can exceed 2x the size of the game binary itself.

[–] HoloPengin@lemmy.world 22 points 2 weeks ago

Could be a bug in their crash handler, just like, infinitely looping and printing something over and over.

[–] leftytighty@slrpnk.net 3 points 2 weeks ago

Binary data is almost always more compact than text data