Revit 2025 architecture snapping issues

[Romain_MarquesEB23K]

Hi All,

We have been struggling in the office for a couple of months now where it got really difficult to snap onto objects. We are a few hundreds in the office and we all have the same problem irrespective of project, scales etc. It also started exactly at the same time for all of us. We all work on virtual machines and use revit 2025. The graphic drivers have been updated several times, we upgraded to windows 11, tried a variety of different settings on revit and there has been no improvement at all. The issues we are facing are the following:

1- when drawing/modelling, it became very hard to snap to anything. You need to get really close to the line/point/etc for the cursor to snap to it, and I mean a few pixels..

2- when moving/copying etc, the same happens and it gets very difficult to grab onto anywhere.

3 - Same thing with moving views on a sheet, it is very difficult to grab onto an alignment.

Would be most helpful if anyone can share any insight on this.

Regards,

Romain

[Pavankumar_H · Accepted solution]

Hello @Romain_MarquesEB23K ,

Thanks for reaching out to us on Forums. 

Based on your description — especially that the issue started at the same time for a large number of users working on virtual machines — this is very unlikely to be a Revit-specific issue. It strongly points to an environment-level change affecting cursor precision, most commonly related to DPI scaling or remote input handling.

I would recommend checking the following:

1. Check Windows Display Scaling (DPI)
   Go to Windows Settings → Display → Scale and test with 100% scaling. Also verify that no scaling is being enforced through group policies. Higher scaling values such as 125% or 150% can significantly reduce the effective snap area in Revit.

2. Review Virtual Machine / Remote Display Settings
   Since all users are on VMs, check for any recent updates to Citrix, VMware, Azure Virtual Desktop, or Remote Desktop. Review display resolution and scaling settings within the VM and test both full screen and windowed modes. Any mismatch between host and VM scaling can impact cursor accuracy.

3. Validate Mouse / Input Behavior
   Test different mouse settings such as pointer speed and ensure acceleration is turned off. If your VM platform supports it, try switching between hardware and software cursor modes. If possible, compare behavior on a local (non-VM) machine to isolate the issue.

4. Verify Revit Snap Settings
   In Revit, go to Manage → Snaps and ensure required snap options are enabled. Also check the snap radius setting (typically around 10 pixels) to confirm it has not been reduced.

5. Identify Recent Central Changes
   Since the issue started simultaneously for all users, coordinate with IT to identify any recent changes such as a Windows 11 rollout, VM image updates, or policy changes affecting display scaling or input behavior. The root cause is most likely tied to a centralized update.

In summary, this issue is typically caused by DPI scaling or VM display/input mismatches, which reduce the effective snap detection area and make snapping require very precise cursor positioning.

Kindly, click on 'Like' or 'Accept Solution' if this has led you to direction in order to resolve the raised issue.
Thank you!

[Romain_MarquesEB23K]

Hi Pavankumar,

I will be trying your suggestions, thank you for replying to the post. I wanted to ask though, where can I find the snap radius setting in revit? that sounds like it could be an easy solution to this problem.

Cheers,

Romain

[David_W_Koch]

On the Manage ribbon tab, on the Settings panel, choose the Snaps tool.  Modify the Length dimension snap increments values.

[Romain_MarquesEB23K]

Oh I see, yes we tried that but it makes no difference. Pavankumar was mentioning a snap radius in pixels which is exactly what we would need. The current snap radius is 1 or 2 pixels at most, so to be able to change that in revit would probably solve our issue.

Regards,

R

[navya_gelli]

Hi @Romain_MarquesEB23K ,

I wanted to check in and see if you still needed assistance, or if you found a solution to your question already? Let us know if you need further assistance by providing an update or if you have found a solution, please share it with the community so other members who may have the same question could learn from your experience.

All the best,

Navya | Community Manager

[Romain_MarquesEB23K]

Hi, no I havent found a solution yet but I believe it's not an autodesk problem, it's most likely a VM problem.

Regards,

R