Very slow pixel search on Windows 10

[rimmi2002]

Hi,

I have been using auto it for a very long time on Windows 7 to automate many things. I needed due to a medical problem with my wrists. I just switched over to Windows 10. The script is running very slow. The problem has boiled down to the pixelsearch() function which runs very slow.

When I compared the speed of the pixelsearch function  on Windows 7 to Windows 10 there are about 16,000 calls to the function in one second on Windows 7 and only 30 calls to the function in one second on Windows 10.

Is there any way to remedy this? I really need the pixel search function for many of my tasks. I am running Windows 10 Pro 64-bit. Thanks for your help in advance.

[JLogan3o13]

@rimmi2002, the problem is on line 7.

In all seriousness, you cannot possibly expect anyone to troubleshoot code you are not going to share, can you?

Edited January 6, 2019 by JLogan3o13

[rimmi2002]

5 minutes ago, JLogan3o13 said:

@rimmi2002, the problem is on line 7.

In all seriousness, you cannot possibly expect anyone to troubleshoot code you are not going to share, can you?

Func ptest()
    $t = TimerInit()
    $n = 0
    While TimerDiff($t) < 1000
        $n += 1
        pixelsearch(500, 500, 500, 500, 0)
    WEnd
    ConsoleWrite($n & " Repetitions done" & @CRLF)
EndFunc   ;==>ptest

 

This is the code, I used to test how fast the function is running. In Windows 7 I get a result n ~= 16,000s. In Windows 10 n = 30.

This is the main reason my whole script is running at a super slow speed. My script is basically a very large script that detects pixels on the screens and automates stuff based on what I say to Dragon dictate. DragonDictate communicates to auto it through the hotkey function. The main program works fine however what used to happen in milliseconds now takes minutes. This trip still runs fine on Windows 7. This is a problem unique to Windows 10. I have seen some other threads on this. I couldn't find a solution that works yet. I was wondering if anyone knew of any?

Edited January 6, 2019 by rimmi2002

[Nine]

I had some problems at one time with Aero Glass Transparency,  Have you enable something like that ?  You could also try using 16bits colors instead of 32.  It must be related to your configuration.  Try different setups. 

[rimmi2002]

14 minutes ago, Nine said:

I had some problems at one time with Aero Glass Transparency,  Have you enable something like that ?  You could also try using 16bits colors instead of 32.  It must be related to your configuration.  Try different setups. 

I tried turning off the Aero Glass transparency. No success. Anything else worth trying? The 16-bit in the 32-bit color I already tried, no difference. On Windows 7 I was running 32-bit color. It was running fine on that.

[rimmi2002]

I guess upon further research I see the problem has also been mentioned here on the forums. I still have not found a solution. It would be highly appreciated if someone from the developing team can somehow remedy this.

 

 

[eXskill]

@rimmi2002 you are not alone in this problem)) I also can not get a good pixelsearch function performance.

Workaround use FastFind:

Local $FFDllHandle = DllOpen("FastFind64.dll")

DllCall($FFDllHandle, "int", "SnapShot", "int", "0", "int", "0", "int", "1920", "int", "1080", "int", "0")

$color=DllCall($FFDllHandle, "int", "FFGetPixel", "int", $xt, "int", "0", "int", "0")[0]

Edited September 27, 2019 by eXskill

[Mysticdrew]

Fastfind is what I had to resort to using. However, possible solutions can be found here. 
https://www.autoitscript.com/forum/topic/126430-advanced-pixel-search-library/page/18/?tab=comments#comment-1328566