jabbothehut

settings are the saem but in ironsight.ini now Edit: Nvmd still looking

That would be amazing thanks!

@DPI Wizard is there a way to customise rds sensitivity exclusively or is it only snipers?

Would be viable if the fov's for irons were the same across games

Thanks my dude! Edit: Realised this was the same as monitor matching the zoom 1 for the awp in csgo. This number changes depending on the weapon zooms. Would 0.81... match all scopes and zooms at 0% in insurgency or is it only for irons?

So if one wanted to get a 0% monitor match to irons what would the number be?

when would that be roughly?

thank you so much! <3

Is there a tutorial somewhere on how to find the correct hex values? I have no idea what to do

I would agree with you but im currently on 34 inches for a 360 x'D. Trust me I've tried every sens from 5-35 inches and it's the same with viewspeed or 100%. It feels way too fast when in ads. Yet again this is personal preference and muh feels so don't hold this as a universal truth.

So far 0% feels wrong and right for me if that makes sense. It gives me the control I should have in zoom that viewspeed doesn't (this is bf4 1x sights btw) but it doesn't feel natural. Bear in mind that I just swapped from viewspeed so I am still getting used to it and it seems to be getting better with time. This is definitely a muh feels vs muh reals scenario since ultimately the brain specialises to one fov and one sensitivity for that specific fov so changes will throw it off no matter how mathematically correct they are.

Rendezvous in a couple of days here then.

I always thought that 0% match would be (mathematically speaking) the most obvious way to line up fov's since you are essentially taking pixel count difference as measurment (for 3d-3d fovs anyway). I suppose as you say that the wierd part to this would be the distortion and the projection issues that the brain tries to deal with. I think i'll swap to this and let my brain get used to it.

Cool thanks man!

Coolbeans. So for anything under 90 (4:3) the current viewspeed formula should do the job then?

What range of FOV's is the current formula viable in would you say?

Guessing you mean extreme FOV as in going from 73.74 hipfire in BF1 to like 20 or something for the 10x scopes?

Just out of interest. Where did you find that the current viewspeed formula started to become inconsistent/problematic?

We shall see!

Maybe. I dunno tbh I don't think it'll change too much. Would just be nice to see what the new one does!

It would be super interesting to see the difference with this new equation. When I use viewspeed for games like bf1 or rainbow six with a very slight zoom on RDS sights they always feel a bit wobbly and too fast. Wonder if that was just in my head or if this was due to the current equation being a bit off :/

I mean it feels the same as it is 1920x1080p (supposedly) for both aspect ratios but I would agree with you that it probably isn't. As potato said it would be great if someone could clarify this!

You misunderstand. I have a 1080p monitor. Siege gives you the option of playing at 1080p but in 16:9 or 16:10 while retaining a 1080p resolution. WOuldn't this be the equivalent of playing 4:3 with black bars on a 1080p monitor?

So in rainbow six siege there is an option for me to play at 1080p at either 16:9 or 16:10. 16:10 gives me a more stretched image which makes headshots easier. The question is; does this affect my sensitivity since resolution stays the same?

360 distance is recommended when the FOV is identical between both calculations whereas viewspeed is used with everything as it keeps sensitivity feel across different fovs, resolutions etc constant. If in doubt just use viewspeed as it will give you the same results for 360 distance anyway if both fovs are the same.