[C++] Color Aim Assist Source Code

[marlinchis]

dont know what i did wrong but when i run it says source file not compiled

[SeaDragon]

Thanks for sharing . Cool that you only release the source so you don't need to reply to trolls asking how to make it work.

BTW a simple method to calculate mouse movement is here:

Math.Atan( (pixels to move) / ( (half of screen width) / ( Math.Tan(Half of fov) ) ) / (2*Math.PI) * 54544 / (Sensitivity) )

watch out for Blizzard notice if you're gonna keep your script on Github though.

Please specify
I want to try your method.
What is a FOV variable

[954612]

the fov is just the value in the graphics settings, the default is 103.

The method of calculation:

Math.Atan( (pixels to move) / ( (half of screen width) / ( Math.Tan(Half of fov) ) ) / (2*Math.PI) * 54544 / (Sensitivity)

^ A way to visualize the fov and the screen.

The 54544 is a full 360 degree mouse movement for 1 sens.

To calculate how much mouse movement needed, first calculate how much degree we need to turn.

A normal screen width is 1920 pixels, so the degrees we need to turn would be:

Math.Atan( (pixels to move) / ( ( half of screen width ) / ( Math.Tan( Half of fov ) ) )

= Math.Atan((pixels to move)/764.0)

but the result is in radians, so dividing by 2*PI times 54544/Sens would give us the mouse movement required.

[SeaDragon]

the fov is just the value in the graphics settings, the default is 103.

The method of calculation:

Math.Atan( (pixels to move) / ( (half of screen width) / ( Math.Tan(Half of fov) ) ) / (2*Math.PI) * 54544 / (Sensitivity)

^ A way to visualize the fov and the screen.

The 54544 is a full 360 degree mouse movement for 1 sens.

To calculate how much mouse movement needed, first calculate how much degree we need to turn.

A normal screen width is 1920 pixels, so the degrees we need to turn would be:

Math.Atan( (pixels to move) / ( ( half of screen width ) / ( Math.Tan( Half of fov ) ) )

= Math.Atan((pixels to move)/764.0)

but the result is in radians, so dividing by 2*PI times 54544/Sens would give us the mouse movement required.

pixels to move ＝ 100
half of screen width ＝ 1920
Half of fov ＝ 103
Sensitivity ＝ 15
Math.Atan (100 ÷ (1920 ÷ Math.Tan (103)) ÷ (2 × 3.1415926) × 54544 ÷ 15)
result= -1.529164 ??
Is it my step to be wrong

[SeaDragon]

pixels to move ＝ 100
half of screen width ＝ 1920÷2
Half of fov ＝ 103
Sensitivity ＝ 15
Math.Atan (100 ÷ (960÷ Math.Tan (103))) ÷ (2 × 3.1415926) × 54544 ÷ 15
result= -47.902342 ??
Is it my step to be wrong

[954612]

The Math.Tan's input should be in radians. Also it's half of fov not fov. So the calculations of 960/Math.tan(51.5 degrees) should be a constant ~763.6.

Math.Atan(100 / 763.6) / (2 × 3.1415926) × 54544 / 15 = 75 should be the right value to move in DllCall or mousemove etc.. functions.

[h4hitman]

One word. Gibberish

[SeaDragon]

The Math.Tan's input should be in radians. Also it's half of fov not fov. So the calculations of 960/Math.tan(51.5 degrees) should be a constant ~763.6.

Math.Atan(100 / 763.6) / (2 × 3.1415926) × 54544 / 15 = 75 should be the right value to move in DllCall or mousemove etc.. functions.

(pixels to move) is the center of the coordinates to the target coordinates of the straight line between pixels?

[954612]

Yes it's the center coordinate to target coordinate difference. Let's say your target is at (860, 640) and your crosshair (960, 540). The difference is (-100, 100), you then calculate how much you need to move in the two axis, the result should be (-75, 75).

[remaxz]

Anyone can teach or compile this?
I use vs 13,vs 15 and vs 16 and nothing!

I don't have any exp in Visual Studio.

[SeaDragon]

Yes it's the center coordinate to target coordinate difference. Let's say your target is at (860, 640) and your crosshair (960, 540). The difference is (-100, 100), you then calculate how much you need to move in the two axis, the result should be (-75, 75).

That is, the result is that I need to move the mouse to 885;615?
If I do not understand the wrong, then I test the results of the mouse to move too far away

[havoc1976]

I dont understand how some people cant compile this.
I use this method.
Open VS.
Create empty project.
Upon creating an empty project, you should see on the right, folders for header files/source files and so forth.
Select header files of the program and drag them to the folder in VS, do the same thing for source files.
Select the project, by clicking on it one, on the right side. Go to file, and do a save as in the same folder that you put the zip'ed program to. Build project,build solution and compile.
The folder that has the program, that you zipped to, should now have a debug folder. Open debug and you should have an exe file. run it. You need to do this every time you change something in the code.

[Zobb]

Resumed uni today so I decided to push another update to clean some things (just in case anyone is interested).

Most of the things that need to be fixed or implemented still remain:
- Mouse movements calculation improvements. I tried 954612's formula which works better when the number of pixels to be moved is large but it tends to overshoot/aim far away which messes with the program because it will end up making endless corrections. The program currently underaims and takes approx. 3 detections and mouse movements to get to the actual location which is really wasteful but I'm not mathematically good enough to solve this with ease so fk it :P.
- Detection of armor & shield bars for better calculation (couldn't obtain these because I literally only tested this out in the training range)
- Red border changing colour at far distances (we can resort moving the mouse to a set constant as a lazy solution)
- Threading

Thanks

[TheLordJesusHimself]

Thanks for the update i hope during your uni time and stuff you can fine some time to update this etc... you have made a good aim assist

Sent from my SM-G930F using Tapatalk

[lamejam]

stinkyjoint, is there anyway you could make this into something we can just launch and play with?