Marvel Rivals Addresses 30 FPS Glitch Issue

Summary

• Lower FPS settings in Marvel Rivals are causing damage issues for some heroes like Dr. Strange and Wolverine.
• Developers are actively working to fix the 30 FPS bug affecting damage calculation in the game.
• The Season 1 launch is expected on January 11 and may address the FPS issue, improving the gameplay experience.

The Marvel Rivals development team has confirmed an issue where players using lower FPS settings may experience reduced damage output compared to those on higher-end devices. They are diligently working on a solution, which is expected to be implemented soon.

Since its launch in early December 2025, Marvel Rivals has quickly become a favorite in the hero shooter genre. Despite initial concerns about hero balance, the game has garnered an impressive 80 percent player approval rating from over 132,000 reviews on Steam.

Recently, players have reported a glitch at 30 FPS that affects certain heroes such as Dr. Strange, Magik, Star-Lord, Venom, and Wolverine, causing them to deal less damage at lower frame rates. A confirmation from a community manager on the official Marvel Rivals Discord server highlighted that this glitch also impacts hero movement at lower frame rates, extending to damage output. While a fix "may take some time," Community Manager James reassured players that the upcoming Season 1 update, set for January 11, will address this issue.

Marvel Rivals is Fixing the 30 FPS Damage Bug

The root of the problem lies in the game's client-side prediction mechanism, a programming feature designed to reduce perceived lag by moving characters onscreen before the server processes player input.

Although the community manager's post did not list all affected heroes or moves, it specifically mentioned Wolverine's Feral Leap and Savage Claw abilities. The impact is more evident when testing against stationary targets, though it can be harder to notice during actual gameplay. If the Season 1 launch does not fully resolve the FPS damage issue, a future update is expected to correct it completely.