Two doors. Play with Task Force Drip.Prove it on Drip League.
DISPATCH 2026.10 / INTEL CONFIDENCE: CONFIRMED

Some enemy models are stuck in the wrong animation.

Call of Duty's official updates account said on the night multiplayer went live worldwide that Infinity Ward is aware of a Modern Warfare 4 issue where some player models render in static or incorrect animations, and that this can make enemy players appear in unintended states. No fix has shipped.

Confirmedmw4multiplayerknown issuesvisibility

Modern Warfare 4 multiplayer opened worldwide on October 23. Just under twelve hours later, the official Call of Duty Updates account posted that the team is aware of an issue causing some player models to appear in static or incorrect animations, and that this may result in enemy players appearing in unintended states. It is logged on the public live issues board that Infinity Ward pointed players to in the launch patch notes. It is not a cosmetic note buried in a changelog. It is the studio saying the thing you are shooting at may not be showing you what it is actually doing.

Confidence

Confirmed, and narrowly so. This is the official Call of Duty Updates account, the channel Infinity Ward's own launch patch notes names for known issues, describing a problem in its own game at 23:34 UTC on October 23. What is confirmed is that the issue exists and is being tracked. How often it happens, what causes it, and what it does to a gunfight are stated nowhere official.

What Call of Duty actually said

The post is two sentences long and it is worth reading exactly. First, some player models appear in static or incorrect animations. Second, this may result in enemy players appearing in unintended states. That is the whole official statement. There is no platform named, no mode named, no map named, no frequency given, and no fix date. A separate post the same evening temporarily disabled the regional map animation in the lobby search screen as a prospective fix for hitching reports on Xbox, which tells you the team was working live issues that night, not that the two are connected.

Why Hardcore SnD cares

Hardcore Search and Destroy is a reading game before it is a shooting game. You do not get a second body, so most of a round is spent deciding whether the shape at the end of a hallway is worth your life. Almost all of that decision is animation: is he planting, is he reloading, is he already peeking you, is he even alive. An animation layer that can go static or wrong attacks the one input you cannot play without.

  • Target ID a model held in a stale pose reads as a static enemy holding an angle when he may already be somewhere else.
  • Post-plant the defuse animation is the clock. A wrong or frozen animation on the bomb is a retake called on bad information.
  • Trade timing entry trades are timed off a teammate's and an enemy's visible actions. Desynced animation makes a clean trade look late and a late one look clean.
  • Review if you cannot trust the model state live, you cannot fully trust what you are watching back when a round gets argued about.

The honest caveat is that none of that is Infinity Ward's claim. The studio said models can appear in unintended states. Everything above is what an unintended state costs a one-life team, and it only costs that much if the bug is common. It may well be rare. Play as though it is rare and verify your reads with sound and with your teammates, because right now sound is the input that is not in question.

In a mode with no respawn, a wrong animation is not a visual glitch. It is bad intel delivered at the worst moment.

What is not confirmed

Whether this is widespread or a handful of edge cases. Whether it is tied to one platform, to high ping, to a specific killstreak or field upgrade, or to the same stability work the October 23 update was already chasing. Whether it can be triggered deliberately, which matters a great deal in a competitive lobby and which no official source has addressed in either direction. And when it gets fixed: Infinity Ward said more updates are coming over the following days and that multiplayer patch notes are still to come, but this issue was not in the October 23 notes.

If you see it

Record it. A clip with a visible scoreboard and a timestamp is worth more to a bug report, and to your own team's argument about a lost round, than a description after the fact.

Sources to review

your move

Trust your ears this week

Until this one is patched, treat a still enemy model as unverified and let audio break the tie. Then go take the round anyway.