New Way to Aimbot AHK PS4 Remote Play menu

User Tag List

Page 2 of 3 FirstFirst 123 LastLast
Results 16 to 30 of 40
  1. #16
    atmos's Avatar Contributor
    Reputation
    97
    Join Date
    Jun 2016
    Posts
    79
    Thanks G/R
    8/65
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Alrighty, those values look fine so that wasn't the issue.
    Try this and see what happens if anything,
    Code:
    setbatchlines, -1
    coordmode, pixel, client
    a_class := "ahk_class SDL_app"
    while (!winexist(a_class)) {
    	tooltip, Run RemotePlayPC
    	sleep, 100
    }
    winactivate, % a_class
    hd := winexist(a_class)
    GetClientSize(hd, w, h)
    center_x := w/2
    center_y := h/2
    MsgBox DwmGetPixel
    loop 50 { ;5 seconds of pixel values, value doesn't matter as long as it's changing
    	tooltip, % DwmGetPixel(center_x+a_index, center_y, hd)
    	sleep, 100
    }
    MsgBox PixelGetcolor
    loop 50 { ;5 seconds of pixel values
    	pixelgetcolor,f, % center_x+a_index, % center_y, rgb
    	tooltip, % f
    	sleep, 100
    }
    MsgBox DllCall mouse
    loop 50 { ;5 seconds of jerking the mouse
    	DllCall("mouse_event", "UInt", 0x01, "UInt", 20*((t:=!t)?1:-1), "UInt", 0)
    	sleep, 100
    		;~ mousemove, % (cx-(fx-search_x))*div, % (cy-(fy-search_y))*div, 0
    }
    MsgBox mousemove
    loop 50 { ;5 seconds of jerking the mouse
    	mousemove, % 20*((t:=!t)?1:-1), 0, 0
    	sleep, 100
    }
    MsgBox done
    exitapp
    rshift::exitapp
    2 different 'get pixels' that use different methods and 2 different mousemoves that use different methods.
    See if and which work.
    Last edited by atmos; 03-01-2017 at 11:56 AM.

    New Way to Aimbot AHK PS4 Remote Play
  2. #17
    kaptainkook's Avatar Member
    Reputation
    4
    Join Date
    Jun 2012
    Posts
    50
    Thanks G/R
    6/3
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by atmos View Post
    Alrighty, those values look fine so that wasn't the issue.
    Try this and see what happens if anything,
    Code:
    setbatchlines, -1
    coordmode, pixel, client
    a_class := "ahk_class SDL_app"
    while (!winexist(a_class)) {
    	tooltip, Run RemotePlayPC
    	sleep, 100
    }
    winactivate, % a_class
    hd := winexist(a_class)
    GetClientSize(hd, w, h)
    center_x := w/2
    center_y := h/2
    MsgBox DwmGetPixel
    loop 50 { ;5 seconds of pixel values, value doesn't matter as long as it's changing
    	tooltip, % DwmGetPixel(center_x+a_index, center_y, hd)
    	sleep, 100
    }
    MsgBox PixelGetcolor
    loop 50 { ;5 seconds of pixel values
    	pixelgetcolor,f, % center_x+a_index, % center_y, rgb
    	tooltip, % f
    	sleep, 100
    }
    MsgBox DllCall mouse
    loop 50 { ;5 seconds of jerking the mouse
    	DllCall("mouse_event", "UInt", 0x01, "UInt", 20*((t:=!t)?1:-1), "UInt", 0)
    	sleep, 100
    		;~ mousemove, % (cx-(fx-search_x))*div, % (cy-(fy-search_y))*div, 0
    }
    MsgBox mousemove
    loop 50 { ;5 seconds of jerking the mouse
    	mousemove, % 20*((t:=!t)?1:-1), 0, 0
    	sleep, 100
    }
    MsgBox done
    exitapp
    rshift::exitapp
    2 different 'get pixels' that use different methods and 2 different mousemoves that use different methods.
    See if and which work.
    This pops up trying to fix it myself New Way to Aimbot AHK PS4 Remote Play-aimbox-gif

  3. #18
    atmos's Avatar Contributor
    Reputation
    97
    Join Date
    Jun 2016
    Posts
    79
    Thanks G/R
    8/65
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Code:
    GetClientSize(hwnd, ByRef w, ByRef h) {
        VarSetCapacity(rc, 16)
        DllCall("GetClientRect", "uint", hwnd, "uint", &rc)
        w := NumGet(rc, 8, "int")
        h := NumGet(rc, 12, "int")
    }
    DwmGetPixel(x, y, hwnd) {
       hDC := DllCall("user32.dll\GetDCEx", "UInt", hwnd, "UInt", 0, "UInt", 1|2)
       pix := DllCall("gdi32.dll\GetPixel", "UInt", hDC, "Int", x, "Int", y, "UInt")
       DllCall("user32.dll\ReleaseDC", "UInt", hwnd, "UInt", hDC)
       return pix
    }
    Add these 2 after it, again goofed :'<

  4. #19
    kaptainkook's Avatar Member
    Reputation
    4
    Join Date
    Jun 2012
    Posts
    50
    Thanks G/R
    6/3
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by atmos View Post
    Code:
    GetClientSize(hwnd, ByRef w, ByRef h) {
        VarSetCapacity(rc, 16)
        DllCall("GetClientRect", "uint", hwnd, "uint", &rc)
        w := NumGet(rc, 8, "int")
        h := NumGet(rc, 12, "int")
    }
    DwmGetPixel(x, y, hwnd) {
       hDC := DllCall("user32.dll\GetDCEx", "UInt", hwnd, "UInt", 0, "UInt", 1|2)
       pix := DllCall("gdi32.dll\GetPixel", "UInt", hDC, "Int", x, "Int", y, "UInt")
       DllCall("user32.dll\ReleaseDC", "UInt", hwnd, "UInt", hDC)
       return pix
    }
    Add these 2 after it, again goofed :'<
    The last thing just points my camera up and 360's

  5. #20
    kaptainkook's Avatar Member
    Reputation
    4
    Join Date
    Jun 2012
    Posts
    50
    Thanks G/R
    6/3
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I think the 1st mouse move is just moving the mouse a little wiggle basically
    Last edited by kaptainkook; 03-01-2017 at 12:54 PM.

  6. #21
    atmos's Avatar Contributor
    Reputation
    97
    Join Date
    Jun 2016
    Posts
    79
    Thanks G/R
    8/65
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Did either of the pixel searches work? If yes then we might have cracked the mystery as on pc you had to divide the amount to move by million, but on ps4 (remoteplaypc) it seems like you might have to multiply by million.

  7. #22
    kaptainkook's Avatar Member
    Reputation
    4
    Join Date
    Jun 2012
    Posts
    50
    Thanks G/R
    6/3
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by atmos View Post
    Did either of the pixel searches work? If yes then we might have cracked the mystery as on pc you had to divide the amount to move by million, but on ps4 (remoteplaypc) it seems like you might have to multiply by million.

    Yea they both did

  8. #23
    atmos's Avatar Contributor
    Reputation
    97
    Join Date
    Jun 2016
    Posts
    79
    Thanks G/R
    8/65
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    In that case, all that you probably need to do with any aimbot is add another set of multipliers for x and y axis since the y axis is probably even more distorted on ps4.
    So, just add these 2 to the top area of any ahk aimbot script you find
    Code:
    ps4_xMult := 2
    ps4_yMult := 2
    And in the script where it moves the mouse, whether it's with dllcall, mousemove or whatever wrap the variables/values in parentheses and multiply that value by the respective values above, like so
    Code:
    DllCall("mouse_event", "UInt", 0x01, "UInt", (x+sensitivity)*PS4_xMult, "UInt", (y+sensitivity)*PS4_yMult)
    You'll definitely have to find the right multipliers for each and it'll be easier if you get one axis at a time by setting e.g. the "ps4_yMult" to 0 so you only get movement on x axis and vice versa.

    (Probably )
    Last edited by atmos; 03-02-2017 at 04:46 AM.

  9. #24
    kaptainkook's Avatar Member
    Reputation
    4
    Join Date
    Jun 2012
    Posts
    50
    Thanks G/R
    6/3
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by atmos View Post
    In that case, all that you probably need to do with any aimbot is add another set of multipliers for x and y axis since the y axis is probably even more distorted on ps4.
    So, just add these 2 to the top area of any ahk aimbot script you find
    Code:
    ps4_xMult := 2
    ps4_yMult := 2
    And in the script where it moves the mouse, whether it's with dllcall, mousemove or whatever wrap the variables/values in parentheses and multiply that value by the respective values above, like so
    Code:
    DllCall("mouse_event", "UInt", 0x01, "UInt", (x+sensitivity)*PS4_xMult, "UInt", (y+sensitivity)*PS4_yMult)
    You'll definitely have to find the right multipliers for each and it'll be easier if you get one axis at a time by setting e.g. the "ps4_yMult" to 0 so you only get movement on x axis and vice versa.

    (Probably )
    Code:
    setbatchlines, -1
    coordmode, pixel, client
    a_class := "ahk_class SDL_app"
    while (!winexist(a_class)) {
    	tooltip, Run RemotePlayPC
    	sleep, 100
    }
    hd := winexist(a_class)
    GetClientSize(hd, w, h)
    ps4_xMult := 2
    ps4_yMult := 2
    center_x := w/2
    center_y := h/2
    search_dim := 100
    search_x := center_x-(search_dim/2)
    search_y := center_y-(search_dim/2)
    ;;change stuff
    div := 0.116 ;decrease if it's too erratic, increase if too slow
    offset_x := 50 ;you probably have to change these
    offset_y := 50 ;you probably have to change these
    ;;change stuff
    MsgBox % "Press ok to 'start' bot.`n" a_class "|" hd "|" w "|" h "|" center_x "|" center_y "|" search_dim "|" search_x "|" search_y
    loop {
    	imagesearch, fx, fy, % search_x, % search_y, % search_x + search_dim, % search_x + search_dim, *80 1.png
    	if (!errorlevel) {
    		DllCall("mouse_event", "UInt", 0x01, "UInt", (x+sensitivity)*PS4_xMult, "UInt", (y+sensitivity)*PS4_yMult) ;;if this doesn't work, comment and uncomment next
    		;~ mousemove, % (cx-(fx-search_x))*div, % (cy-(fy-search_y))*div, 0
    	}
    	;no need to sleep here since the imagesearch takes longer than 1 frame anyway
    }
    rshift::exitapp
    GetClientSize(hwnd, ByRef w, ByRef h) {
        VarSetCapacity(rc, 16)
        DllCall("GetClientRect", "uint", hwnd, "uint", &rc)
        w := NumGet(rc, 8, "int")
        h := NumGet(rc, 12, "int")
    }

    I tired with that and it doesnt work...god I feel like we are so close!

  10. #25
    kaptainkook's Avatar Member
    Reputation
    4
    Join Date
    Jun 2012
    Posts
    50
    Thanks G/R
    6/3
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by atmos View Post
    In that case, all that you probably need to do with any aimbot is add another set of multipliers for x and y axis since the y axis is probably even more distorted on ps4.
    So, just add these 2 to the top area of any ahk aimbot script you find
    Code:
    ps4_xMult := 2
    ps4_yMult := 2
    And in the script where it moves the mouse, whether it's with dllcall, mousemove or whatever wrap the variables/values in parentheses and multiply that value by the respective values above, like so
    Code:
    DllCall("mouse_event", "UInt", 0x01, "UInt", (x+sensitivity)*PS4_xMult, "UInt", (y+sensitivity)*PS4_yMult)
    You'll definitely have to find the right multipliers for each and it'll be easier if you get one axis at a time by setting e.g. the "ps4_yMult" to 0 so you only get movement on x axis and vice versa.

    (Probably )
    Code:
    init:
    #NoEnv
    #Persistent
    #SingleInstance, Force
    #Persistent
    #InstallKeybdHook
    #UseHook
    #KeyHistory, 0
    #HotKeyInterval 1
    #MaxHotkeysPerInterval 127
    version = 2.0
    traytip, Sharpshooter %version%, Running in background! Aimspot = Torso > Aim is staying on target, 5, 1
    Menu, tray, NoStandard
    Menu, tray, Tip, Sharpshooter %version%
    Menu, tray, Add, Sharpshooter %version%, return
    Menu, tray, Add
    Menu, tray, Add, Help, info
    Menu, tray, Add, Exit, exit
    SetKeyDelay,-1, 8
    SetControlDelay, -1
    SetMouseDelay, -1
    SetWinDelay,-1
    SendMode, InputThenPlay
    SetBatchLines,-1
    ListLines, Off
    CoordMode, Pixel, Screen, RGB
    CoordMode, Mouse, Screen
    PID := DllCall("GetCurrentProcessId")
    Process, Priority, %PID%, High
    EMCol := [0xF2361B, 0xEF3519, 0xEE4131, 0xED4233, 0xEE4031, 0xCF8790, 0xCF878F, 0xD92411, 0xDC2613, 0xA24D53, 0xA84547, 0xB25C62, 0xAB545B] ;Color to search for, hex!
    ColVn := 50  ; Color Variations Allowed (higher number more colors allowed)
    AntiShakeX := (A_ScreenWidth // 160)
    AntiShakeY := (A_ScreenHeight // 128)
    ZeroX := 960
    ZeroY := 528  ; Higher The number the Higher The Shot
    CFovX := 92   ; Fov in pixel around crosshair
    CFovY := 92   ; Fov in pixel around crosshair
    ScanL := ZeroX - CFovX
    ScanT := ZeroY
    ScanR := ZeroX + CFovX
    ScanB := ZeroY + CFovY
    NearAimScanL := ZeroX - AntiShakeX
    NearAimScanT := ZeroY - AntiShakeY
    NearAimScanR := ZeroX + AntiShakeX
    NearAimScanB := ZeroY + AntiShakeY
    Loop, {
    KeyWait, LButton, D
    PixelSearch, AimPixelX, AimPixelY, NearAimScanL, NearAimScanT, NearAimScanR, NearAimScanB, EMCol, ColVn, Fast RGB
    if (!ErrorLevel=0) {
    loop, 1 {
    PixelSearch, AimPixelX, AimPixelY, ScanL, ScanT, ScanR, ScanB, EMCol, ColVn, Fast RGB
    AimX := AimPixelX - ZeroX
    AimY := AimPixelY - ZeroY
    DirX := -1
    DirY := -1
    If ( AimX > 0 ) {
    DirX := 1
    }
    If ( AimY > 0 ) {
    DirY := 1
    }
    AimOffsetX := AimX * DirX
    AimOffsetY := AimY * DirY
    MoveX := Floor(( AimOffsetX ** ( 1 / 2 ))) * DirX
    MoveY := Floor(( AimOffsetY ** ( 1 / 2 ))) * DirY
    DllCall("mouse_event", uint, 1, int, (MoveX * 1.35)/ .555, int, MoveY, uint, 0, int, 0)    ; MoveX * "1.35" (how fast the aimbot aims)
    }
    }
    }
    Return
    Pause:: pause
    return:
    goto, init
    info:
    msgbox, 0, Sharpshooter %version%, Made by erik96 `nGame must be running in borderless windowed mode.`nPress pause key to pause this program.`nLeft click automatically aims down target near the center of the screen.`nRecommended for near distance.`nTry 1920X1080 as resulution works best for me.
    return
    exit:
    exitapp
    Using this code it kinda works....

  11. #26
    atmos's Avatar Contributor
    Reputation
    97
    Join Date
    Jun 2016
    Posts
    79
    Thanks G/R
    8/65
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Try replacing the dllcall with this,
    Code:
    DllCall("mouse_event", uint, 1, int, (MoveX * 5)/ .555, int, MoveY, uint, 0, int, 0)
    I assume it should spaz out, which would be good.

  12. #27
    kaptainkook's Avatar Member
    Reputation
    4
    Join Date
    Jun 2012
    Posts
    50
    Thanks G/R
    6/3
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by atmos View Post
    Try replacing the dllcall with this,
    Code:
    DllCall("mouse_event", uint, 1, int, (MoveX * 5)/ .555, int, MoveY, uint, 0, int, 0)
    I assume it should spaz out, which would be good.
    yea it does

  13. #28
    atmos's Avatar Contributor
    Reputation
    97
    Join Date
    Jun 2016
    Posts
    79
    Thanks G/R
    8/65
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Then replace that with these 2 lines,
    Code:
    mult_x := 5 ;change this to lower, e.g. 4.5, 4, 3.5, 3, 2.5, etc etc.
    DllCall("mouse_event", uint, 1, int, (MoveX * mult_x)/ .555, int, MoveY, uint, 0, int, 0)
    and change the mult_x to lower values until it becomes stable.

  14. #29
    kaptainkook's Avatar Member
    Reputation
    4
    Join Date
    Jun 2012
    Posts
    50
    Thanks G/R
    6/3
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by atmos View Post
    Then replace that with these 2 lines,
    Code:
    mult_x := 5 ;change this to lower, e.g. 4.5, 4, 3.5, 3, 2.5, etc etc.
    DllCall("mouse_event", uint, 1, int, (MoveX * mult_x)/ .555, int, MoveY, uint, 0, int, 0)
    and change the mult_x to lower values until it becomes stable.
    i put the /.555 in becuz anything lower or higher either does nothing or spazzes out

  15. #30
    atmos's Avatar Contributor
    Reputation
    97
    Join Date
    Jun 2016
    Posts
    79
    Thanks G/R
    8/65
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    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,
    Code:
    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
    }
    Last edited by atmos; 03-07-2017 at 08:14 AM.

Page 2 of 3 FirstFirst 123 LastLast

Similar Threads

  1. LoLCamera : A new way to play!
    By Spl3en in forum League of Legends Exploits. Cheats, Hacks
    Replies: 5
    Last Post: 08-29-2014, 08:23 AM
  2. LoLCamera - A new way to play !
    By Spl3en in forum League of Legends
    Replies: 3
    Last Post: 12-18-2013, 07:08 PM
  3. New Way Under OG Post 1.11
    By Matt in forum World of Warcraft Guides
    Replies: 11
    Last Post: 07-13-2006, 10:53 AM
  4. new way to hyjal, very ez!
    By bloodofwar in forum World of Warcraft Exploits
    Replies: 9
    Last Post: 05-27-2006, 06:46 PM
All times are GMT -5. The time now is 09:17 AM. Powered by vBulletin® Version 4.2.3
Copyright © 2024 vBulletin Solutions, Inc. All rights reserved. User Alert System provided by Advanced User Tagging (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
Digital Point modules: Sphinx-based search