Sikuli not finding what it should --- raise quality of captured images

Asked by Ross Parrent

I'm running Sikuli IDE 1.0.0 on Win7x64. I have noticed that after having executed a particular program several times, sikuli starts to "expect" or "anticipate" the location of particular regions, even if they are not visible where the target click point finds them, or they aren't visible at all (a different application is obscuring the target application, for example).
Is this an "image cache" that Sikuli is not really refreshing its internal ram with the actual, visible screen?
This is happening even after closing Sikuli and the target application and starting Sikuli first, then the target application.

TIA,
Ross Parrent

Question information

Language:
English Edit question
Status:
Solved
For:
SikuliX Edit question
Assignee:
No assignee Edit question
Solved by:
RaiMan
Solved:
Last query:
Last reply:
Revision history for this message
Best RaiMan (raimund-hocke) said :
#1

Sikuli always takes a new screenshot as base for the current find operation and repeats this during the given waiting time according to the scan rate (standard 3 times per second).

So the current Sikuli does not remember anything, that might lead to your observations.

I guess this is simply a similarity problem: you have "bad" shots, that lead to false positives, if the supposed targets are not visible, a common challenge with Sikuli.

Shots should have as little background as possible and concentrate on the visual aspects, that differentiate them from similar targets. The match score should always be above 0.9 (even better 0.95).

Revision history for this message
Ross Parrent (parrent) said :
#2

Thank you for your explanation. I look into it further. I may need to do a screen cast to demonstrate my experience so you can see what I see. I'll close the ticket for now. Thanks again.

Revision history for this message
Ross Parrent (parrent) said :
#3

Thanks RaiMan, that solved my question.