Ev >  Haberler >  Marvel Rivals 30 FPS Hatasını Ortadan Kaldırdı

Marvel Rivals 30 FPS Hatasını Ortadan Kaldırdı

Authore: HarperGüncelleme:Jan 22,2025

Marvel Rivals 30 FPS Hatasını Ortadan Kaldırdı

Marvel Rivals Addresses Low FPS Damage Issue

Several Marvel Rivals heroes, including Dr. Strange and Wolverine, are experiencing reduced damage output at lower FPS settings. This 30 FPS bug, affecting damage calculations, is currently under active development by the game's creators.

The issue is expected to be addressed, at least partially, with the launch of Season 1 on January 11th. This update aims to improve the overall gameplay experience for players on lower-end hardware.

Launched in early December 2025, Marvel Rivals quickly gained popularity in the hero shooter genre. Despite initial concerns about hero balance, the game boasts an impressive 80% player approval rating based on over 132,000 Steam reviews.

Recent reports highlight a significant glitch impacting damage dealt by certain heroes (Dr. Strange, Magik, Star-Lord, Venom, and Wolverine) at 30 FPS. This damage reduction is more apparent against stationary targets. A community manager confirmed the problem on the official Discord server, acknowledging movement and damage inconsistencies at lower frame rates. While a complete fix might take time, the Season 1 update is slated to offer a solution, with further improvements planned if necessary.

The 30 FPS Damage Bug: A Closer Look

The root of the problem appears to be the client-side prediction mechanism, a common programming technique to minimize perceived lag. This mechanism, in Marvel Rivals, seems to be the source of the damage discrepancies at lower FPS.

While the official statement didn't list all affected heroes or abilities, Wolverine's Feral Leap and Savage Claw were specifically mentioned. The developers are committed to resolving this issue, ensuring a fair and balanced gameplay experience for all players regardless of their FPS settings. If Season 1 doesn't fully eradicate the problem, a subsequent update will address any remaining inconsistencies.