Jump to content

Quackerjack

Premium Members
  • Posts

    346
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by Quackerjack

  1. this is sick dude nice work!!! This also explains why the sens from 1.6 differs to csgo. If u play 4:3 sens is the same in 1.6 and go but if u play 16:9 u have to set m_yaw 0.0195 in csgo!!!
  2. apex fov doesnt affect sensitivity it says in the notes, try 360.
  3. actually i over thinked that, it says Valorant dont change ur sensitivity if u use different FoV's so 360 conversion to csgo or the other way csgo to valorant 360 should be correct
  4. yea but this game is mostly hipfire aim so mdh 0 should be in theory better
  5. just subscripe guys. Dpi Wizard had a lot of work here to do and did a great job, this calculator is awesome and his price worth
  6. just use instead of 360 MDV 0% and u fine. Dont forget to put in the right fov for apex. OW fov should be locked cause u cant change that.
  7. for my understanding u do it wrong, u have to calculate ur new resolution first, than convert 360. I dont recommend it. Just use MDV 0%.
  8. yes i saw that. But that isnt a option for me. I just want my native res i give it a try. So with the custom resolution i calculate 360 distance then? Edit 1: Wow this feels actually very very nice! Edit 2: Switched back to native res and 0% MDV, its better for me
  9. yes u right about that. But there are games u cant change hipfire fov. Ex. Csgo and Valorant. I would go for 0% for this games not 360
  10. But is it not always the best options to convert hipfre with MDV 0%? If u have different FoV u should use 0% not 360 if u want exact same sens. Most important on a hipfire only game.
  11. maybe, but what if m_rawinput 1 add m_filter 1. How u test that? found this thread: and this post: soonpls FaZe Clan Fan 1 point · 3 years ago technology evolved since 1.6 days nowadays, most mouses have filter inside their software. there's lots of things that are different in csgo, like using m_rawinput 1 and m_mousespeed 0 - gives you a similar feeling to m_filter 0, but it's still not the same. What i've experienced is having the DPI as close as possible to the resolution, so for 1920x1080 - 1800 dpi, for 800x600 - 800dpi, etc. and adjusting your sens to have the same 360 sens you have now, will get you a snappy gameplay and on-point aiming, decreases the smoothness. try that, maybe it'll help you as well. tl;dr m_filter is irelevant these days. closest way to reproduce it is m_rawinput 1; m_mousespeed 0 (dont do that use m_mousespeed 1) And this solved every Problem for me mouse is 1:1 now
  12. i highly recommend 100% MDV fells so natural for me
  13. Hi guys, since i got much time now (thanks corona hope everyone is fine) i start testing m_rawinput 1 vs 0 again. Hint: u need to have stable fps on m_rawinput 0 First the backgrounds, it was testet that m_rawinput 1 does not generate any input lag and works the way it should. But only normal mouse movements were tested with a script. I claim that m_rawinput 1 doesn`t capture small mouse movements correctly. Try: 1. On a pistol server m_rawinput 1 vs 0 u notice headtracking is much easier with 0, u dont overshoot when enemies strafing (AD AD AD) 2. Spray on a wall its much easier with m_rawinput 0 Why?!?! Small mouse movements are not perceived so u move ur mouse more and overshoot (test 1) or fuck up your spray cause u pull the mouse slowly down but the mouse movement dont get detected. (test 2) This is where you come in. I do not want to make any claims, I want to prove that something is wrong. The only question is how can I do that? Any help is welcome
  14. the calculator works fine just read the instructions
  15. i will give it a try again. The problem for me is that the same fov on apex looks so zoomed in.
  16. I tried this before i prefer matching all with MDH 0% now. I also make it like 1 zoom apex fov is hipfire fov for csgo so the sensitivity should be excat the same.
  17. na u good, i just have to read better. But im still confused why i can aim in apex perfect fine and in csgo the sens seems to slow/delayed. Can this be input lag or smth?
  18. damnit i didnt realise its Scope sensitivity i thought its ADS. So yes it was set wrong by myside. Sry @Mr. Wizard
  19. than there is a small bug. Its the same with MDH 0%. I also found out the sensitivity feels closer if u set fps_max 0 in cs
  20. is this correct? The sensitivity should be excat the same but in csgo it feels a lot slower?
  21. Yes i understand that. But in theory if u switch monitors with different aspect ratios this should also affect the sensitvity. https://www.computerbase.de/forum/threads/16-9-oder-16-10-gaming.940573/#lg=post-10464649&slide=1
  22. just to make sure. If u went from 16:10 monitor native resolution to 16:9 monitor native resolution this whole thing doesnt affect it. I dont get it why this change in aspect ratio doesnt affect anything
  23. nice!!! iam still confused if u went from a 16:10 screen/monitor or 4:3 screen to a 16:9 Monitor. U choose which option or doesnt it matter?
  24. are we sure the fov is right in the calculator? Seems like 108 ingame looks more like csgo 90 fov
×
×
  • Create New...