RVT2025:cursor too precise on revit 25 in windows 11

RVT2025:cursor too precise on revit 25 in windows 11

l_cart
Explorer Explorer
4,768 Views
16 Replies
Message 1 of 17

RVT2025:cursor too precise on revit 25 in windows 11

l_cart
Explorer
Explorer

Hello everyone,

 

Since our office switched from windows 10 to windows 11, we've had a problem with cursor precision.
It has become too precise (see attached images).
We asked support but unfortunately, their solution didn't work.
The solution is to adapt the Snaps settings in the manage tab.
Have any of you already encountered this problem?
We're working on an omniscia horizon virtualized environment and on W11 with A2 and T4-8Q graphics cards. When we were on W10 with Rvt25 we didn't have this problem.

Thanks in advance!

 

0 Likes
4,769 Views
16 Replies
Replies (16)
Message 2 of 17

HVAC-Novice
Mentor
Mentor

From the images it isn't clear what "too precise" means. Can you elaborate? 

 

Does the cursor behave differently in Revit vs. Windows or other applications? Did you try the W11 mouse/cursor settings? Are you using a mouse with separate settings for pointer speed, resolution etc. (Like my wireless Logitech mouse does). 

 

And was that upgrade to W11 a fresh installation or an in-place upgrade? I don't think this is related to your issue, but in-place upgrades are just another cause for issues. 

Revit Version: R2026.4
Hardware: i9 14900K, 64GB, Nvidia RTX 2000 Ada 16GB
Add-ins: ElumTools; Ripple-HVAC; ElectroBIM; Qbitec
0 Likes
Message 3 of 17

l_cart
Explorer
Explorer

With the previous version of Windows, the default snapping allowed detection of the selection as shown in the attached image.


In the new version of Windows, even when adapting the snapping parameters, we can no longer adjust the cursor detection zone.
Users need to be very precise in their navigation, to be “pixel-perfect” on the line they want to select.


We tried enabling or disabling Enhance Pointer Precision on W11, but it didn't seem to reactivate snapping.

We've gone back to a new W11 image for our VDIs.

We have the latest version of revit 2025 ( Revit version: R2025.4)
All users have different mice (wired, wireless, different makes and models).

 

This over-precision is driving my colleagues crazy....

 

Message 4 of 17

azad.Nanva
Advisor
Advisor

did you uncheck the  "Enhance pointer precision" in mouse installing.

 

azadNanva_0-1738844178777.png

 

 

If it solves your problem, please click Accept to enhance the Forum.
0 Likes
Message 5 of 17

jwelch7QQ2K
Observer
Observer

I am still experiencing this issue - seemingly only occurs on Windows 11 VMs. Has anyone else found a solution to this issue? 

0 Likes
Message 6 of 17

kvermaEAZJ5
Explorer
Explorer

Checking in to report running into this as well, does anyone have an update on this issue?

0 Likes
Message 7 of 17

jwelch7QQ2K
Observer
Observer

I still don’t have a solution. Curious, are you running bare metal or on a VM?

0 Likes
Message 8 of 17

kvermaEAZJ5
Explorer
Explorer

VM similar to the OP, Horizon virtual instant clone environment.

0 Likes
Message 9 of 17

blesnau1
Enthusiast
Enthusiast

Curious if Autodesk has commented or reported on this issue.  Currently running into the same issue as our company has switched to Windows 11 and the hypersensitivity of the mouse cursor/pointer is completely hindering workflow.  The switch in operating systems seems to be the issue with Revit... maybe?


Open to suggestions!

0 Likes
Message 10 of 17

jostendorff
Contributor
Contributor

Our company recently switched to VMs.  This issue was fixed when IT turned off SVGA on the vmware side.

Message 11 of 17

jwelch7QQ2K
Observer
Observer

Going to try this - was this just disabled in Device Manager?

0 Likes
Message 12 of 17

jostendorff
Contributor
Contributor

We use Omnissa Horizon Client to access our virtual machines. In our case, the issue turned out to be a VMware display setting that needed to be disabled. I didn’t have access to that configuration, so our IT support team—who manages our VMs—had to make the change.

A quick way to check if you might be experiencing the same issue is to right-click on your desktop and open Display Settings. If you see more monitors listed than you actually have connected in the “Rearrange your displays” section, this could be the cause.

Our Horizon Client was initially set to use Horizon Blast, but switching to PCoIP worked as a temporary workaround (although the IT department wasn’t thrilled with that solution).

While I’m not an IT expert, I can say that Revit was nearly unusable until that setting was corrected. I spent quite a bit of time troubleshooting before IT confirmed the cause—after I shared a screenshot showing multiple phantom monitors appearing in Display Settings.

0 Likes
Message 13 of 17

blesnau1
Enthusiast
Enthusiast

This remedied the issue!!  A standing ovation and BIG "Thank You" to you for taking the time to respond to this.  Helped us out a ton!  Reference planes are showing correctly as well.

 

THIS IS THE FIX!

 

(at least for us - Running Omnissa Horizon Client on Windows 11)

0 Likes
Message 14 of 17

jwelch7QQ2K
Observer
Observer

Thanks for the insight. We do have the issue with additional monitors being showing in display settings, 3 monitor rather than the 2 physical displays in use. I am going to go ahead and open a ticket with Omnissa and see if we can get that issue resolved. Hopefully, it helps with the mouse issue. 

Did your IT happen to mention what the solution was or what the setting was that was causing the issue with multiple displays? Was the the SVGA in device manager?

0 Likes
Message 15 of 17

jostendorff
Contributor
Contributor

IT turned off SVGA on the vmware side. That fixed the extra monitors showing up and the Revit issue also.

0 Likes
Message 16 of 17

kvermaEAZJ5
Explorer
Explorer

We did remove the SVGA driver on our side but still seeing phantom displays. Is it possible this is from the Horizon indirect display adapter thats in place as well?

0 Likes
Message 17 of 17

kif9D6Z7
Explorer
Explorer

FYI, the root cause of this bug was identified and fixed when using the IDD driver, and will be addressed in the next release of Horizon.  A sandbox build is available through Omnissa support if a fix is required immediately.   There is a kb article on this issue:  https://kb.omnissa.com/s/article/6001433

0 Likes