Nevertheless, the program will not only scan for the target under the width of the health bar but will scan slightly to the left and also right of it's bounds (specifically 1/3 the width). jpxue/Overwatch-Aim-Assist is licensed under the GNU General Public License v3. The only problem is when there is only 1 health bar in that case I assume that the width is 150 by default. I have mine at 70 horizontal and 35 vertical. I always left aim assist at 100, but switched the window down to 10 to stop that horrible magnet feeling. Anyway, if you want to have some more fun, implement RawInput, here is a good example cnvcl/CnRawInput.pas at master * cnpack/cnvcl * GitHubIt's not super-accurate but accurate enough imo. I set sensitivity to 40/40 and hope to increase it further when I get used to it. Really nice from you to post source code, I wish more were like you. Coincidentally, this is also the window during ADS in COD. Aim Assist Window & Aim Assist Ease In The exact window where the magnetic pull of the aim assist matches the enemys body is 20. so you get for example pixelwidth 3 instead of 4 if you are farer away and you multiply wrong then. You can treat the game as having your breath held while scoped at all times since there is no idle sway in Overwatch. Problem: The width of one pack varies based on distance. For example: You determine the number of health bar "packs" by measuring one packs width and multiply it then. yeah you did it like i did in my first bot In my opinion it is not accurate enough though. Hanzo arrow hitbox combined with console aim assist. Other than that, I like how aim assist works in this game, since it certainly leaves a lot of space for actual skill when aiming, while providing a bit of assistance on moving targets.
I am too lazy to look into code, but how did you measure the width of the healthbar when target is not full hp?Įdit:// Okay I looked into code. Not sure if its some sort of lag or aim assist making a headshot when it shouldnt been one.