AC3D Forums - View Single Post - NearSnap not working

jpadgett · 14th July 2011, 01:36 AM

I think I understand now - this quote from Andy above shows the way

"It will only work in 3D if you do not adjust the view between adding the initial vertices and the new ones that snap on to them..."

That is what I am seeing. It works in the 2D view, and only in the 3D view with verticies that are placed in the world before ANY changes to the 3D view orientation or position.

That being said...

I would find it EXTREMELY useful to have a function in the 3D view for creating polygons that would snap to the vertex that is nearest to the mouse cursor as seen from the current view orientation (and to ANY vertex in the world, not only to the vertecies placed there before changing the orientation)
This seems like a pretty simple thing to calculate (and thus to implement), however the computational complexity could get large with a lot of verticies in the world. Limiting the checks to only visible and unlocked objects would probably help this.

I can get by handily without this, there is always more than one way to do things, but I know I would find it very convenient.

BTW, thanks for a great and inexpensive product to the developers of this tool.

14th July 2011, 01:36 AM	#10
jpadgett Junior Member Junior member Join Date: Jul 2011 Posts: 3	Re: NearSnap not working - Linux version 6.8.14 I think I understand now - this quote from Andy above shows the way "It will only work in 3D if you do not adjust the view between adding the initial vertices and the new ones that snap on to them..." That is what I am seeing. It works in the 2D view, and only in the 3D view with verticies that are placed in the world before ANY changes to the 3D view orientation or position. That being said... I would find it EXTREMELY useful to have a function in the 3D view for creating polygons that would snap to the vertex that is nearest to the mouse cursor as seen from the current view orientation (and to ANY vertex in the world, not only to the vertecies placed there before changing the orientation) This seems like a pretty simple thing to calculate (and thus to implement), however the computational complexity could get large with a lot of verticies in the world. Limiting the checks to only visible and unlocked objects would probably help this. I can get by handily without this, there is always more than one way to do things, but I know I would find it very convenient. BTW, thanks for a great and inexpensive product to the developers of this tool.