AIucardd

I'm using either Monitor Distance Dynamic or Vertical Viewspeed, and the conversions feel fine on my end. Make sure you're using your hipfire sensitivity as the 1.0x zoom baseline. From what I can see, your off calculations looks FOV-related. A 75 FOV in STALCRAFT is very low, so the scaling for 1.x scopes can easily feel off compared to higher FOV values. With my in-game FOV set to 98, the generated values scale as expected and I don't see the same issue.

Strange. Here, I recorded fresh install of the game, (don't mind 4.xxxxxxx sensitivity in the beginning - looks like that's because it's got my settings i had before the patch and bugged sens value), but I can set 0.01-0.99 no problem. I don't now, i doubt they have a difference between EU and RU versions... If it'll help, I lunch game through VK-play launcher (https://vkplay.ru/about/promo) strange.mp4strange 2.mp4

Hello there! I believe they updated sens slider in the game, now you can set decimals :-)

Hello there! They changed something again. Patch notes states that they made all x1 sights x1.25... but somehow it's feels a bit off. Maybe my options.json file gliched again, but, if it's not troublesome, it will be cool to doublecheck 😀

Hey there! I believe they updated the way you set sens a little (it's more refine rn). And I'm not sure about 1.0x sens - it's suppose to be same as hip-fire when using any other method than 360 distance (there is no zoom for 1.0x scopes).

Hey there! probably outdated. At least INI file edit makes sens way to low and "ingame" settings don't have "%" value

hello! There is zoom whilst ADS, but there is no compensation in mouse speed - it feels like there is the same см/360 for hipfire and for ads, but because of zoom ADS feels way faster. Is there an option to add ADS to calculator at least for bolters? I would rather have slower hipfire than faster ADS XD

ok, i fixed it. I deleted attributes.xml ([GAME FOLDER]\user\profiles\default\attributes.xml) file and everything is fine now. Sorry for wasting your time...

I have send a link to visualise what I mean, but TLDW: 360 for hipfire and Monitor distance dynamic for ADS, same FOV as Kovaak, mercenary aim type and default shoulder (no zoom). Sens for some reason at least 2 times slower than kovaak's My first thought was that there is no raw input in hunt, so I changed mouse pointer speed from 4 to 6. Same effect. Before update everything was perfect.

hmm, calculated sens feels way to slow, idk why.

false positive, I have no idea what it depends on. One day sens feels snappy and great, other days a bit sluggish and laggy. So yeah, disregard post above. XD

Ok, I figured this stuff out i think. Maybe it'll help some poor bastard like me. So, I Use AMD GPU. In AMD software there is analogical option to NVIDIA anti-lag feature (reflex) - "Radeon anti-lag". In most games it does more bad than good, but in Once Human it's almost fixed the issue at any fps (not only with high one). I can run the game at 150-200fps, so restricting it to about 120 with this option enabled removes horrible sluggish mouse feel. Your mileage may vary, i believe unstable fps fps will still give sluggish mouse feel. Strange, because in other games mouse feels great even with 60-80fps.

So, after release they added x2; x4; x8 scopes. Sens feels sluggish, probably input lag. ingame mouse smoothness option does not affect this. Manageable, but noticeable.

very strange, I did tried it with those settings and mouse feels way better than it was by default... maybe i played with screwd Y sens for so long that this one felt right on the money. bDampenFirstPlayerControls=0 bDampenThirdPlayerControls=0 fIronSightsLookSpeedPitch=2.0000 fIronSightsLookSpeedYaw=2.0000 fIronSightsPitchSpeedRatio=1.0000 fLookSpeedPitch=1.0000 fLookSpeedYaw=1.0000 fMouseHeadingXScale=0.0100 fMouseHeadingYScale=0.0100 fPitchSpeedRatio=1.0000 Altho, for ones who whant to try it, mod autor said you need to set and adjust mouse sens in game with ¯\_(ツ)_/¯

yes, I did those the same numbers and used it with fMouseHeadingXScale=0.0210 and fMouseHeadingYScale=0.03738, still felt off for me.