Tom Clancy's Rainbow Six Siege

In my test, the ACOG in r6s is a 3x to 3.5x scoping sight

good job ubi

6 hours ago, samuel_hou said:

In my test, the ACOG in r6s is a 3x to 3.5x scoping sight

good job ubi

It depends on your FOV but more or less yeah. 3.1x at 60 FOV and 3.5x at 90 FOV.

Exact zoom ratio is given by http://www.wolframalpha.com/input/?i=tan(90°%2F2)%2Ftan(90°%2F2*0.35)

On 1/21/2018 at 11:13 AM, Inakyo said:

Is it possible to preserve viewspeed between ACOG and iron sights?

4 分钟前, Skwuruhl说:

It depends on your FOV but more or less yeah. 3.1x at 60 FOV and 3.5x at 90 FOV.

Exact zoom ratio is given by http://www.wolframalpha.com/input/?i=tan(90°%2F2)%2Ftan(90°%2F2*0.35)

Cooooooool！

But i just wondering why they use this strange value? just because the 0.35x acog sensitivity for default(50)?

====================

and could i use your formula on other website (of course with your id and no profit）？thx

7 minutes ago, samuel_hou said:

Cooooooool！

But i just wondering why they use this strange value? just because the 0.35x acog sensitivity for default(50)?

====================

and could i use your formula on other website (of course with your id and no profit）？thx

ACOG just multiplies your FOV by 0.35. Zoom doesn't scale linearly with FOV so this doesn't work out to be a static zoom amount of 2.86x.

It's not my equation (or anybody's), it's just how zoom scales when using rectilinear projection (how games "paint" the scene).

After using the mouse calc, whenever I ADS, my sensitivity feels as if it is "anchored" or very, very slow. Has anyone had this issue before using this mouse-sens calc? Even if I set my controls to default, ADS is abnormally slow. 

Lol. Simple mode converts using 360 distance. If that's too slow while ADS, then I don't know what to tell you tbh. The result must be incredibly wrong or something.

17 hours ago, DPI Wizard said:

It's using Monitor Distance 75% (when you switch between simple and advanced the conversion method is not changed). The issue is that Simple Mode uses default values for sens 2 and multiplier 1, so it will not work with calculations such as iron sight or ACOG for R6 config file. 

You have to use either Advanced Mode or in-game for this to work.

In-game (meaning MouseSensitivityMultiplierUnit and XFactorAiming must be set to 0.02):

Advanced:

Thank you for clearing this up for me DPIWizard! 

Pretty insane with the amount of popularity this game gets they haven't fixed the zoom scaling. Like would it be that hard Ubi? What is even the current best action without using some type of macro? Just match the ironsight and let the ACOG be what it is?

So after Chimera update my mouse sensitivity has changed slightly. before it was a 12.7cm/360 in white noise, now its like 13.1cm/360. is there any adjustment will be made to the calculator?

and yeah i saw the post of DPI wizard when he tested it in TTS but didn't notice any difference, but it could be because I changed the x-factor, and the multiplayer-unit?

BTW that was my hip fire sens

On 3/7/2018 at 10:04 AM, infamous50c said:

So after Chimera update my mouse sensitivity has changed slightly. before it was a 12.7cm/360 in white noise, now its like 13.1cm/360. is there any adjustment will be made to the calculator?

and yeah i saw the post of DPI wizard when he tested it in TTS but didn't notice any difference, but it could be because I changed the x-factor, and the multiplayer-unit?

BTW that was my hip fire sens

Yeah, a couple of the pros said sens has changed with the latest update (the one in production not TTS). Would be nice if you could run a check on it. TIA.

11 hours ago, OrangeGuac said:

Yeah, a couple of the pros said sens has changed with the latest update (the one in production not TTS). Would be nice if you could run a check on it. TIA.

Problem is a lot of the pros don't really understand how sensitivity works. They all preach the "83" ingame value to get the same sensitivity without realising that fov changes also impact the sensitivity. Same goes for raw input, sens hasn't changed but the response time is snappier which feels weird on a brain that is used to slight input delay.

just tested out different FOVs and with raw input on and off and all of them approximately end up at the same point. So no I don't think the update changed the FOV relation to the sensitivity for this game.

4 hours ago, jabbothehut said:

Problem is a lot of the pros don't really understand how sensitivity works. They all preach the "83" ingame value to get the same sensitivity without realising that fov changes also impact the sensitivity. Same goes for raw input, sens hasn't changed but the response time is snappier which feels weird on a brain that is used to slight input delay.

just tested out different FOVs and with raw input on and off and all of them approximately end up at the same point. So no I don't think the update changed the FOV relation to the sensitivity for this game.

4 hours ago, infamous50c said:

just tested out different FOVs and with raw input on and off and all of them approximately end up at the same point. So no I don't think the update changed the FOV relation to the sensitivity for this game.

Appreciate the comments and work but wouldn't you need to test sensitivity pre vs post patch? 

When I try to convert my CS:GO sensitivity to Rainbow Six Siege it asks me for a sensitivity in Rainbow Six Siege. What should I put in Here?

does Glaz's scope =acog?

also,

does iron sight = reflex and holo in the calculator?

When will holo sights be added to the calculator?

irons are the same as holo, rds, and reflex

If I run 4:3 aspect ratio in Siege should I change the resolution to something like 1280x960 in the calculator? Since you get a lower FOV at 4:3 compared to native 16:9 you've gotta get different results when calculating

22 minutes ago, DPI Wizard said:

Is it stretched to fit 16:9, 4:3 with black bars or an actual 4:3 monitor?

It's stretched on a 16:9 monitor. I'm assuming black bars is equal to 16:9