14.1 BUG--FindImagePos/WaitScreenImage

armsys · Post by **armsys** » Tue Mar 18, 2014 1:52 am

When running 14.1, ALL previously successful codes with FindImagePos / WaitScreenImage fail catastrophically.
Now I have to reinstall back 14.0.18.
Please redress the bug ASAP. Thanks.

Post by **Marcus Tettmar** » Tue Mar 18, 2014 7:41 am

No. All my image recognition macros are working nicely in 14.1. None of the image recognition features have changed in 14.1.

And as it happens I made a video just last night showing how to use the image recognition features using 14.1. Works fine:

https://mjtnet.viewscreencasts.com/b788 ... 2fa7cfa8a5

As you can see everything is working swimmingly. This video was made last night using 14.1

Oh and when you say "fail catastrophically" can you be more precise? Is there loss of life? Any error messages? What values are returned? What do you see in the watch list?

armsys · Post by **armsys** » Tue Mar 18, 2014 7:52 am

Hi Marcus,
I just sent you an email showing you a fatal error screenshot.
Line xx - Cannot find image file in FindImagePos/WaitScreenImage
Can other users corroborate my bug report?

BTW, a sample line:
WSI>C:\ArmSys\Macro Scheduler\Image\ejfq.bmp

Post by **Marcus Tettmar** » Tue Mar 18, 2014 8:06 am

Doesn't make any sense. Seriously, there have been *NO* changes to the image recognition code!

Are both versions installed in the same place? Are you referencing the images using an absolute path or relative to the script?

Can you post your script? What happens if you use IfFileExists to check the existence of the bitmap file before the WaitScreenImage command.

armsys · Post by **armsys** » Tue Mar 18, 2014 8:16 am

>Can you post your script?
Of course:

Code: Select all

IfFileExists>C:\ArmSys\Macro Scheduler\Image\ejfq.bmp
    MDL>Yes
Else
    MDL>No  
Endif

Let>WSI_TIMEOUT=5
Let>WW_TIMEOUT=10
Let>Win=EJFQ - Mozilla Firefox

IfWindowOpen>%Win%
  SetFocus>%Win%
Else
  Macro>%Script_Dir%\FireFox.scp
  WaitWindowOpen>EJFQ - Mozilla Firefox
  WSI>C:\ArmSys\Macro Scheduler\Image\ejfq.bmp
Endif

Yes, both v14.1 and v14.0.18 confirms the file exists.

>Are both versions installed in the same place?
Only one version of Macro Scheduler is installed, either 14.0.18 or 14.1, not both.

Post by **Marcus Tettmar** » Tue Mar 18, 2014 8:22 am

Looks like you have some parameters missing - tolerence and algorithm:

WSI>C:\ArmSys\Macro Scheduler\Image\ejfq.bmp,0.7,CCOEFF

Post by **Marcus Tettmar** » Tue Mar 18, 2014 8:30 am

Though that doesn't explain why it works in .0.18 but not in .1. Let me double check the code - I wasn't aware that anything had changed but it looks like something has.

armsys · Post by **armsys** » Tue Mar 18, 2014 8:42 am

BTW, all images used in my Macro Scheduler scripts are created by SnagIt, not Image Recognition Wizard.
BTW, following your tutorial video, a test script generated by the Image Recognition Wizard does work like a charm.
For all practical purposes, I can't go thru hundreds of scripts to re-generate the FindImagePos and WaitScreenImage by the Image Recognition Wizard again.
My only solution is to stick to 14.0.18 for the time being.

Post by **Marcus Tettmar** » Tue Mar 18, 2014 8:48 am

I'm trying to find out what changed.

However, you should always use the built in capture tool or wizard to capture your images. Other tools may use different color depths etc. If you use a different tool we are unable to guarantee results and would not be able to support that.

armsys · Post by **armsys** » Tue Mar 18, 2014 9:00 am

Marcus Tettmar wrote:you should always use the built in capture tool or wizard to capture your images.

That's exactly my worry--the only probable casue to the sudden 14.1 incompatibility.
Not sure if 14.1 can detect the minor nuances between the .bmp created by SnagIt and Macro Scheduler.
The reason I use SnagIt or Corel Paint is to crop the .bmp images.
Yes, I'll start using the Image Recognition Wizard in the future.

Post by **Marcus Tettmar** » Tue Mar 18, 2014 10:09 am

So I was wrong. It turns out there was an attempt to improve the error message that is produced if either the needle or haystack images aren't found. However, it caused this issue with legacy code where tolerance and algorithm are not specified. This has now been fixed in 14.1.01 which you can download now.

armsys · Post by **armsys** » Tue Mar 18, 2014 10:24 am

Marcus Tettmar wrote:This has now been fixed in 14.1.01 which you can download now.

Thanks for your fast fix.
Please re-check with your 14.1.01 on your server. It's ZERO byte.
Thanks.

Post by **Marcus Tettmar** » Tue Mar 18, 2014 12:12 pm

Seems ok here. Pls try again.