WhoCares? Posted July 2, 2018 Posted July 2, 2018 (edited) Hi all Until now I didnt spend a lot of time in CSGO, so I am not that well-versed in therms of console-commands and stuff. I would like to train my aim at different FOVs with help of CSGO. For different FOVs I want to scale my sensitivity with 0% Monitor match, and I want to change this by doing a simple key press For example: When I press Numpad 1, my fov is lowert from 90 (4:3) to 50 (4:3) and the corresponding sensitivity (in my case 0.593440 at 1600 DPI and full-HD) will be automatically lowert (in my case 0.498106.) I know somewhere in this forum (I belive in Viewspeed Rework) somone posted this kind of scripts, but I can not find them anymore I can do the calculation for myself, I justn need an example how to do the keybinds Can anyone help me out? AND, before I forget: is sensitivity affected by the ads-sensitivity slider when using the fov_cs_debug comment? (even when not using an actuall scope? From my testing it looks like it does) If yes, do just I just set the ads-sensitivity slider to 1.0 and do all the caculations with the normal sensitivity? Edited July 2, 2018 by WhoCares?
potato psoas Posted July 2, 2018 Posted July 2, 2018 Do you still have the modified python script link @Drimzi?
Drimzi Posted July 2, 2018 Posted July 2, 2018 https://github.com/Skidushe/sens-fov-scalar Zoom sensitivity ratio has no affect on hipfire sensitivity, even if you change the fov. The sensitivity scales by 90/fov, and so it will be distance matched to 4:3 if you leave the sensitivity value untouched and change fov.
WhoCares? Posted July 2, 2018 Author Posted July 2, 2018 1 hour ago, Drimzi said: https://github.com/Skidushe/sens-fov-scalar Zoom sensitivity ratio has no affect on hipfire sensitivity, even if you change the fov. The sensitivity scales by 90/fov, and so it will be distance matched to 4:3 if you leave the sensitivity value untouched and change fov. Thank you a lot ! But are you sure ADS sensitivity doesnt affect the fov_cs_debug? I mean I am pretty sure it does If I set it to 0.1 my normal hip fire sensitivity is nearly zero when using 50 fov forced by fov_cs_debug comment. EDIT: Just checked again. When using fov_cs_debug you sensitivity is definitly affected by the ads sensitivity slider. I used 89 fov und lower the ads sensitivity slider all the way down, and my sensitivity is extremely low. When I set it to 1.0 ist fine again.
Drimzi Posted July 3, 2018 Posted July 3, 2018 (edited) 13 hours ago, WhoCares? said: Thank you a lot ! But are you sure ADS sensitivity doesnt affect the fov_cs_debug? I mean I am pretty sure it does If I set it to 0.1 my normal hip fire sensitivity is nearly zero when using 50 fov forced by fov_cs_debug comment. EDIT: Just checked again. When using fov_cs_debug you sensitivity is definitly affected by the ads sensitivity slider. I used 89 fov und lower the ads sensitivity slider all the way down, and my sensitivity is extremely low. When I set it to 1.0 ist fine again. Wow you are right. That's pretty funny. Tested 360 with a script with 1.0 zoom_sensitivity_ratio and it was spot on. Tried 0.01 and it wouldn't even move. At least it affects all fov equally. Edited July 3, 2018 by Drimzi WhoCares? 1
Wizard DPI Wizard Posted July 3, 2018 Wizard Posted July 3, 2018 4 hours ago, Drimzi said: Wow you are right. That's pretty funny. Tested 360 with a script with 1.0 zoom_sensitivity_ratio and it was spot on. Tried 0.01 and it wouldn't even move. At least it affects all fov equally. This explains a lot! I never even considered this to be the issue, but when I was analyzing CSGO and how it scales with FOV a long time ago I got really weird results. I deleted the config file and suddenly the scaling made sense. I realize now that the reason it was weird is because I had the zoom_sensitivity_ratio to something other than 1. The question is if there's a demand for a calculation where this value is applied to hipfire for those who want to change FOV and use values other than 1 for zoom?
WhoCares? Posted July 3, 2018 Author Posted July 3, 2018 Yeah I found it strange too So it's best to set it to 1.0 for my desire of switching fovs, right?
Wizard DPI Wizard Posted July 3, 2018 Wizard Posted July 3, 2018 1 minute ago, WhoCares? said: Yeah I found it strange too So it's best to set it to 1.0 for my desire of switching fovs, right? Yes, if you don't intend to use the scopes anyway keep it at 1.0
Drimzi Posted July 3, 2018 Posted July 3, 2018 You can always set it to 1 in your fov changing binds, and have it correct in your autoexec.
Skidushe Posted July 8, 2018 Posted July 8, 2018 I recently pushed an update to the script I was going to create a post about but forgot, I've changed the file structure so rather than pressing 2 and 3 for each change, the scripts incorporate this so that you only need to keep pressing 1. I'll push my python script up to the same repository which does this so that you don't need any differences in keyboard macro software and everyone can use the same thing. I'll make a main post when I do this WhoCares? 1
Skidushe Posted July 8, 2018 Posted July 8, 2018 (edited) @WhoCares? I've just posted a new thread with all the info on here: Edited July 8, 2018 by Skidushe
WhoCares? Posted July 8, 2018 Author Posted July 8, 2018 (edited) 1 minute ago, Skidushe said: @WhoCares? I've just posted a new thread with all the info on here: I was reading/watching it right now Thank you for your effort Edited July 8, 2018 by WhoCares?
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