I have been wondering this for A LONG TIME. When selecting a point to modify, be it shape or line, etc. why doesn't microstation select the closest point to snap to. The images are trying to show what I mean. In image 1 I have selected a point on the blue shape, I want to move the point to the end of the yellow line. As you can see the First point it tries to find is the red dotted line (a reference file) and when I snap it goes to the red dotted line (image 2) THEN the Second Snap will go to the yellow line.
Why doesn't microstation select the closest point? Turning off Locate on the reference works but it doesn't answer the question. This happens even when I am working on files without references.
Is there maybe a setting to fix this?
Thank you
Hi Dbl,
To investigate this problem in detail, can you please send us the dgn file in which you are facing this problem?
Thanks,
Manoj
Manoj Sahani, thank you for your response. I apologize for not getting back sooner but I have had the flu :-(
I don't believe this is a dgn file issue. This has happened for a long time at different companies I have been employed by.
Thanks Jon Summers, but "snapping" isn't the issue because I can snap until I finally get the point I want I just would like the snap to go to the closest point rather than all of the other points that accusnap/accudraw will find.
Thanks Bob Rayner, I'll add that bit of info to my list on connect.
Dbl J D said:I don't believe this is a dgn file issue
Hi. Despite of it's probably not DGN issue, it can help to localize the problem better. Because when the test file will behave correctly on others computers, your HW/SW configuration (Windows version, graphic card and driver version..) and maybe also MicroStation configuration (corrupted upf, how locate tolerance is set...) would be discussed.
If you will share a test case, I recommend to use Saved View to exactly specify where "bad snap behaviour" can be tested.
With regads,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Dbl J D said:I don't believe this is a dgn file issue. This has happened for a long time at different companies I have been employed by.
If you mention about common snapping issue, it is already filed in Defect 744851.
I am asking for test case and steps to investigate your specific scenario properly.