Wickland

Was this forgotten? or is there just no way you can figure out the conversion at this time.

Haven't got to it, but will do it eventually!

Thankyou very much, ESL starts in 2 weeks and it would be nice to have my sensitivity, right now the one in game is very strange at 22cm/360 you can only get within 5cm or so above/below with going from 12-13 setting.

Wickland is up now!

Thanks for getting this done mate! Having this issue, my mate with 1150 DPI and like 3.66 sense has the same issue, now i can double the DPI and half the sensitivity to get a number to show up, but then im not 100% sure if its going to be accurate and im also not sure in the CFG where to find the relevance is to change the sense.

with 800 dpi and 2 sense in QL i get this below

Edited December 11, 201411 yr by StillBlaze

I feel like something is still off. I tried to replicate the same sensitivity from  Quake and CS:GO to Wickland

I'm currently using 800DPI/430sens @100fov in Wickland which is calculated to 0.97 in CS:GO however this results in MUCH slower movement in CSGO compared to Wickland and requires an estimated 10/15cm or so more movement to turn 360degrees

I measured Wickland at 430 to be roughly 40cm and not 52cm as stated by the calculator. It says that sens is affected by FOV but my rough measurements suggest that it isn't.

Calculations are off and i think i know why. If you take another game on ue3 like ut3/tribes and set same sens and fov in both games like for example fov90 then cm/360 would be quite similar. When wickland is running at default 120fov it affecting sens to be higher. You actually noted that its affected by fov but the starting point seems a bit different. Try tribes/ut3 algorythm im pretty sure it must work. Can you please check this out