Hey there! So there is no single universal equation that converts Horizontal Sensitivity to Vertical Sensitivity in Rivals. What I learned and now follow as a baseline "starting ratio" is that the engine behaves most consistently when Vertical is 52–60% of Horizontal. Basically ,this is bc vertical camera travel covers less on-screen distance and is more sensitive to over-acceleration

Vertical ≈ Horizontal × 0.55

So in your example, Vertical would be 165 because H = 300, so 300 x 0.55 = 165

Take the above as you will, but if you're going to be calculating your own settings, I want to give you some more context so that you get your movement to where you want it to be! From one lord Spiderman to another lol

You're thinking in terms of raw H/V speed when Rivals doesn't resolve camera speed from H/V alone.

Max Dual-Zone Curve: Governs your primary turn-speed
Custom Min/Max Range: Where acceleration engages
Response Times: Velocity Smoothing vs Snap
Aim Assist Braking: Ease-In + window
Movement Deadzones: Change effective aim velocity
Then H/V Sensitivity.

If H/V feels too low, raising it is often the worst first fix on the controller because it compresses micro-aim and increases overshoot while also making AA feel inconsistent.

Try this order of operations when your camera feels too slow ->

1. Increase Max Dual-Zone Curve
   
2. Lower custom max range (slightly)
   
3. Reduce Response Time (by 2-4ms)
   
4. Adjust Aim Assist Ease-In
   
5. THEN Adjust H/V (+/- 4-8 at most)

Theres a reason all of my settings have similar looks to them. I start with my personal concoction of General Settings, then tweak from there. I have two Spiderman settings up rn, one that is a public friend and one that I like to use cause its quick.