(⬤ᴥ⬤) to [email protected] • 3 months agoefficient game design rulelemmy.blahaj.zoneimagemessage-square39fedilinkarrow-up1747arrow-down117cross-posted to: microblogmemes
arrow-up1730arrow-down1imageefficient game design rulelemmy.blahaj.zone(⬤ᴥ⬤) to [email protected] • 3 months agomessage-square39fedilinkcross-posted to: microblogmemes
minus-square@9point6link74•edit-23 months agoSo 300×1024×1024= 314,572,800kb Assuming something like 200 bytes per log line x5 = 1,572,864,000 logs Assuming this is your standard console port with a 60fps frame rate lock: ÷60fps ÷ 60 seconds ÷ 60 minutes ÷ 24h = 303.407… days You would need to play for nearly a year solid to generate that many logs at a rate of one per frame. Given that’s probably not what’s happened, this is a particularly impressive rate of erroring
minus-square@[email protected]linkfedilink52•3 months agoYeah, that does not add up, you are right. There must be several error or it must include the stacktrace or something.
minus-square@rtxnlinkEnglish31•3 months agoIt’s possible that the log writer wanted to fseek to the end of the file and write something, but the target pointer value was somehow corrupted. Depending on the OS, the file might end up having a fuckton of zeroes in the skipped part.
minus-square@TheEntitylink10•3 months agoThat should result in a sparse file on any sane filesystem, right?
minus-square@rtxnlinkEnglish9•3 months agoTheoretically, yes. Theoretically NTFS supports sparse files, but I don’t know if the feature is enabled by default.
minus-squareThe_DecryptorlinkfedilinkEnglish2•3 months agoIt supports it, but it’s opt-in by apps. Enabling compression is another option (Though with a speed and size penalty), it’s user visible at least.
minus-square@[email protected]linkfedilink8•3 months agoIf you’re getting a stack trace every frame youd be there much sooner. Maybe like a week.`
So
300×1024×1024= 314,572,800kb
Assuming something like 200 bytes per log line
x5 = 1,572,864,000 logs
Assuming this is your standard console port with a 60fps frame rate lock:
÷60fps ÷ 60 seconds ÷ 60 minutes ÷ 24h = 303.407… days
You would need to play for nearly a year solid to generate that many logs at a rate of one per frame.
Given that’s probably not what’s happened, this is a particularly impressive rate of erroring
Yeah, that does not add up, you are right. There must be several error or it must include the stacktrace or something.
It’s possible that the log writer wanted to
fseekto the end of the file and write something, but the target pointer value was somehow corrupted. Depending on the OS, the file might end up having a fuckton of zeroes in the skipped part.That should result in a sparse file on any sane filesystem, right?
Theoretically, yes. Theoretically NTFS supports sparse files, but I don’t know if the feature is enabled by default.
It supports it, but it’s opt-in by apps.
Enabling compression is another option (Though with a speed and size penalty), it’s user visible at least.
If you’re getting a stack trace every frame youd be there much sooner. Maybe like a week.`