Overwatch 2's D.Va Bug Is Back and Launching Players Into Another Match

I've been playing Overwatch since before role queue was a twinkle in the dev team's eye, and I thought I had seen every physics oddity the game could throw at me. Then I saw the clip of a D.Va getting charged by Reinhardt, slipping through a wall, and getting catapulted not just off the map but into an entirely different match. That's not just a bug—it's the Overwatch equivalent of being asked to leave one party and suddenly waking up at a completely different party with no explanation.

The original report comes from Reddit user jmiranda005, who shared a clip of this weirdness in Overwatch 2. In it, a charging Reinhardt pushes D.Va through a wall and off the map entirely. The timing is the real kicker: if you watch the text chat closely, an error warning pops up about half a second before D.Va gets launched. So this may have been a game crash that just happened to detonate at the exact moment D.Va's mech ejection was already arguing with the map geometry. In other words, the physics engine folded like a cheap lawn chair in a hurricane, and D.Va was the one who got flung through the patio door.

Why D.Va keeps getting picked on

D.Va is the only hero in the roster who has two distinct playable states: pilot and mech. Whenever she gets de-meched, the game has to instantly swap her collision box, reposition her camera, and recalculate where "solid ground" is supposed to be. That transition is a perfect little storm for bugs. Think of it like trying to swap the engine out of a moving car while still driving—most of the time it works, but when it doesn't, you end up in a cornfield three counties away.

This isn't even new. Way back in 2017, D.Va players in the first Overwatch reported that being knocked out of their mech was causing them to fall through the map entirely. Back then it was more of a quiet, accidental drop into the void. The Overwatch 2 clip is the same ghost wearing a louder costume, because now the game seems to eject the player from the entire match instead of just the map.

Is it a crash or a genuine bug?

The half-second warning in chat complicates things. If the game client crashed for an unrelated reason, the "launch into another match" might just be how the replay or reload process handles a sudden disconnect. But even if the crash was separate, the visual of D.Va being shoved through a wall by Reinhardt and immediately leaving the match is... well, it's hard not to laugh. It's like playing poker and the dealer suddenly swaps your table mid-hand, then insists you were always at the new table.

Other weird bugs still hanging around

Overwatch 2 has never exactly been short on glitches. Here are a few that have made me question my life choices:

• D.Va mech ejection bug: Getting knocked out of mech can occasionally send you through terrain or out of the match.

• Lucio Snow Fox skin issue: This skin has been causing Lucio to be visible through walls, which turns every corner into a horror movie jump scare.

• Sombra payload clipping: Players found a way to get Sombra inside the payload, basically turning her into an invisible objective-camping gremlin and pretty much guaranteeing a win.

Final thoughts

I'll be honest: part of me hopes this D.Va bug sticks around just a little longer, not because it's good for competitive play, but because it's the kind of chaotic energy that makes Overwatch highlights so unforgettable. Playing D.Va with this glitch is like riding an ejection seat in a submarine—you're leaving the situation, but not through any hatch that makes sense. In 2026, as Overwatch 2 keeps evolving with new heroes and balance patches, I'd like to think the devs will eventually nail down these collision gremlins. But if they don't, at least we'll get a few more clips of tanks being launched into orbit.