I’m currently experiencing issues with trying to indicate targets on screen. My system runs fine while in studio but as soon as I select to indicate on screen and the overlay appears, my mouse moves incredibly slow. It appears to lag and it takes about 1 -2 mins for my mouse to stop move to either allow me to select or Esc out of the indication process. It doesn’t appear to be my computer since I can still see programs functioning just fine in the background. I will also note that everything seems to work fine as well if the overlay is up and I happen to move my mouse across the UiPath studio window.
I’m unable to find anything related to this in the forum or the documentation.
Any ideas as to what is causing this?
Hi @tdoneal91 ,
A common cause of this issue in UiPath Studio is a conflict between the modern screen overlay, graphics/display drivers, or high DPI/multiple monitor settings.
You can try with the following solution:
Update UiPath Studio to the latest version.
Update your graphics driver (Intel/NVIDIA/AMD).
Try disabling Hardware Acceleration in UiPath Studio settings.
If using multiple monitors, try indicating targets on the primary monitor only.
Check Windows display scaling (set temporarily to 100%).
Disable any screen recording, remote desktop, or overlay applications that may interfere with screen detection.
Test by switching between Modern and Classic design experience to see if the issue persists.
If the problem only occurs during target indication and nowhere else, it is most likely related to the display/graphics rendering used by UiPath’s indication overlay rather than your computer’s performance.
First, try updating the UiPath.UIAutomation.Activities package to a version compatible with your installed Studio version.
If you’re using a newer UI Automation package with an older Studio version, package/Studio compatibility issues can sometimes cause unexpected behavior during target indication.
During “Indicate on screen,” Studio does a live UI Automation tree traversal under the cursor to draw the highlight rectangle, on every pixel of mouse movement. If the target window/app has a heavy or deeply nested UI tree, that traversal blocks the hook thread and the cursor appears to crawl.
Try and see if your issue is resolved through these steps below:
Use F2 to freeze indicate to hold Ctrl or press F2 to pause the live element scan, move the mouse to position, then release/press again to resume. This sidesteps the live-tree-walk-per-move lag entirely.
If you are using different monitors and if they have different scaling %, the overlay recalculates coordinates per move; setting all displays to the same scaling (or 100%) has fixed this for others.
Check UI Automation vs Active Accessibility framework in the target activity/project settings, try switching UI Framework (Default → UI Automation / Active Accessibility) to see if one is faster for that specific app.
Update UI Automation Activities package, version mismatches between Studio and extension may cause an issue sometimes.
Graphics drivers, outdated GPU drivers cause overlay redraw lag in some environments; worth a quick check.
Update your graphics driver (Intel/NVIDIA/AMD). - done
Try disabling Hardware Acceleration in UiPath [Studio] - I haven’t found the option to remove it in the settings
If using multiple monitors, try indicating targets on the primary monitor only. - I have done this as well
Check Windows display scaling (set temporarily to 100%). - Monitor is on 100%
Disable any screen recording, remote desktop, or overlay applications that may interfere with screen detection. - I disabled Nvidia overlay and Xbox game bar just in case
Test by switching between Modern and Classic design experience to see if the issue persists. - I thought I don’t have the option to switch between designs with the version I’m currently using
Try and open the Performance tab in your Task Manager and watch how ressources on your machine are affected when trying to indicate.
If you experience spikes then perhaps the UiPath Studio installation is “faulty” and you could consider a re-install.
Perhaps run CCleaner after the uninstall to clean up files and registry before re-installation.