"Find/Search Image on Screen & Move Mouse" action orders of magnitude slower since v6.868 (and possibly later)

sm1ng · October 13, 2026, 10:57am

Hi Andreas,

I use this action extensively throughout my routines and what I've noticed is that roughly 1 to 2 weeks ago, image recognition slowed down by orders of magnitude from approximately an average of 300 ms to 1-7 seconds.

In order to see if the culprit is perhaps the new zoom-friendly functionality that you added as part of feature request "Enhance "Find/Search Image on Screen & Move Mouse" action to recognize the image when it's zoomed in/out (e.g. by browser zoom level)", I downloaded the build from September 28 (6.868) and sure enough when I executed a routine with six image recognition actions, it executed in the blink of an eye. I repeated the test several times, because there are the vestiges of a half decent scientist within me somewhere, and obtained the same result. I then put the new version back and sure enough the image recognition slowed down dramatically as mentioned earlier.

I won't pretend to know what to suggest to you in terms of remedial action, I just wanted you to know that the existing action has been severely degraded. Going back precisely on what I just said, I for one one would appreciate a new build with the new Zoom-friendly functionality hidden behind a config flag or similar.

Many thanks as always,

Peter

Type of Mac:MBP M1 16"

macOS version:27.0.1

BetterTouchTool version: 6.921

Andreas_Hegenberg · October 13, 2026, 11:03am

that is weird, they it still seems to be near instant here. You didn't change the matching method to one of the newly added ones, correct? (because they might be slower).

I'll check whether anything could cause it to use one of the new algorithms by accident

Andreas_Hegenberg · October 13, 2026, 11:11am

I just ran my test suite for this across both the old build and new build. On my machine there is no difference in speed if the same algorithm is used.
I also checked the code, both versions execute exactly the same code if the "Template Matching" algorithm is selected, so I guess the issue can't really be related to the "Find/Search Image" action.