To all: this isn't a sales thread, stop asking me to sell, this is a question thread
same for me
You know coding is pretty basic and does all you ask to your hardware to do. Just check your loops and variables, there is 0 reason to move 200 instead of 10 pixel, w/e the language you are using. And yeah, you should do your aimbot in C++ , you can use any language for that work, this is just an aimbot, nothing really complicated in here.
I've changed to C++ and it is still giving me this issue, I guess I'm missing some checks somewhere @_@ not sure where though.
And yes I'm learning how to make a better aimbot
Not sure if this is the issue..
my in game mouse sensitivity is 3
0->screenshot and parse to analsys
1->analysis detect red pixel at 70x
2->the mouse tries to move -332.5x
3->before the mouse even finish moving, the screenshot method starts to run again
4->then it detects red pixel at 75(because the mouse is moving halfway)
5->then tries to move the mouse -320x
6->I am not sure if it's because the mouse is still moving -332.5pixels to the left and then this -320pixels to the left sort of interrupts/adds up together
Last edited by comic-1337; 07-25-2016 at 06:24 AM.
Problem with pixel is it could be jumping to anything red.
What method are you using to set mouse position.
SetPos (const Point& point)
SetPos (uint32 x, uint32 y)
Last edited by spoofjack; 07-25-2016 at 06:35 AM.
I'm sure it is not jumping to anything red except the red I want, 100% sure about that because I've did write image and seen the file written.
I'm using an arduino to move my cursor
You have to mess with your values a bit as mentioned here http://www.ownedcore.com/forums/fps/...g-mouse-c.html (How does Overwatch Mouse Sensitivity correlate to Moving the mouse with C++?) and you also have to multiply mouse movement on y by ~2.41 since yaw and pitch have different 'sensitivities' in overwatch and you're better off using "MOUSEEVENTF_MOVE" to move your mouse.
Last edited by atmos; 07-25-2016 at 08:03 AM.
can you pm me your skype, i like to buy your aimbot
Does setting the new mouse movement override the original? Or is it additive? You may need to have your mouse movement be handled as a "move towards this point", "the point moved, adjust accordingly" etc.
EDIT: Two separate threads will probably give the best performance. One to move the mouse to the last found point (if one exists) and the other to update the point via pixel searching.
Last edited by Sychotix; 07-25-2016 at 04:46 PM.
I guess the screenshot is faster than the mouse move function, I might be wrong but it looks like before the mouse even reached the point, the screenshot function is called again,
E.g screenshot0 ->mouseMoveTo (70,5)
Screenshot1->mouseMoveTo (65,3)
I THINK the mouseMove function is additive.
I tried to do a check whether the mouse has reached the end point by using while(mouse! =Endpoint){move}
But it just slows down the whole process alot
Will try multithreading next
Last edited by comic-1337; 07-25-2016 at 05:54 PM.