Wuthering Waves Engine Lead Implies Kuro Games Ruined Optimization After He Left — Players Split: Did His Departure Break the Game, or Was It Always Broken?

A former engine lead at Kuro Games posted on social media two months after leaving the company, strongly implying that the team destroyed his carefully crafted optimization work after his departure. The post instantly blew up on NGA, splitting the community into two warring factions.

According to the thread, this engine lead left before Wuthering Waves' official launch, and on his way out, he took some thinly veiled shots at his former employer. While he didn't name names, the implication was clear: whoever took over his optimization work butchered it, directly causing the performance disaster at launch. As one NGA user put it: "He's basically saying they wrecked his work after he left. Whether you believe him is up to you, but that's definitely what he meant."

The "he left and everything broke" camp had a compelling piece of evidence: Wuthering Waves' third closed beta ran fine, but the public launch was plagued by stutters, frame drops, and VRAM leaks. One commenter noted, "The problems at launch didn't exist in beta 3." Another added: "If that's the case, something changed after he left. Performance optimization isn't a 'it worked last version so it'll work this time' kind of thing — you have to constantly monitor it."

The most absurd detail? Players reported their GPUs running out of VRAM while playing, and the community's workaround was to simultaneously run a second game that clears memory — essentially using one game as a VRAM janitor for another. As one commenter deadpanned: "Thank god GPUs can't talk back." This might be the most unhinged player workaround of 2024.

The opposition wasn't having any of it. One user fired back: "This guy has the nerve to show up? The optimization was garbage in every beta." Another analyzed: "You think his departure caused the performance issues? Performance engineering runs through the entire dev cycle — it doesn't just fall apart because one person left." Others were even harsher: "If anything, this proves firing him was the right call. His optimization work was trash from the start."

One commenter laid out a devastating catch-22: "How do you even defend this? If you call him incompetent, then an incompetent person was the engine lead — how bad is the team? If he's actually talented, then he left a company so toxic he had to air dirty laundry on his way out — how bad is the team?" Either way, Kuro Games' management doesn't come out looking good.

The more technically-minded commenters urged caution. One explained: "Performance can break because of a single change deep in the system — like resource recycling logic — that cascades into a full meltdown. You can't just blame one person." Another borrowed a football analogy: "The guy who never plays is always the best player on the bench, because when you lose, he's the one who can say 'I would've won it for us.'" In other words, easy to claim credit when you're not on the field.

It's also worth noting that Wuthering Waves' performance issues are hardly unique. As one player observed: "There's never been a mobile open-world gacha game with good optimization — not Genshin, not Tower of Fantasy, and not Wuthering Waves." The genre seems permanently cursed when it comes to mobile performance.

As of now, Kuro Games has not issued any official response. Whether the former engine lead's claims are a righteous whistleblower speaking truth to power or a disgruntled ex-employee throwing shade, only the source code — and the people who wrote it — know the real answer.