Quake Champions

[slime]

6 minutes ago, DPI Wizard said:

Yes, 360 distance only works well when the FOVs is very close to each other. The best way to illustrate this is matching 360 distance between hipfire and a sniper scope, it wouldn't work. But if you match something like CSGO hipfire with Overwatch hipfire, 360 distance would work quite well.

Thank you for the insight. This is a great service you guys have here especially with the customer support. 

[danilo106]

Anyone can help me? i have on Black Ops III   1600 dpi , 0.85 in game and 0.018 vertical sens, how i can covert it to quake champions? i am playing all games at 1600x900  res

ive tryed the calculator but in game dosn't look same!

thanks

 

 

Edited October 26, 2017 by danilo106

[DPI Wizard]

4 hours ago, danilo106 said:

Anyone can help me? i have on Black Ops III   1600 dpi , 0.85 in game and 0.018 vertical sens, how i can covert it to quake champions? i am playing all games at 1600x900  res

ive tryed the calculator but in game dosn't look same!

thanks

Have they changed the settings in game? I'll check later today if so!

[danilo106]

Thanks you, anyway i am using this :

 

1600x900 resolution  in game and on windows

Windows sensitivity:  6/11 with accell on

Mouse Sensitivity: 1600 DPI (Logitech G402)

in game sens: 0.85 and vertical 0.018 (Call of Duty:Black Ops III) 100 FOV

my monitor: BenQ xl2411  24' 144hz

«if you can help me to get same sensitivity on Quake Champions will be awesone!♥

config.ini  <-- Bo3

Quake Champion settings

Edited October 27, 2017 by danilo106
Adding CoD:BO3 Config

[danilo106]

On 27/10/2017 at 11:40 AM, danilo106 said:

Thanks you, anyway i am using this :

 

1600x900 resolution  in game and on windows

Windows sensitivity:  6/11 with accell on

Mouse Sensitivity: 1600 DPI (Logitech G402)

in game sens: 0.85 and vertical 0.018 (Call of Duty:Black Ops III) 100 FOV

my monitor: BenQ xl2411  24' 144hz

«if you can help me to get same sensitivity on Quake Champions will be awesone!♥

config.ini  <-- Bo3

Quake Champion settings

 

[BlackSilv3r]

@DPI Wizard What is the FOV on zoom with rail gun? Could you guys add that to the calculator? Couse i have amazing sensitivity on zoom with rail gun and would like to transfer that to other games (I think the zoom FOV is the same for all guns and it's not influenced by hipfire FOV).

Edited April 22, 2018 by BlackSilv3r

[stereo3D]

https://www.reddit.com/r/QuakeChampions/comments/8fo9as/quake_champions_zoom_fov_and_sensitivity/

zoomFOV is 79 and scales with vertical FOV.

[BlackSilv3r]

@stereo3D Thanks for letting me know

[Drimzi]

If the sensitivity is scaling with vertical fov, then use vertical monitor match to replicate it. The monitor match percentage required to accomplish this is equal to: resolution height / resolution width * 100. e.g. 1080/1920 * 100 = 56.25 %

[MattKelly]

.

Edited October 10, 2018 by MattKelly

[DPI Wizard]

1 hour ago, MattKelly said:

Quake Champions got an update today that added zoom sensitivity finally. Any chance that might be added to the calculator in the near future? @DPI Wizard

Thanks in advance!

I think they may have messed something up when they added it. Regardless of configured FOV the zoom is 79, and currently it scales like this (configured FOV on the bottom, counts on the left), which makes no sense:

It should either be a straight line or a nice arc. 

[Drimzi]

It was vertical angle ratio before this patch.

[MattKelly]

.

Edited October 10, 2018 by MattKelly

[Drimzi]

You can manually find your zoom sensitivity.

 

Counts for 360° - Hipfire:

360/(Sensitivity * Yaw)

Counts for 360° - Zoom:

360/(Sensitivity * Yaw) * (tan(HipfireHFOV * pi/360) / tan(79 * pi/360))

 

A Logitech Gaming Software script to find your zoom sensitivity (click scroll wheel or press G1/F1:

function OnEvent(event, arg)
    Sensitivity = 1
    Yaw = 0.022
    HipfireHFOV = 120
    Counts = 360/(Sensitivity * Yaw) * (math.tan(HipfireHFOV * math.pi/360) / math.tan(79 * math.pi/360))
    Payload = 100

    if ((event == 'G_PRESSED' and arg == 1) or (event == 'MOUSE_BUTTON_PRESSED' and arg == 3)) and GetMKeyState() == 1 then
      for i = 1, Counts / Payload do
        MoveMouseRelative(Payload,0)
        Sleep(10)
      end
    end
end

 

It should send the correct number of counts (minus rounding) to perform a 360° for 79 HFOV based on your sensitivity and hipfire FOV. Tune the zoom sensitivity value until it rotates a perfect 360°.

[Drimzi]

I tested with with vertical angle ratio, 120 to 79 gives me 0.846643 zoom sensitivity, which works but overshoots by the *tiniest* amount (doesn't really matter). Probably because the games also rounding to 3 decimals (with a lot of extra numbers at the end) for me, despite using the config, and the bug that DPI Wizard is observing.

I put in 0.58735264, it changes to this.

{
   "Input": {
      "mouseRotateSensitivityCoef": 0.58700001239776611,
      "mouseZoomRotateSensitivityCoef": 0.84700000286102295
   },
   "cfg_version": 1
}

 

 

Edited August 3, 2018 by Drimzi

[DPI Wizard]

1 hour ago, Drimzi said:

I tested with with vertical angle ratio, 120 to 79 gives me 0.846643 zoom sensitivity, which works but overshoots by the *tiniest* amount (doesn't really matter). Probably because the games also rounding to 3 decimals (with a lot of extra numbers at the end) for me, despite using the config, and the bug that DPI Wizard is observing.

I put in 0.58735264, it changes to this.

{
   "Input": {
      "mouseRotateSensitivityCoef": 0.58700001239776611,
      "mouseZoomRotateSensitivityCoef": 0.84700000286102295
   },
   "cfg_version": 1
}

 

0.84519987 will make it perfect for that one instance. But since the scaling is not consistent at the moment it's impossible to add it to the calculator.

It mostly close to a 60% monitor match, but is completely off at lower FOV's. I'll do some more measurements and double check the settings in the config file as I only went off the in-game settings initially.

[stereo3D]

what's 100 % at FOV 120, please?

[DPI Wizard]

2 minutes ago, stereo3D said:

what's 100 % at FOV 120, please?

Should be 0.855339, but I can't verify it until later today.

[stereo3D]

shouldn't it be above 1 if default is 60 %? i just set it to 1.2 for the time being.

[DPI Wizard]

1 minute ago, stereo3D said:

shouldn't it be above 1 if default is 60 %? i just set it to 1.2 for the time being.

I divided the wrong way  1.169127

[stereo3D]

ah, that should be right, thanks!

[DPI Wizard]

If it feels correct it probably is, but I'll verify it later.

[stereo3D]

since there is only one zoomFOV the devs should simply disable the internal sensitivity scaling.

[DPI Wizard]

Just now, stereo3D said:

since there is only one zoomFOV the devs should simply disable the internal sensitivity scaling.

Yeah, it's really illogical that the hipfire sensitivity is unaffected by FOV change while the zoom is affected by it even though it has a static FOV...

[DPI Wizard]

I've added the zoom sensitivity with the inaccuracy as a sidenote. It is within 2% accurate above FOV 106. Hopefully the devs will fix it soon.

I analyzed every FOV step between 100 and 140 to get all the data, the blue line is the actual 360 distance, the orange line is the calculated 360 distance.