Possible bug with PixelSearch on AMD latest crimson update 17.6.1

Report problems with documented functionality
pevecg
Posts: 5
Joined: 11 Jun 2017, 04:47

Possible bug with PixelSearch on AMD latest crimson update 17.6.1

11 Jun 2017, 04:54

My script is lagging on the latest AMD driver update. It makes the windows explorer unusable and the script doesn't work anymore in the game I am using it. Reverting back to the previous drivers makes the script working again.

Code: Select all

#NoEnv  ; Recommended for performance and compatibility with future AutoHotkey releases.
Coordmode Pixel, Screen
MyNumber=0
MyRandom=0
start:
PixelSearch, Px, Py, 788,1047, 795, 1060, 0x72CC72,0,
if ErrorLevel
	Sleep, 100
else
	Sleep, 200

if(Px>>0 && Py>>0)
{
Px=0
Py=0
IfWinNotExist ahk_exe GTA5.exe
    return
; Otherwise, the above has set the "last found" window for use below.
ControlSend, ahk_parent, k  ; Pause/Unpause
Sleep, 12000
if(MyNumber=1)
{
WinGet, original, ID, A
WinActivate, ahk_exe GTA5.exe
Sleep, 100
SetKeyDelay, 150, 500
Random, MyRandom, 1, 3
if(myRandom=1)
{
Send A
Send D
}
if(myRandom=2)
{
Send A
}
if(myRandom=3)
{
Send D
}
SetKeyDelay, 80, 80
WinActivate, ahk_id %original%
MyNumber=0
goto nadaljuj
}
MyNumber=1
nadaljuj:
ControlSend, ahk_parent, Y
Sleep, 300

}

goto start
Return
just me
Posts: 9452
Joined: 02 Oct 2013, 08:51
Location: Germany

Re: Possible bug with PixelSearch on AMD latest crimson update 17.6.1

11 Jun 2017, 05:07

So it seems to be a driver bug, doesn't it?
pevecg
Posts: 5
Joined: 11 Jun 2017, 04:47

Re: Possible bug with PixelSearch on AMD latest crimson update 17.6.1

11 Jun 2017, 05:41

Yes, I just wanted to report it, incase devs can do anything to help it.

Return to “Bug Reports”

Who is online

Users browsing this forum: No registered users and 47 guests