Marvel Rivals FPS Hatası Geliştiriciler Tarafından Ele Alındı

Yazar : Aaliyah Jan 18,2025

Marvel Rivals FPS Hatası Geliştiriciler Tarafından Ele Alındı

Marvel Rivals Addresses 30 FPS Damage Glitch Affecting Several Heroes

Players of Marvel Rivals experiencing reduced damage output at lower FPS settings, particularly with heroes like Dr. Strange and Wolverine, can breathe a sigh of relief. The developers have acknowledged a 30 FPS bug impacting damage calculations for certain characters and are actively working on a solution.

Released in early December 2025, Marvel Rivals quickly gained popularity in the hero shooter genre, boasting an impressive 80% player approval rating on Steam (over 132,000 reviews). Despite initial hero balance concerns, the game has largely been well-received.

Recent reports highlighted a significant glitch affecting damage dealt by heroes like Dr. Strange, Magik, Star-Lord, Venom, and Wolverine at 30 FPS. Community feedback indicated reduced damage on some or all of their attacks at lower frame rates. A community manager on the official Discord server confirmed the issue, noting movement problems at lower FPS settings that also affect damage output.

While a precise fix date isn't available, the community manager, James, assured players that the upcoming Season 1 update (launching January 11th) will address the problem. A complete resolution may require a subsequent update if Season 1 doesn't fully resolve the issue.

The Root of the Problem: Client-Side Prediction

The root cause appears to be linked to the game's client-side prediction mechanism, a common programming technique used to minimize perceived lag. This mechanism, however, seems to be the source of the damage calculation discrepancies at lower frame rates.

Although the official statement didn't provide an exhaustive list of affected heroes and abilities, Wolverine's Feral Leap and Savage Claw were specifically mentioned. The effects are more pronounced against stationary targets than in live matches. Regardless of the Season 1 update's success, developers are committed to resolving this issue completely in a future patch.