Hero Shooter · PC GUIDE
Marvel Rivals
Settings & responsiveness.
Marvel Rivals supports Reflex and DLSS features on compatible hardware. Compare base rendering performance separately from frame generation so your FPS readings remain meaningful.
Updated · InputLag editorial · English
YOUR MANUAL CHECKLIST
Settings to review.
These are starting points, not a universal best config. Apply changes in the game, compare the result, and mark what you’ve reviewed. Availability can vary by hardware and patch.
4 settings shown
- Enabled, on supported NVIDIA GPUs
Use the in-game latency option where available. Compare Boost separately; benefits and power use depend on your system.
- Off for the baseline measurement
Then compare it separately for smoothness and input feel. Generated frames are not the same measurement as base rendered FPS.
- Compare a supported quality mode with native
Available on compatible hardware. Keep the output resolution fixed and compare detail and frame pacing.
- Compare a lower preset in the same fight
Test effects-heavy scenes; quiet areas can hide performance dips.
Make the comparison useful.
Record which technologies are active
Note upscaling and frame generation with each result. Do not compare a generated-FPS run to a native-rendering run as though the workload were identical.
Change one thing at a time
Keep your resolution, map and test route consistent. Compare several runs and record frame-time spikes as well as average FPS.
Keep a baseline
Save your current settings before changing them. Keep changes that improve your own measurements; a higher peak FPS alone does not mean steadier play.
A SEPARATE BROWSER CHECK
How to read your browser score.
The Responsiveness Lab gives a browser-based score. It does not measure this game’s click-to-photon latency, inspect Windows settings, or predict your rank. Use repeated runs to compare browser test conditions.
Run a browser test ↗See game benchmark methodology ↗
A high result in this browser session. Compare repeat runs under the same conditions.
A solid browser result. Check the individual test results for variation.
Review the individual tests and repeat with background load reduced.
Repeat the test and check browser, display and background activity before drawing conclusions.
Sources & review notes
Official references below support the documented features. The comparison steps are editorial starting points, not measured performance guarantees. No lab benchmark was performed for this guide.
How InputLag handles supported changes →