New Way to Aimbot AHK PS4 Remote Play

[kaptainkook]

Hm, I guess remoteplaypc doesn't normalize/convert it to a value between -1+1 and instead interprets the mouse_event as a literal movement of that magnitude.
This shouldn't work very well, but will tell if that's the issue, replace the dllcall with this,

moveAmount := 1 ;try smaller values as well (0.1, 0.5, etc), iirc you could only feed ints, but worth a try with floats
movex:= round(movex)
while (movex-=moveAmount != 0) {
	DllCall("mouse_event", uint, 1, int, moveAmount, int, 0, uint, 0, int, 0)
        ;mousemove, % moveAmount,0,0,r ;try this one too, incase remoteplaypc will interpret it the way we'd like it to
	sleep, 40
}

all this was doing was barely moving my mouse right (in game) by like a Millimeter

[atmos]

Did it do so gradually though or was it just 1 jerk of 1 millimeter? If the gradual part, then let's try to figure out how remoteplaypc translates mouse distance per axis to the normalized controller axis.
If not then the next thing I can think of to deal with the retardation would be just writing to memory and that might take a bit of time. Memory manipulations with remoteplaypc wouldn't be an issue though since it's entirely separate entity and we can do whatever we want with it.

[kaptainkook]

Did it do so gradually though or was it just 1 jerk of 1 millimeter? If the gradual part, then let's try to figure out how remoteplaypc translates mouse distance per axis to the normalized controller axis.
If not then the next thing I can think of to deal with the retardation would be just writing to memory and that might take a bit of time. Memory manipulations with remoteplaypc wouldn't be an issue though since it's entirely separate entity and we can do whatever we want with it.

yea it was gradual

[atmos]

muy cool, try swapping moveAmount to values greater than 1 and see if it moves more or the same and if more then see what's the upper boundary since I'm guessing some distance from center is translated as 'force' of 1 and -1 while distances between center and max distance are weighted with some value.
After the bounds are found, we'll need to figure out the max 'polling rate' and then it could/should be solved mostly.
Another test would be to run this, and see at which value exactly it's done a 360 spin and commenting the first loop and uncommenting the next to see the same for 180 degrees on yaxis

loop { ;360 spin on x-axis
        x := 1
	dllcall("mouse_event", uint, 1, int, x, int, 0, uint, 0, int, 0)
	sleep, 30
	tooltip % a_index
}
;~ loop { ;180 spin on y-axis, from facing looking down/ground to looking at sky/roof
        ;~ y := 1
	;~ dllcall("mouse_event", uint, 1, int, 0, int, y, uint, 0, int, 0)
	;~ sleep, 30
	;~ tooltip % a_index
;~ }

[kaptainkook]

muy cool, try swapping moveAmount to values greater than 1 and see if it moves more or the same and if more then see what's the upper boundary since I'm guessing some distance from center is translated as 'force' of 1 and -1 while distances between center and max distance are weighted with some value.
After the bounds are found, we'll need to figure out the max 'polling rate' and then it could/should be solved mostly.
Another test would be to run this, and see at which value exactly it's done a 360 spin and commenting the first loop and uncommenting the next to see the same for 180 degrees on yaxis

loop { ;360 spin on x-axis
        x := 1
	dllcall("mouse_event", uint, 1, int, x, int, 0, uint, 0, int, 0)
	sleep, 30
	tooltip % a_index
}
;~ loop { ;180 spin on y-axis, from facing looking down/ground to looking at sky/roof
        ;~ y := 1
	;~ dllcall("mouse_event", uint, 1, int, 0, int, y, uint, 0, int, 0)
	;~ sleep, 30
	;~ tooltip % a_index
;~ }

the numbers increase but the mouse movements dont...around 50 with the old code makes it turn in circles... would it be easier if you remoted in?

[Atchya]

muy cool, try swapping moveAmount to values greater than 1 and see if it moves more or the same and if more then see what's the upper boundary since I'm guessing some distance from center is translated as 'force' of 1 and -1 while distances between center and max distance are weighted with some value.
After the bounds are found, we'll need to figure out the max 'polling rate' and then it could/should be solved mostly.
Another test would be to run this, and see at which value exactly it's done a 360 spin and commenting the first loop and uncommenting the next to see the same for 180 degrees on yaxis

loop { ;360 spin on x-axis
        x := 1
	dllcall("mouse_event", uint, 1, int, x, int, 0, uint, 0, int, 0)
	sleep, 30
	tooltip % a_index
}
;~ loop { ;180 spin on y-axis, from facing looking down/ground to looking at sky/roof
        ;~ y := 1
	;~ dllcall("mouse_event", uint, 1, int, 0, int, y, uint, 0, int, 0)
	;~ sleep, 30
	;~ tooltip % a_index
;~ }

Does this work???????

[lox090]

Damn, this thread looked promising :x

[glidarn]

any update about this?

[lox090]

Any news on this?

[Survey]

Any updates?