Wizard DPI Wizard Posted September 14, 2018 Author Wizard Posted September 14, 2018 Not sure exactly when this was updated, but a lot of scopes have changed. 4X is now 4.2229X (??), 2X is actually 2X (was 1.8X), 8X is actually 8X (was 7.25X) and so on. Since the sensitivity scale according to the FOV the impact on the sensitivity is minimal, but I will update them all soon!
Skidushe Posted September 14, 2018 Posted September 14, 2018 I will be interested on seeing if this is the reason some things have been feeling weird, well spotted
Dency Posted September 15, 2018 Posted September 15, 2018 When comes the new version of the calculator?
Skidushe Posted September 15, 2018 Posted September 15, 2018 On 9/14/2018 at 6:01 PM, DPI Wizard said: Not sure exactly when this was updated, but a lot of scopes have changed. 4X is now 4.2229X (??), 2X is actually 2X (was 1.8X), 8X is actually 8X (was 7.25X) and so on. Since the sensitivity scale according to the FOV the impact on the sensitivity is minimal, but I will update them all soon! has this been implemented yet?
Wizard DPI Wizard Posted September 15, 2018 Author Wizard Posted September 15, 2018 Just now, Skidushe said: has this been implemented yet? Only on the new version which isn't published yet. I hope to publish it tomorrow!
Skidushe Posted September 15, 2018 Posted September 15, 2018 Just now, DPI Wizard said: Only on the new version which isn't published yet. I hope to publish it tomorrow! looking forward to it
Wizard DPI Wizard Posted September 16, 2018 Author Wizard Posted September 16, 2018 Scopes are updated: 2X is 2X (was 1.8X) 4X is 4.21X (was 4X) 8X is 8X (was 7.25X) Scopes now also scale correctly with aspect ratio.
RipGroove Posted September 17, 2018 Posted September 17, 2018 (edited) As I have a 21:9 monitor should I be doing anything different in the calculator to compensate for that and give me my true cm/360° distance? Currently my calculation looks like this: TPP FPP I've not physically measured my cm/360° yet but it does feel a bit fast with the above settings. Oh and are you able to explain why my sensitivity values are different to the above if I leave Squad off the calculator and just try to calculate a 35cm/360° for PUBG? Edited September 17, 2018 by RipGroove
Wizard DPI Wizard Posted September 17, 2018 Author Wizard Posted September 17, 2018 You are converting 75% Monitor Distance from Squad to PUBG, change the Normal conversion mode to 360 Distance if you want that to be 35cm for all games This is also why you get different results when you plug in 35 cm directly for PUBG.
Skidushe Posted September 17, 2018 Posted September 17, 2018 Should I trust the lastContertedSensitivity values generated from putting the in game sensitivities in, or the lastContertedSensitivity values generated by the calculator more? They always seem to be ever so slightly different?
Wizard DPI Wizard Posted September 17, 2018 Author Wizard Posted September 17, 2018 Just now, Skidushe said: Should I trust the lastContertedSensitivity values generated from putting the in game sensitivities in, or the lastContertedSensitivity values generated by the calculator more? They always seem to be ever so slightly different? The ones generated by the game are actually slightly off, the calculator is accurate. But the difference is barely even measurable.
RipGroove Posted September 18, 2018 Posted September 18, 2018 23 hours ago, DPI Wizard said: You are converting 75% Monitor Distance from Squad to PUBG, change the Normal conversion mode to 360 Distance if you want that to be 35cm for all games This is also why you get different results when you plug in 35 cm directly for PUBG. I'm so confused, I thought I based my calculations on what you showed me below but I forgot to set 'Conversion Setup" properly: But after correcting I still get different results when I convert a Squad hipfire of 35cm/360° to PUBG: Conversion: Just PUBG: Obviously I'm missing the concept as one method gives me sens of 32 for all scopes and the other method gives me a sens of 32 for "General" and 36 for everything else.
Wizard DPI Wizard Posted September 18, 2018 Author Wizard Posted September 18, 2018 The first one is using TPP, the second one is using FPP. These are different for General sensitivity since TPP is locked to a specific FOV, while FPP has a variable FOV. For the first one your actual FOV is 92, while Squad is 90. That's why you get a slightly different result for General (which is matched to 360 distance) and the scopes which are matched to 100% of the 90 FOV. For the second one the actual FOV is 103.5 which is why the General sensitivity is so much lower. The scopes are still matched to Squad with 90 FOV however. In the last one everything is matched to the FOV of FPP, so they are all the same. The important thing to note is that all the sensitivities will be calculated based on the hipfire sensitivity of the input game. So when you do like the first and second one the scopes are not matched to General sensitivity in PUBG, but Squad hipfire. RipGroove 1
RipGroove Posted September 18, 2018 Posted September 18, 2018 8 minutes ago, DPI Wizard said: The first one is using TPP, the second one is using FPP. These are different for General sensitivity since TPP is locked to a specific FOV, while FPP has a variable FOV. For the first one your actual FOV is 92, while Squad is 90. That's why you get a slightly different result for General (which is matched to 360 distance) and the scopes which are matched to 100% of the 90 FOV. For the second one the actual FOV is 103.5 which is why the General sensitivity is so much lower. The scopes are still matched to Squad with 90 FOV however. In the last one everything is matched to the FOV of FPP, so they are all the same. The important thing to note is that all the sensitivities will be calculated based on the hipfire sensitivity of the input game. So when you do like the first and second one the scopes are not matched to General sensitivity in PUBG, but Squad hipfire. Thanks. I need to stick with Squad as the input then to keep muscle memory I guess. I'll have a play around in the training mode again and see what feels right.
RipGroove Posted September 18, 2018 Posted September 18, 2018 I guess for muscle memory this is what I should be focusing on for all scopes and games?
Wizard DPI Wizard Posted September 18, 2018 Author Wizard Posted September 18, 2018 38 minutes ago, RipGroove said: I guess for muscle memory this is what I should be focusing on for all scopes and games? Yes, and that's why it's important to always use the same source for your conversion. RipGroove 1
NukeON Posted September 18, 2018 Posted September 18, 2018 (edited) 4 hours ago, DPI Wizard said: The important thing to note is that all the sensitivities will be calculated based on the hipfire sensitivity of the input game. So when you do like the first and second one the scopes are not matched to General sensitivity in PUBG, but Squad hipfire. What do you think is the most important game to maintain the sensitivity for ads and scoping?? of the original game that is being exported or the one you are playing, my idea is to keep the hipfires, but I do not know which configuration of 0% MM to use for ads and scope, from root game, or the export... Edited September 18, 2018 by NukeON
RipGroove Posted September 18, 2018 Posted September 18, 2018 11 hours ago, DPI Wizard said: Yes, and that's why it's important to always use the same source for your conversion. So what exactly is the 'cm mouse movement'?
Wizard DPI Wizard Posted September 18, 2018 Author Wizard Posted September 18, 2018 Just now, RipGroove said: So what exactly is the 'cm mouse movement'? In this case it's how far you have to move the mouse to aim at something at the very edge of your monitor.
Wizard DPI Wizard Posted September 18, 2018 Author Wizard Posted September 18, 2018 8 hours ago, NukeON said: What do you think is the most important game to maintain the sensitivity for ads and scoping?? of the original game that is being exported or the one you are playing, my idea is to keep the hipfires, but I do not know which configuration of 0% MM to use for ads and scope, from root game, or the export... The original game, or else you will get different scope sensitivity in games that have different FOV from the original.
NukeON Posted September 18, 2018 Posted September 18, 2018 1 minute ago, DPI Wizard said: The original game, or else you will get different scope sensitivity in games that have different FOV from the original. Thanks mate!, fixing my sens, thanks for all.
RipGroove Posted September 18, 2018 Posted September 18, 2018 8 minutes ago, DPI Wizard said: In this case it's how far you have to move the mouse to aim at something at the very edge of your monitor. 8 minutes ago, DPI Wizard said: In this case it's how far you have to move the mouse to aim at something at the very edge of your monitor. Interesting, thanks.
a634754420 Posted September 19, 2018 Posted September 19, 2018 (edited) English is not my mother tongue, this is Google translate. This conversion right? I am a 16:9 zoom_sensitive_ratio_mouse is 1 But I can't change it I want a Chinese, I can't understand English Edited September 19, 2018 by a634754420
MuntyYy Posted September 19, 2018 Posted September 19, 2018 (edited) 1 hour ago, a634754420 said: This conversion right? I am a 16:9 zoom_sensitive_ratio_mouse is 1 set those to 75% Edited September 19, 2018 by MuntyYy
a634754420 Posted September 20, 2018 Posted September 20, 2018 21 小时前, MuntyYy说: set those to 75% BBS 0% vote not to say that all is better?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now