Escape from Tarkov

[DPI Wizard]

Just added!

View full update

[Traxilla]

You might want to wait a lil bit, some of the ironsights, which all have the same FOV doesn't have the same ADS sens. i've been trying to get discussions going in the forums on it, but it doesn't seem like people even notice the problem.

[lagarto]

True, another annoying thing, is the decrease of sens of the armors, now its impossible to have a 1:1 sens with 1 config file

[Traxilla]

Last i tested it, the sensitivity didn't change with armor, i just went in the other day to test if the sensitivities are still off with the different ironsights, which they are. But i don't think they implemented armor changing sens...

If that gets implemented i'm not gonna play the game.

Edited July 14, 2017 by Traxilla

[lagarto]

9 minutes ago, Traxilla said:

Last i tested it, the sensitivity didn't change with armor, i just went in the other day to test if the sensitivities are still off with the different ironsights, which they are. But i don't think they implemented armor changing sens...

If that gets implemented i'm not gonna play the game.

I know, is bad, but is the truth, you can see this in http://escapefromtarkov.gamepedia.com/Armor  ,this penalty only work for hip sens, there is a post about this http://forum.escapefromtarkov.com/topic/14825-armour-turning-speed-ie-mouse-sens/

[Traxilla]

Fuckin hell, i even wrote in that post. One thing i hate is the people that use the "Realism" excuse for mouse mechanics... It's ridiculous

 

[lagarto]

Is there a way to to convert monitor distance from a weapon to another ?, the aim sens is killing me

[PolygonPrime]

Wow these calculations are waaaay off..  If I actually set the suggested sensitivity from the screenshot below, my character just starts spinning wildly when i move the mouse an inch.

[lagarto]

6 hours ago, PolygonPrime said:

Wow these calculations are waaaay off..  If I actually set the suggested sensitivity from the screenshot below, my character just starts spinning wildly when i move the mouse an inch.

the aim sens calculator dont work

[DPI Wizard]

They probably changed something as this game is in development. Is the closed beta ongoing now, so I get immediate access if I buy the game?

[lagarto]

15 minutes ago, DPI Wizard said:

They probably changed something as this game is in development. Is the closed beta ongoing now, so I get immediate access if I buy the game?

I tried when you posted and dont work

Yes, now you get instant acces, i can give you my account for that (45 U$S are too much)

 

[DPI Wizard]

Actually it was a small typo here, the aiming sensitivity is the 

"MouseAimingSensitivity":

value in the config file, not the 

"MouseSensitivity":

one. Try again with the correct value

[lagarto]

1 minute ago, DPI Wizard said:

Actually it was a small typo here, the aiming sensitivity is the 

"MouseAimingSensitivity":

value in the config file, not the 

"MouseSensitivity":

one. Try again with the correct value

I dont use the confige file, because i need differents config for every weapon and armor, for example

Hip-Fire: 0.21, with paca 0.23 and 0.27 for armor + helmet

Ads: 0.17, if the weapon got RDS 0.22

in my case the calculator suggest 0.51 for ads, im use the convert in monitor distance

[DPI Wizard]

1 minute ago, lagarto said:

I dont use the confige file, because i need differents config for every weapon and armor, for example

Hip-Fire: 0.21, with paca 0.23 and 0.27 for armor + helmet

Ads: 0.17, if the weapon got RDS 0.22

in my case the calculator suggest 0.51 for ads, im use the convert in monitor distance

Ok, it needs updating then.

[PolygonPrime]

I've also notices i need to set different sensitivity's with different guns. It constantly changes. It even changes when adding a red dot scope to an AK. When an RDS is attached a 360 degree rotation takes twice as much mouse movement.

I've already sent battelstate games a bug request although om not sure it actually is a bug.

[DPI Wizard]

Updated the aiming now, adjusted it for iron sights.

[consis]

Hi! I try to convert from Overwatch to Escape from Tarkov and it says "Aiming" to be almost twice as high as "hipfire", which should be the opposite if I'm not mistaken? Also the realtion between the two feels off, even though I swap the two. Is adjustment possible? Regards

[lagarto]

Yes, try convert monitor distance, if you use 75 fov, in the aim fov put 50

[consis]

Thanks for reply! I must admit I'm a bit confused. When I roughly compare to the 360 distance on my mousemat, it seems that "hipfire" from 360 distance conversion is right (0.26), but not "aiming iron sight" (0.41). Instead for "aiming iron sight", conversion to monitor distance for "hipfire" feels most on point (0.18), not "aiming iron sight" (0.11). I use default 50 FOV, mouse at 800 dpi.

For Overwatch I use default FOV, sensitivity 5 at 800 dpi, or rather 2.5 sensitivity at 1600 dpi. 
Greatful for help!

[lagarto]

Escape from tarkov sens should confused you , the aim fov depends of your in game fov, try 0.26 hipfire,75 in game fov, 0.20 aim (iron sight) with 800 dpi, remember that armor change hip fire sens, and RDS change the aim sens

[Kodak]

Hey there, it is maybe not exactly the right topic, but i couldnt find any help anywhere and think you could help me maybe.

I have to play with an touchpad from bamboo, it has its own drivers and in some games (like escape from tarkov) its not possible to look around. I can hit and aim with the touchpad, but i cant look around with it. 

so i checked the config data and i saw this: "

            "axisName": "LookX",
            "pairs": [
                {
                    "positive": {
                        "isAxis": true,
                        "keyCode": "None",
                        "axisName": "Mouse X",
                        "positiveAxis": true,
                        "deadZone": 0,
                        "sensitivity": 5
                    },
                    "negative": {
                        "isAxis": true,
                        "keyCode": "None",
                        "axisName": "Mouse X",
                        "positiveAxis": false,
                        "deadZone": 0,
                        "sensitivity": 5
                    }
                },
                {
                    "positive": {
                        "isAxis": true,
                        "keyCode": "None",
                        "axisName": "Joystick Axis 4",
                        "positiveAxis": true,
                        "deadZone": 0.63,
                        "sensitivity": 2
                    },
                    "negative": {
                        "isAxis": true,
                        "keyCode": "None",
                        "axisName": "Joystick Axis 4",
                        "positiveAxis": false,
                        "deadZone": 0.63,
                        "sensitivity": 2
                    }
                }
            ],
            "isInverted": false,
            "gravity": 0,
            "snapToZero": false
        },
        {
            "axisName": "LookY",
            "pairs": [
                {
                    "positive": {
                        "isAxis": true,
                        "keyCode": "None",
                        "axisName": "Mouse Y",
                        "positiveAxis": false,
                        "deadZone": 0,
                        "sensitivity": 5
                    },
                    "negative": {
                        "isAxis": true,
                        "keyCode": "None",
                        "axisName": "Mouse Y",
                        "positiveAxis": true,
                        "deadZone": 0,
                        "sensitivity": 5
                    }
                },
                {
                    "positive": {
                        "isAxis": true,
                        "keyCode": "None",
                        "axisName": "Joystick Axis 5",
                        "positiveAxis": true,
                        "deadZone": 0.63,
                        "sensitivity": 2
                    },
                    "negative": {
                        "isAxis": true,
                        "keyCode": "None",
                        "axisName": "Joystick Axis 5",
                        "positiveAxis": false,
                        "deadZone": 0.63,
                        "sensitivity": 2

"

 

all the KeyCode are labeled with None. Is that maybe the Problem?

If it is, what i have to insert instead? I tried it with Mouse X- and Mouse X+ but this seems to be wrong

Thx for your help

 

[lagarto]

This is not the place i think, sorry but i have no idea

[lagarto]

On 11/7/2017 at 7:15 PM, Traxilla said:

You might want to wait a lil bit, some of the ironsights, which all have the same FOV doesn't have the same ADS sens. i've been trying to get discussions going in the forums on it, but it doesn't seem like people even notice the problem.

apparently this will be fixed in the next patch

" Now, when switching from optics to reflex sight, mouse sensitivity changes "

forum.escapefromtarkov.com/topic/38694-patch-04-the-preliminary-patch-notes/

[Traxilla]

Ye i saw the patch notes, however i'd say wait until we get to try it after it drops.

[TheYellaKing]

Ive noticed when changing the Field of View the Aim Down Sights sensitivity feels about the same. Im playing on 75 FoV and when converting the monitor distance from other games I put 75 FoV in the aim down sights. This felt too fast, should I just put 50 for the FoV in ADS even though im playing on 75 FoV for hipfire. Bit confused.