Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
So Manager wasn't automatically updated for you?
Please update your Manager with latest in the store. Older versions of Manager are no longer getting game updates. Was Manager not updated automatically for you?
I'm convinced that high DPI + low polling is the gold standard. Gives strong aim assist yet not in a detrimental way, makes the bubble nice and smooth to work with. I feel like high polling just makes the aim slowdown happen so suddenly, whereas low polling creates more of an ease-in effect, making it easier to get to the centre of the hitbox. Been on 125hz with Default sync for a couple of weeks and it's been great.
Guys make sure you know the sensor in your mouse if its not a logitech or a mouse with similar sensor that adds no smoothing at any dpi. Other wise example of you got a mouse with a 3360 sensor like me i suggest using 2000 dpi. Otherwise if you go higher your adding 32 frames of smoothing(6.4ms delay) and making aim assist alot stronger. If you dont feel the delay your crazy.Bro run a 3200 like the rest of the community recommends. Your literally wasting your time fooling around with all these dpis. High dpi is @#$%, and has garbage micro movement, low dpi will you give you more sticky hitbox in and out, and 3200 is literally the sweet spot. I’ve been on any dpi you can think from 800-250000. And I always go back to 3200 it’s just a flexible dpi. You can run a low sens and feel like 800, or a high sense and feel like 16000. You so worried about something everyone knows console comes with DELAY, you cupcake. Go on your xim app use a 3 smoothing and stop posting these dumb comments, you sound inexperienced like you don’t know to use a simple app
Guys make sure you know the sensor in your mouse if its not a logitech or a mouse with similar sensor that adds no smoothing at any dpi. Other wise example of you got a mouse with a 3360 sensor like me i suggest using 2000 dpi. Otherwise if you go higher your adding 32 frames of smoothing(6.4ms delay) and making aim assist alot stronger. If you dont feel the delay your crazy.Bro run a 3200 like the rest of the community recommends. Your literally wasting your time fooling around with all these dpis. High dpi is @#$%, and has garbage micro movement, low dpi will you give you more sticky hitbox in and out, and 3200 is literally the sweet spot. I’ve been on any dpi you can think from 800-250000. And I always go back to 3200 it’s just a flexible dpi. You can run a low sens and feel like 800, or a high sense and feel like 16000. You so worried about something everyone knows console comes with DELAY, you cupcake. Go on your xim app use a 3 smoothing and stop posting these dumb comments, you sound inexperienced like you don’t know to use a simple app
Guys make sure you know the sensor in your mouse if its not a logitech or a mouse with similar sensor that adds no smoothing at any dpi. Other wise example of you got a mouse with a 3360 sensor like me i suggest using 2000 dpi. Otherwise if you go higher your adding 32 frames of smoothing(6.4ms delay) and making aim assist alot stronger. If you dont feel the delay your crazy.Run 0 smoothing, learn how to steady your hand, use 3200 dpi.
Ya i agree with you...have u ever tried max dpi or even lower dpi an off sync an 20 smoothing to see how it is for a day or so?
Yeah I tried MJFame settings for quite a while, 800 DPI, 1000hz, sync off. Tried them again this evening just out of curiosity, they're still definitely good but I prefer 250hz, 3000DPI, common sync. I should try those but with 500hz instead of 1000, see how it feels!
@Bb4life1991 Welp, it appears I made as mistake in my earlier posts. I said before I switched from 12k and 250hz, to 3000 and 500hz. At first I was switching back and forth between the two, couldn't decide which I liked best, ended up calling it a night and decided I marginally liked 3000 DPI 500hz better so I set that up for the next day.
The next day, I tried it, it felt amazing, been using it all week, still love it...
...well, today I discovered I'm actually running 250hz 3000 DPI lol. Been switching back and forth between 250hz and 500hz on the same config and I'm absolutely convinced, 500hz is stickier in a way you don't want it to be, AA bubble feels very stiff. 250hz is not only giving me a smoother time with the AA bubble but also the tracking assistance is way stronger.
I do genuinely believe that, at least for lower sens players, lower hz is the way to go. 3000 DPI and common sync with it feels great. RML AAA curve #6 to aid cutting into and out of the hit box. I've never found a config that's as sticky as this yet had no problems with getting stuck outside the hitbox. 250hz gives more controller-like movements which helps you ease into the hitbox where 1000hz would see you getting stuck on the edge of the bubble.
Bb4life1991where can I see the settings mrbrutalfrosty?
Ya see what u said i feel same way high hz low dpi vise versa as long as one way or another there is a delay it works well. Low dpi to me feels delayed same with low hertz or 20 smoothing etc etc. the moment I try to make it snappy like pc aim assist feels janky an strong etc etc
I also feel st plays a role i feel xbox almost gives that delay feel vs the ps4 st but not sure maybe vise versa
Yeah, just about finding that sweet spot. I tried low everything, 800DPI, 250hz, common sync, that was too much, felt horrible lol, legit took 100+ milliseconds for my aim to catch up to my hand. Don't wanna be getting more delay than the next guy using a controller that's for sure lol. I feel like if you were a player of hardcore modes on COD where snapping onto the enemy as quickly as possible and just hitting one shot is the primary goal, high DPI, high hz, sync off would be the play, you just want pure snappiness. I'm still a BO4 player mainly though and especially in Blackout, being first to shoot is less important than actually staying on target for a very significant amount of time. That's when snappiness becomes less important and tracking while moving yourself is everything. A trade off of adding a little latency to have more of your bullets hitting once on the target is well worth it.
So you feel a difference between 1000hz common an 250hz common? To me i almost was thinkin default an common are actual those hertz amount. Cause 125hz off sync you have the same exact sense as default sync(120hz) then when you use common or default any jittter or interpolation is gone...common getting rid of it even on 800 dpi.
Yeah absolutely felt a difference, even with common sync, the lower hz feels a tad more sluggish but feels nicer with the AA and more accurate, whereas 1000hz common felt snappier but the AA slowdown felt really sharp at times and not nice.
I think the balance of DPI, sync and hz all come into play. Low DPI and high hz can feel similar to high DPI and low hz, for example. Either way, what I do know is, I've been sleeping on common sync for a long time aha. Makes the AA bubble silky smooth and provides the most accurate mouse movements.
I first tried low polling after reading one of SweatyPapi's threads, I did initially try 250hz common with 3000DPI like he suggests but I'm quite a low sens player, and it felt way too sluggish for me. So higher DPI or higher polling was needed. Initially went with 12k and 250hz but tried 3000 with 500hz and it definitely feels better, beam settings.