@Semih 3318  can you check scaling and screen resolution ?

@rbkadiyam how to check if botcreator resolution and botrunner resolution are the same? i think that might solve the issue, thanks

@Semih 3318 

You can get the screen resolution in execution time using different ways. Some approaches:

command dos

wmic path Win32_videoController get CurrentVerticalResolution,CurrentHorizontalResolution /format:value

Powershell

(Get-WmiObject -Class Win32_VideoController).VideoModeDescription;

Browse to 

https://whatsmyscreensize.com/

HTH

Regards

@Raul Jaimes  thank you for the reply, ill try that.

image recognition works on botcreator perfect, but on botrunner it tries to capture different area, it must be resolution problem i guess

Yes you are right @Semih 3318 make sure resolution is same as that of your Bot creator desktop

Permanent suggestion : Connect with your IT and ask them to set default resolution that matches your Bot creator one 

@Raul Jaimes when i wrote this command “wmic path Win32_videoController get CurrentVerticalResolution,CurrentHorizontalResolution /format:value” on command line, both botcreator and botrunner are 1024 and 768.

But the bot works fine on botcreator, not on botrunner.

@ChanduMohammad on commandline, i see that botcreator and botrunner are 1024 and 768.

i dont know what to change.

@Semih 3318 

Enterprise Client supports as 1366X768 minimum screen resolution. 

https://docs.automationanywhere.com/bundle/enterprise-v11.3/page/enterprise/topics/aae-client/bot-creator/creating-an-automation-task/using-the-standard-recorder.html

Some ideas:

-The screenshot was taken in a different screen resolution like 1366x768 or higher with botcreator

-Same VM for botcreator and botrunner?

-Recapure the screen area if it is a different VM. 

-Select the Run bot runner session on control room when you want the Control Room to use the RDP of the Bot Runner sessions and run it in its local memory. Check below reference:

https://docs.automationanywhere.com/bundle/enterprise-v11.3/page/enterprise/topics/control-room/activity/schedule-a-bot.html

-Verify if web browsers are using 100% zoom. ​

Let us know your feedback,

HTH

Regards

Hello @Raul Jaimes i am sorry,

i said they both were 1024*768, i just got that info on command line without running a bot.

Now i run the botcreator for having screenshot, it was 1920*1080

when i run the same bot on botrunner, it was 1920*1080 too

then what could be the issue?

Thank you for your feedback @Semih 3318 

As my previous post:

-Same VM for botcreator and botrunner?

-Recapure the screen area if it is a different VM. 

-Select the Run bot runner session on control room when you want the Control Room to use the RDP of the Bot Runner sessions and run it in its local memory. Check below reference:

https://docs.automationanywhere.com/bundle/enterprise-v11.3/page/enterprise/topics/control-room/activity/schedule-a-bot.html

-Verify if web browsers are using 100% zoom.

-Try using a different Match percentage and/or Tolerance

https://docs.automationanywhere.com/bundle/enterprise-v11.3/page/enterprise/topics/aae-client/bot-creator/commands/image-recognition-command.html

-An additional idea is recapture area in the VM where image recognition is failing and test again in the Vm where is working fine.

HTH

Regards

@Raul Jaimes thanks for the reply. When I said they both were 1920*1080, i run the task on botrunner itself, not on controlroom. As I see when i run it on controlroom, it changes to the setting which was set by default.

When i change it, it seems working, thank you

@Semih 3318  you can also set this screen resolution setting in control room for the machine

Manage → devices

Hello @rbkadiyam  you are right but it can be done on A360 as i know. On A11 is a bit different as in the picture i took the screenshot of.

@Raul Jaimes thanks for the reply. When I said they both were 1920*1080, i run the task on botrunner itself, not on controlroom. As I see when i run it on controlroom, it changes to the setting which was set by default.

When i change it, it seems working, thank you

 

welcome!.