(⬤ᴥ⬤)@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 5 months agoefficient game design rulelemmy.blahaj.zoneimagemessage-square11fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1imageefficient game design rulelemmy.blahaj.zone(⬤ᴥ⬤)@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 5 months agomessage-square11fedilink
minus-square9point6@lemmy.worldlinkfedilinkarrow-up1·edit-25 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-squaremogoh@lemmy.mllinkfedilinkarrow-up1·5 months agoYeah, that does not add up, you are right. There must be several error or it must include the stacktrace or something.
minus-squarefallingcats@discuss.tchncs.delinkfedilinkarrow-up1·5 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.
If you’re getting a stack trace every frame youd be there much sooner. Maybe like a week.`