visionFind dpi_96

Hello,

What affects the dpi of the visionFind image file?

All of a sudden the images are not being found and when I select a new image, it’s making files titled dpi_87 instead of dpi_96.

Thanks in advance.

With the imageName_dpi_XX UIV RPA stores the DPI of the screenshot image, which is the DPI of your screen. It uses this information to ensure visual UI test macros are compatible between different systems. So if you take your macro from a typical laptop (dpi 96) to a HiDPI system (e. g. macbook or surface laptop) it automatically scales the images up or down, so that they are found.

Now, why UIV now uses 87 dpi instead of 96 dpi is a bit strange. Some questions:

  • Is this a different machine?
  • Did you change any screen scaling recently? (that should not affect the recognition, but maybe there is a bug)
  • Are you testing the images on the same machine as you created them?

Same machine.
Same scaling.

Yes, this is very odd. This started out of the blue (or at least so it seems to the naked eye.)

I restarted the computer and I’m still getting dpi_87

It’s like something stopped working correctly with image recognition altogether.

Shall I uninstall and re-install the chrome extension?

Yes, please do. It will be very interesting to hear if this fixes the issue.

I had to create a new Chrome profile and install UI.Vision there.

Thank you.


Update 2023: Please note that uninstalling and reinstalling UI.Vision does not solve the issue. You must create a new Chrome profile and install the extension there.

That is surprising - thanks a lot for this helpful feedback!

I am having this problem too. However a reinstall did not help. Any other suggestions? I have tried to:
a) Reboot machine
b) Change resolution to something else and back again.
c) Reinstalled UI.Vision.

Need 96 dpi - but I keep getting 87 every time I try to create a new image.

Best regards,
Magnus

1 Like

Hello @mskoua - just to clarify:

Unfortunately the “DPI changed to 87” issue still happens in 2023, as we just confirmed. It happens rarely but it does happen. We are not sure yet what triggers it. But if that happens it breaks the image search as the “87dpi” value is wrong (96dpi would be correct). The good news is that the “Create new Chrome profile” fix also still works :wink: