Set a frame-rate target your PC can hold

A fluctuating high frame rate can feel worse than a slightly lower but stable limit. Test in a demanding battle royale scene, not only the firing range. Watch the one-percent lows and frame-time graph if your monitoring tool provides them. The correct cap leaves a little headroom during effects-heavy fights.

Use your display’s native refresh rate and confirm the operating system is actually outputting it. Full-screen behavior, variable refresh rate, and a frame limiter can interact differently by system, so validate with your own frame-time result rather than a universal claim.

  • Native resolution unless GPU load makes it unstable
  • Low or disabled expensive effects before reducing texture clarity
  • A cap that remains stable during smoke, ultimates, and dense POIs
  • No background capture or overlay you do not actively use

Prioritize enemy readability

Competitive visibility means preserving silhouettes and motion while removing visual noise. Keep texture streaming within your available VRAM; setting it too high can create stutter, while setting it unnecessarily low can make distant scenes harder to parse. Shadows and volumetric effects are common places to recover performance, but every patch can change the cost.

Field of view is a trade-off. A wider view provides more peripheral information but makes distant targets appear smaller. Test it at the ranges where you miss most often and avoid changing it at the same time as sensitivity.

Mouse: preserve cm/360 across tests

Disable operating-system pointer acceleration for a consistent baseline and keep the same DPI while comparing in-game sensitivity. Record your effective DPI and cm/360. The 2PVP sensitivity converter can move a baseline between compatible games, but ADS scopes and FOV behavior still need an in-game check.

A lower sensitivity is not automatically more competitive. You need enough control for recoil and enough range for close tracking, movement, and rapid target changes. Test with the same drill and score the same behavior across several days.

Controller: tune response before aim assist debates

Use the smallest deadzone that does not produce drift. Response curve changes how quickly input builds, so compare it with the same weapon and range. Advanced Look Controls give more precision but also more variables; if you cannot describe the problem each slider solves, begin with a standard response preset.

Retest after firmware, controller, and major game updates. A setup is a measured baseline, not a permanent truth.

A clean testing protocol

Change one category at a time, capture the result, and keep a rollback value. Ten minutes of structured comparison is more useful than an evening of continuous tweaking.

  • Record current values before changing anything
  • Use one repeatable recoil and tracking drill
  • Test a real match for visibility and frame pacing
  • Keep the winner for three sessions before another change
Quick answers

Frequently asked questions

What FOV is best for Apex Legends?+

There is no universal best value. Higher FOV adds peripheral information but reduces apparent target size; compare values at your real engagement distance without changing sensitivity simultaneously.

Should I use uncapped FPS?+

Only if your system delivers stable frame times and your display/input setup benefits. A sustainable cap often feels cleaner during heavy fights.

How do I copy a pro sensitivity?+

Use it as a starting point, convert with DPI included, and validate your own cm/360. Hardware, grip, role, and FOV make exact copying unreliable.

Built to stay useful

This guide separates durable fundamentals from details that can change with patches, seasons or tournament rules. Recheck current schedules and in-game rules when timing matters.

How 2PVP reviews guides →