PixelCheckSum working on PC, but not on laptop.

[DarthLobster]

Hello. I wrote a script which uses pixelchecksum to detect changes in a small region of my screen. It works fine on my desktop PC, but it does not seem to be working on my laptop.

I suspect it is getting the checksum of a different window. When I press alt+tab, the checksum detects a change. I have tried moving my cursor over the region, which should cause the checksum to change, but it doesn't register a change in the checksum of the region.

I am using a discrete graphics card on my PC and an integrated graphics chip on my Laptop. My PC is using Windows 11 and my Laptop is using Windows 10.

 

I tried changing the PixelCoordMode and tried forcing the hWnd in the function, but neither helped.

[ioa747]

I can only speculate.
They have the same resolution and the same scale layout?

[DarthLobster]

No, but that shouldn't matter - each machine has a separate configuration file which determines the region scanned. The checksums don't need to match each other across machines, they just need to register changes within specific regions on the screen.

I was searching for an hour or so earlier and saw somebody mentioning that PixelCheckSum can fail to run on a specific window and will run on the window beneath it, which I suspect may be what's happening, but I couldn't find any information about why that would happen or what I could do about it.

[ioa747]

One reason would be the elevated rights.

[Nine]

You may want to try my Screen Scraping UDF.

[DarthLobster]

5 hours ago, ioa747 said:

One reason would be the elevated rights.

I am running AutoIt as administrator, if that's what you mean.

 

Or would running the window I am trying to capture in administrator help? I don't believe I am running the window I am trying to capture as administrator on either machine, but I can try later.

[DarthLobster]

5 hours ago, Nine said:

You may want to try my Screen Scraping UDF.

While peeking at your thread there, it made me realize that my windows setting for window scaling was at 150% on my laptop, and I decided to try setting that to 100 to see if it made a difference, and it did. My script is working correctly now, I guess it was just looking in the wrong spot on the screen because of the window scaling. Very puzzling, because window scaling doesn't affect the application I'm running...