- User Since
- Aug 12 2007, 10:08 PM (548 w, 6 d)
Jan 3 2018
No prob - weird though - has always been 100% reproducable for me, for literally years, and on multiple versions and operating systems - it's just that it's taken me several years to figure out why it was happening for me (being too 'close' to the object) - but I swear it's been there forever, and still is! XD
No worries though, I'll come back if I have any insights.
Nov 20 2017
Within the file, select any of the multiple objects in the viewport and move it using an axis constraint - you will find that the axis constraints function.
Now, zoom in to any object, with numpad period, or just zoom so that an object fills the viewport, and try using an axis constraint again - for me, the axis constraint disappears and the object's movement is not constrained at all.
Would be interested to see if anyone else can reproduce this?
Nov 6 2017
Here's a vid, hopefully will help explain, but still not how to reproduce :l This is actually happening in the default, non maximised 3d view now - I always thought it was only when in a maximised view, but perhaps it is to do with the wider field of view when maximised that makes it more prone to happen?
Ahah! I've found the cause!! So, happened again this morning, and I was almost considering making a video to show you what I meant, but while playing around with the 'bug' I finally realised that some objects would still constrain - then it dawned on me that those objects were further away - so, I zoomed out to move my problem object further away, and, lo and behold - axis constrain! So, I'm supposing it's a clipping plane thing? If the object is too close to the viewer, it is out of some operational clipping bounds and therefor doesn't get the constrain code?
Would you mind trying to recreate yourself? I am able to 'fix' the problem when it happens (by zooming out), but wonder if you are able to 'create' the problem by zooming in?