i have a bunch of guidepoints which are mapped with a gps plotter, and i need to select the point to move the group of points to a known reference point, but they keep being slightly not whre i want to place them.
this becomes oven more clear when i try to draw lines between the points, as i get the “snap to guide point” but i can see that the line is slightly off from the point.
which basically makes this whole thing useless and i cannot for the life of me figure out why this is so.
i have checked the unit settings and display settings, all seems good, but its weird behavior.
There’s no way of telling how much the edge endpoints are off of the guidepoint.
But… yes, they should coinside.
What you might try is rotating the drawing axes to some arbitrary orientation. In a way that drawing a new edge from first location to your target guidepoint will not be close to one of the axes orientations. Otherwise an axis orientation might “get the better hand” over the guidepoint due to inferencing and SketchUp’s angle tolerance.
It is worth a try.
I’ve seen this recently on a couple of machines that were a little bit too low in term of ressources. the engine worked fine most of the time, but they has the same problem you do (and it was not distance related)
if switching engine works, you might want to go to Nvidia’s website (or the Nvidia app) and check for a driver update.
windows pushes driver updates only for big versions, it won’t push all the smaller bugfixes.
Note also that in a model with lots of geometry (points, edges…) the inference engine detects a lot of inference points so it is important to slow down between clicks and observe closely what the inference tooltips have to say. It is often necessary to move the cursor around for a bit until you get the correct inference instead of a “from point…” type one. I have often suggested that the user should have an option to turn off unneeded inference types. In a 3D environment, though, some type of inference is mandatory.
