UI.Vision v10 and automatic scale factor (XClick with coordinates don't working)

Ui.Vision Bug Reports
,
1

Hello!, I like the new version 10 of UI.Vision and the AI panel for help, but I’m really needing to downgrave to a previous version cause the new XModules is doing something very weird that is not doing before, first let me say that I have upgraded to UI.Vision 10 cause I have restart my browser after days and days without needing to do it and then UI.Vision auto-updated to v10, it’s ok and is like all extensions works always, but it shows that I had no intentions to install the new version while there is “BETA” present in the version.

My previous version: 9.5.3
My new actual version: 10.0.218

My actual macro is working in Desktop mode.

I have installed the new XModules and I did all XModules tests and seems all ok, but I use mainly a macro that I created months ago that is mainly a canvas with all into it, so my macro need and have a lot of absolute XClick commands, all works with my macro in v9.5.3, I did no changes, but now my macro is not working in v10.0.218, what changed? only UI.Vision version, what’s the problem? seems like the new XModules automatically apply (without any chance to prevent it) a scale factor that previous XModules didn’t does.

In windows config I have it scaled to 125% (recommended) but I have it like this also in previous version and all works good, now in a XClick command to “2513,724” I see in log:
[info]

XClick → screen (3138, 905) [desktop scope, × 1.248527679623086]

Why is it doing it now and the user have no chance to control/modify it?, seems like now the new XModules is taking the Windows 125% scale and amplifying it and not clicking in the XClick coords that I have manually assigned (with a very good specific tool for get screen coords) but clicking in new coords cause the 125% scale from Windows, I want to say again: this macro works PERFECT in previous version and no changes is made to screen or anything, the only change is the update to v10 so the problem is the v10 or still more specific the new XModules.

For last I want to propose a small change, it’s really ok that the new XModules can intercept and apply the screen scale but, can better give more control to the users and add a new option in configs panel (and please a new internal variable for it like “!screenscale” or something) where the user can specify the screen scale to apply by the new XModules instead of apply the Windows values?.

Thanks you for read it and sorry for my bad english.

admin note:

  1. I have send this post to Bug Reports but I’m not sure of thinking that it’s a bug so, please, move it according to the type of post.
  2. I really like UI.Vision much more than old IMacros: long life for you, for all developers helping in UI.Vision and for UI.Vision project!

Cheers.

2

Thanks for the detailed report. And hello old iMacros user :blush:

Nothing is wrong with your Windows setup. In v9 the XModule worked in physical screen pixels, so a coordinate tool that shows physical pixels matched it. Since v10 desktop automation uses logical pixels, the same unit Ui.Vision’s own desktop screenshot shows, and the XModule converts to physical pixels once when it clicks. That is what the “× 1.25” in the log is.

For an existing macro, divide the old numbers by your display scale once (2513,724 becomes 2010,579), or re-take them from the v10 screenshot. Your report also led us to a real bug in 10.0.218: XClickText and XClick on an image in desktop mode were scaled twice at 125%. That will be fixed in the next update this week.

3

Thanks you my friend!.

Really the only solution is to convert all coords in prev version macros to the new XModules coords logical pixels?, I have more than 200 XClick commands in the macro… and I have lot of more macros using also the physical pixels screen coords also :man_facepalming: definitely I think that it’s better to go to v9 again for moment :frowning: , it’s bad that usually all tools uses physical pixels measures and too many ppl have all their macros with XClick to spicific coords in that format but now the only option is use logical pixels. :-1:

Don’t you consider to add some option in config for let users use physycal or logical pixels format? or the option and internal variable I mentioned that let users specify the scale factor instead of take it from Windows screen config?, everything that means let users control and customize their tasks is always the best option. :+1:

I’m really happy to help you to find the real bug in XClick and XClickText that apply the scale x2!! :slightly_smiling_face: :slightly_smiling_face: :slightly_smiling_face:

Hug for you my friend! :people_hugging:

4

Workaround: You could keep version 9 installed.

Or: Tools like Claude Fable or OpenAI Astra can easily convert the macro. They can even test-run it via the new MCP bridge.