I have Overwatch FoV configured to 100 in game, and Quake Live FoV also configured to 100 in game. I'm using Viewspeed V2. Where I'm currently confused is:

Do I want to type 100 for FoV in the calculator for Quake Live, or do I want to lower the in-game FoV until I have an "Actual HFoV" of 100 to match the 100 FoV that Overwatch is using?

Is the goal to try to unify the in-game FoV with the "actual FoV", or does Viewspeed render this point moot?

Here as an image of what I have been doing, I don't know if it's "correct", though, given the FoV discrepancies...

 

If you select the same FOV Type for Quake Live as Overwatch uses (Hdeg Res) and enter the value from Overwatch (100), the output will show you the FOV you need to configure in Quake Live to get the exact same FOV (set cg_fov "83.58")

That's cool, and something I hadn't considered! Thank you :). I suppose now the question is:

Is that necessary when using Viewspeed? I only ask because some games have rigid FoVs (Like CS:GO), and it might be a lot of work to unify sensitivities around a handful of games that don't allow you to easily alter their FoVs (Without sv_cheats, for example).

And is there anything special I should be paying attention to when it comes to Zoom?

 

If you can match the FOV, it doesn't matter which conversion method you use as they all will give you the same result. Matching FOV is the best way to keep a consistent sensitivity.

When FOV can't be matched use Viewspeed indeed.

For Zoom remember to set Sensitivity 2 to your cg_zoomfov value, and enter the regular FOV into the FOV field.

14 hours ago, DPI Wizard said:

If you can match the FOV, it doesn't matter which conversion method you use as they all will give you the same result. Matching FOV is the best way to keep a consistent sensitivity.

When FOV can't be matched use Viewspeed indeed.

For Zoom remember to set Sensitivity 2 to your cg_zoomfov value, and enter the regular FOV into the FOV field.

The instructions on the calculator have those inputs reverse from what you're suggesting, and it recommends typing the zoomfov in the FOV field, and regular FOV in the Sensitivity 2 field, am I messing up, somewhere?

3 hours ago, Grumple871 said:

The instructions on the calculator have those inputs reverse from what you're suggesting, and it recommends typing the zoomfov in the FOV field, and regular FOV in the Sensitivity 2 field, am I messing up, somewhere?

You are correct, the variable values must be switched. I'll double check later.

25 minutes ago, DPI Wizard said:

You are correct, the variable values must be switched. I'll double check later.

Thank you! Please update when you find out more! I really appreciate your help 😀 !

The way explained in the notes is the correct one, and it's done so the FOV is processed correctly. But it is a bit opposite of what it should be, so I'll see if it's possible to change.

1 hour ago, Grumple871 said:

Thank you! Please update when you find out more! I really appreciate your help 😀 !

I switched it around now so it's more logical. The FOV field is now your regular FOV, and the Sensitivity 2 is the zoom FOV

10 hours ago, DPI Wizard said:

I switched it around now so it's more logical. The FOV field is now your regular FOV, and the Sensitivity 2 is the zoom FOV

Thank you for clearing that up 😄 !