Same cm/360, Different Aim Feel? Check FOV and Zoom

A converter can return the correct rotational match while the destination game still feels unfamiliar. The apparent contradiction disappears when you separate two measurements: how far the camera turns and how far an object appears to move across your screen.

What cm/360 preserves

If two linear, non-accelerated configurations both measure 40 cm/360, a 20 cm movement corresponds to a 180-degree horizontal turn in each. That is a useful shared reference.

It says nothing by itself about the size of a target on the display, the speed of a character or the mouse movement needed to reach a particular screen position while zoomed. Treat it as a rotational baseline, not a promise of identical aim.

Start with the DCPROSENS converter, then verify a physical turn inside both games. Game-specific scaling and input modes still need to be correct.

FOV changes the visual context

Field of view determines how much of the scene the camera shows. EA's Apex Legends settings guidance explicitly notes that increasing FOV reveals more surroundings while making distant objects appear smaller.

Different games can label their FOV controls differently. One may use a horizontal angle, another a vertical angle or a value referenced to a particular aspect ratio. Two sliders displaying “90” are therefore not automatically equivalent.

For a standard rectilinear perspective camera, the relationship is:

horizontal FOV = 2 × atan(tan(vertical FOV / 2) × aspect ratio)

Use consistent angular units when calculating. At 16:9, a vertical FOV of 60 degrees corresponds to approximately 91.49 degrees horizontally. This is a geometry example, not a claim about a particular game's slider.

The DCPROSENS FOV converter is a useful place to organize that comparison. Confirm the game's actual convention before interpreting its output.

Compare these settings in order

Do not change all five at once. If your measured turn does not match, fix the input conversion first. If it does match, investigate presentation and zoom before recalculating the sensitivity again.

A simple two-task comparison

Choose two tasks in each game: a broad turn to a landmark and a small correction near the center of the screen. Keep your normal posture and use the same mouse and pad.

Write down which task feels wrong. “Broad turns match, but small ADS corrections feel too fast” is a useful observation. “The converter is broken” is not specific enough to guide the next test.

For the first case, keep the hip-fire baseline and investigate ADS sensitivity matching. If broad turns also fail to match, check DPI, active profiles and input acceleration.

What should you prioritize?

Choose a matching goal based on the task you care about. Preserving rotational travel is convenient for turning. A screen-distance approach can be useful when comparing corrections at a particular point in the view. Neither creates a universal match for every zoom level and every target position.

You can also prefer different sensitivities in different games. A shared baseline helps you start systematically; it is not a rule requiring every game to feel identical.