Announcements

Announcement: We’re aware of an issue affecting starting a new topic from category pages and creating new blog posts. New topics can still be started directly from the relevant board. Learn more here.

Object and vertex move command does not follow osnap trajectory

Object and vertex move command does not follow osnap trajectory

ODO18
Advocate Advocate
915 Views
2 Replies
Message 1 of 3

Object and vertex move command does not follow osnap trajectory

ODO18
Advocate
Advocate

Ok, I have looked everywhere for a solution and have come up empty and this has been driving me crazy so I am hoping someone can help me.  I will post pictures to try to illustrate what I am saying.  I am using Civil 3D 2015.

 

When I am making quick edit to lets say a rectangle that is 40'x50' and I want to make it 30'x50', I have always grabbed the vertex point and moving it 10' along any line that may be going the direction I want it to go, type in the distance and hit enter, and then the vertex will move in the direction of my osnap 10' as long as i am osnaping in the direction i want the vertex to move.  

Image 1.jpg

I will also move objects this same way.  I select move command, i will osnap along a line for directional start point, then osnap (but do not select) on another point along the line, type in the distance and the object will move in that distance along the trajectory of your two osnap points.

image2.jpgimage3.jpg

 

The issue is that this not what has been happening for the last month or so.  What happens is when I try to do either of these things, the vertex or object moves in the direction of my cursor rather then the osnap so sometimes it will be off my a visually unoticable amount.  It is as if the cursor is overriding priority over the osnap.

 

Any help would be great because I use this all the time and I have searched everywhere.  I am not sure if I am using the wrong terminology or what that is why I posted pictures.  I am hoping this is not a Civil 3D 2015 hotfix issue that has not been noticed yet, because I need this fixed asap.

 

Thanks

 

0 Likes
Accepted solutions (1)
916 Views
2 Replies
Replies (2)
Message 2 of 3

Jeff_M
Consultant
Consultant
Accepted solution

I noticed this yesterday myself, having just recently moved to C3D2016 from 2012. I found THIS older thread that suggests this was changed at the 2013 release and we must now have DYNINPUT on in order to use this process of obtaining the new location.

Jeff_M, also a frequent Swamper
EESignature
0 Likes
Message 3 of 3

ODO18
Advocate
Advocate

Thank you so much.  That thread explained it all.  Setting DYNMODE to 1 fixes it.

0 Likes