RoboTask forum

Despite I managed to not only disable the touchscreen within Windows, but also to disable it in BIOS, the offset is still there.
We've picked up a different laptop with full hd resolution (but no touchscreen), put the clone on there... and all good!

I think I've did that already.
I'll check tonight and let you know!

Meanwhile, you agree with me, that only such touchscreen is causing the offset right?
(Keeping in mind, that it is an image so all things like Windows zoom, layout in Word or Chrome etc. are identical.)

Hi Oleg, I hope you have more indepth knowledge on this topic, so I don't have to alter loads of actions. I got this nuc-pc with a normal monitor attached to it, win10 1920x1080. All scripts working fine, where I use screen pixels to determine whether something is loaded, or where to click on autopi...

I think you are right - the black CLI window shows a fraction, which is probably the culprit..
I've now set a DELAY of 200 ms in front, and so far it's solid.

Thanks again Oleg!
Consider it solved.

I have tried to replicate and even on 8 and 16 tolerance it still happens.
notice how 2017 is run (ok) and the next instance 2020 script (not ok) then after a few attempts 2017 is run again (ok)

https://i.imgur.com/BdDUbFe.mp4

Interesting.
I will set both to 8 tolerance to see if it won't occur this way.

NOTE:
I'm not using Remote Desktop or any other, also its not a laptop (which could change color due battery mode / dim-mode vs. when on electrical socket charger)

No I did not.
I gave up.

Perhaps you have a workaround?

Thanks Oleg! It works! :D See: https://i.imgur.com/PU9ZuWW.mp4 NOTE: - I changed it to the stated path, but then it wasn't able to find python3.exe - Then I changed it to where Python3.exe actually is , according to 'where python3' (without selecting it from the built-in explorer, so just typing the...

When I run it locally in CMD, it does work:
https://i.imgur.com/zfVOKBI.mp4

It is refering to chromedriver of selenium:


Which is located in the assigned path: