March 7Mar 7 Author Wizard 26 minutes ago, Fortynbras said: Can you update as rn its not even close I just verified that the calculations for this game are correct. What exactly is your conversion? Join the community on Discord!
March 7Mar 7 From overwatch 1600 dpi 2 sens to 0.22 in fragpunk (109 fov) but its too fast. About 0.08 is more like it
March 7Mar 7 Author Wizard 42 minutes ago, Fortynbras said: From overwatch 1600 dpi 2 sens to 0.22 in fragpunk (109 fov) but its too fast. About 0.08 is more like it It might be a polling rate issue maybe, are you using over 1000 Hz? Join the community on Discord!
March 9Mar 9 My conversions seem to turn up incorrect. The proper sensitivity I used for 360 conversion seems to be 1.18. I checked using kovaak's sensitivity matcher.
March 9Mar 9 kovaaks for fragpunk shows 0.23762 which is even more, so I guess there's some bug in the game?
March 9Mar 9 Author Wizard 4 hours ago, SeikoPotato said: My conversions seem to turn up incorrect. The proper sensitivity I used for 360 conversion seems to be 1.18. I checked using kovaak's sensitivity matcher. 2 hours ago, Fortynbras said: kovaaks for fragpunk shows 0.23762 which is even more, so I guess there's some bug in the game? Are you getting the Kovaak's Sensitivity Matcher to work in Fragpunk? It does not work here, I have to use physical mouse emulation. I would assume you have to tweak the settings in Kovaak's to get accurate results if it does work. Join the community on Discord!
March 9Mar 9 Author Wizard On 3/7/2025 at 7:50 PM, Fortynbras said: From overwatch 1600 dpi 2 sens to 0.22 in fragpunk (109 fov) but its too fast. About 0.08 is more like it 4 hours ago, Fortynbras said: kovaaks for fragpunk shows 0.23762 which is even more, so I guess there's some bug in the game? Might be a bug that doesn't affect any of my systems. The sensitivity formula is consistent with Unreal Engine, so there's no doubt it is correct. Here's a demo of your exact sensitivities, and as expected, FragPunk overshoots a small amount (247 counts) due to lack of decimals, so it's 100% correct according to the calculations. 7 hours ago, SeikoPotato said: My conversions seem to turn up incorrect. The proper sensitivity I used for 360 conversion seems to be 1.18. I checked using kovaak's sensitivity matcher. I see that they've updated the 1x FOV, so this change is reflected in the calculator now Join the community on Discord!
Create an account or sign in to comment