is scoped in sensitivity differnet than unscoped


(mendaciousBattlement) #1

I have played a lot of sniper in many games (mostly tf2 CsGo) and most of the time the scope moves the same distance per input when scoped vs unscoped. However I’m feeling like the sniper in this game seems to drag a bit almost like I’m playing on 10 sensitivity not 11.9. is it possible the change i made to my setting isn’t effecting my scope or is there actually a modifier when scoped in.


(Humbug) #2

I think “FOVSensitivityScale” is the command in console for changing it


(Ghosthree3) #3

FOVSensitivityScale doesn’t exist. Just checked. Neither does anything starting with sensitivity or scale.


(Humbug) #4

hm didn’t try it yet.
would like a slider for zoom sensitivity, I can’t snipe in DB because of the weird zoom sensitivity.


(Lagenberg) #5

This is also a huge problem. Stopped playing Vassili because of this. It’s kinda ridiculous that you cannot control the scoped in sensitivity as mercs run and long jump easily past you as you try to track them with ~40% of your sens.


(B_Montiel) #6

One way worth exploring : Through console or .ini binding file, you should be able to bind your aim key and set the sensitivity while pressing/releasing it. Two issues tho : you’ll be forced to hold your key and it will change the sensitivity not only for scopes but also when adsing with any weapon.

udn.epicgames.com/Three/KeyBinds.html
forums.warchest.com/showthread.php/33070-Dirty-Bomb-Technical-Pro-Tips

The proper command to tune the sensitivity is : setSensitivity “yournumber” savetoconfig “0 or 1”. savetoconfig seems to be optional.


(Ghosthree3) #7

If he wants it to be a uniform sensitivity he wouldn’t need to hold it. Simply pressing it should readjust the sens to the base one after its changed for the zoom.

If sensitivity is in fact modified which I really doubt, it’s probably just scaled.


(fubar) #8

SetFOVSensitivityScale (0-1)


(Ghosthree3) #9

SetFOVSensitivityScale (0-1)[/quote]
Hm, that pops up when you start to type it but finishing tab to complete it or just typing it in says command unrecognised when you return.


(B_Montiel) #10

You’re right, that’s probably due to the difference of FOV between scoping and not. At least, all UE3 games I played before were using FOV modifications while scoping. That precise scaling in FOV virtually modify the sens. There’s probably a less harsh way to change the sens while scoping but if you find the ratio that would work as a turn-around solution I guess.


(Ghosthree3) #11

According to mouse-sensitivity.com this game’s mouse input is unaffected by the fov setting, which is really good. Perhaps scoped fov is different though.


(B_Montiel) #12

Yup, I think it is. But in my mind, even if the mouse input is unaffected by the fov, it may modify the sensitivity from the player perspective. I’m far from being an expert, but in chivalry (good archers mainly) and tribes:ascend (both UE3 based games), people extensively using scope worked those sens issues that way.


(Litego) #13

I’m not sure what the OP is saying, but in TF2 and CSGO your sensitivity do scale with zoom (FoV) as it does in most games (By default). Mouse-sensitivity only checks the FoV scaling flag if sensitivity scales when you change the default FoV, for zoomed FoV almost every game I know do scale the sensitivity, and for good reason. Having the same sensitivity unscoped and scoped is terrible and fucks up your aim, it’s not natural. Because even though it’s the same sensitivity, it feels like you changed it. Moving the mouse 5 cm will for example turn the camera 500 pixels while unscoped and 1000 pixels while scoped. You moved the same distance in 3d space, but a monitor is 2d, so it feels off.

The problem with this game, and UE3 in general is that at low sensitivity the game starts rounding mouse inputs down to 0 (basically ignoring your mouse). Say you have a sensitivity of 6, should be fine, but then you zoom in and the game scales it down to like 4, now you’re fucked. This causes it to feel sluggish, like it lags behind. The only solution is to increase the in-game sensitivity and compensate by lowering your DPI. It’s an engine problem and I don’t have any hopes for it to be fixed. See the same problem in every single UE3 game, it’s terrible.


(Ghosthree3) #14

My sensitivity is 3.699143 and I have no problems with rounding/ignoring input.


(Litego) #15

My sensitivity is 3.699143 and I have no problems with rounding/ignoring input.[/quote]
Take Vasilli, zoom in, move your mouse very slowly, you’ll see nothing happens. If I remember correctly the problem first occurs around a sensitivity of 5, and the lower you go the more obvious it becomes, as in, you can move your mouse faster at lower sensitivities with nothing happening.


(Ghosthree3) #16

I’ll give it a go when I get him, or when he’s free - oh god imagine free week Vasilli.

Does it need to be zoomed or could you test it by simply reducing the sensitivity?


(Litego) #17

[quote=“Ghosthree3;26104”]I’ll give it a go when I get him, or when he’s free - oh god imagine free week Vasilli.

Does it need to be zoomed or could you test it by simply reducing the sensitivity?[/quote]
I am not sure, the problem only happens for me when I zoom in UE3 games, and I haven’t read up on the issue since Tribes Ascend. I guess you could try to set your sensitivity ridiculously low and see what happens.


(mendaciousBattlement) #18

so from what im getting is maybe binding the scope in key to a sensitivity change may fix this ill give it a try see if it helps ty


(Ghosthree3) #19

[quote=“Litego;26107”][quote=“Ghosthree3;26104”]I’ll give it a go when I get him, or when he’s free - oh god imagine free week Vasilli.

Does it need to be zoomed or could you test it by simply reducing the sensitivity?[/quote]
I am not sure, the problem only happens for me when I zoom in UE3 games, and I haven’t read up on the issue since Tribes Ascend. I guess you could try to set your sensitivity ridiculously low and see what happens.[/quote]
Well I ended up getting Vasilli and trying it, can’t feel any problems with any setfovsensitivityscale settings or unmodified.