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 that an issue is affecting players on lower FPS settings, resulting in reduced damage output for certain heroes compared to those using higher-end devices. They are diligently working to resolve this problem, with a potential fix expected within days.
Since its launch in early December 2025, Marvel Rivals has quickly become a standout in the hero shooter genre. Despite initial concerns about hero balance, the game has garnered an impressive 80 percent player approval rate from over 132,000 reviews on Steam.
Recently, players have reported a glitch at 30 FPS that causes select heroes, including Dr. Strange, Magik, Star-Lord, Venom, and Wolverine, to deal less damage than at higher frame rates. This issue has been confirmed by a community manager on the Marvel Rivals official Discord server, who noted that some heroes experience movement issues at lower frame rates, impacting their attack damage. While a complete fix might take some time, Community Manager James has assured fans that the upcoming Season 1, set to launch on January 11, will address this glitch to some extent.
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 technique designed to reduce perceived lag by moving characters onscreen before the server processes player input.
Although the community manager's post did not provide a full list of affected heroes or moves, it specifically mentioned Wolverine's Feral Leap and Savage Claw abilities. These effects are more noticeable when tested against stationary targets, though they can be harder to detect during actual gameplay. If the Season 1 launch does not fully resolve the FPS damage issue, a future update is expected to address it completely.
