The constrain axis manipulator often fails to function when the 3d view is maximised #53212

Closed
opened 2017-10-31 11:14:01 +01:00 by Wayne Johnson · 24 comments

Blender Bugs

System Information
OSX 10.13
NVIDIA GeForce GT 755M 1 GB

Blender Version
Broken: 2.79
Worked: Never? spotted it about 7 years ago, but only just around to filing this!

Short description of error
The constrain axis manipulator often fails to function when the 3d view is maximised

Exact steps for others to reproduce the error

  1. Use Shift + Spacebar to take the 3d View into full screen
  2. Try to constrain the axis of an object's movement by dragging on one of the manipulator axis (red, blue or green arrows)
  3. You should find that the object's translation is not constrained as you would expect?
  4. …oh…works fine at the mo? I started this report yesterday and quit it, because I couldn’t reproduce….but the next morning I can!
  5. So, I am still not exactly sure ‘how’ to faithfully reproduce, but I definitely have again…

I think this is the reason I have never fully reported it, because I can’t figure out the exact cause. However, these things I know for sure….

3d View must be maximised (Shift+Spacebar)
Must be in Perspective view! Flipping back between Ortho and Perspective (Numpad 5) you can see that the Axis Constraint works fine in Ortho, but not in Perspective.

Once the bug is ‘found’, it is persistent…
You can ShitSpacebar back to normal UI, all will work, but if you immediately ShiftSpacebar back to maximised, the constraint will fail again.

Also, with regard to Blender version and operating system, I have noticed this bug for many, many years on multiple computers on both PC and Mac computers.
Hope you can find it! Will report back if I figure out the exact reproduction steps…
I currently have the bug in Edit Mode, but it can definitely happen in Object Mode too.
Cheers
Wayne

Blender Bugs **System Information** OSX 10.13 NVIDIA GeForce GT 755M 1 GB **Blender Version** Broken: 2.79 Worked: Never? spotted it about 7 years ago, but only just around to filing this! **Short description of error** The constrain axis manipulator often fails to function when the 3d view is maximised **Exact steps for others to reproduce the error** 1. Use Shift + Spacebar to take the 3d View into full screen 2. Try to constrain the axis of an object's movement by dragging on one of the manipulator axis (red, blue or green arrows) 3. You should find that the object's translation is not constrained as you would expect? 4. …oh…works fine at the mo? I started this report yesterday and quit it, because I couldn’t reproduce….but the next morning I can! 5. So, I am still not exactly sure ‘how’ to faithfully reproduce, but I definitely have again… I think this is the reason I have never fully reported it, because I can’t figure out the exact cause. However, these things I know for sure…. 3d View must be maximised (Shift+Spacebar) Must be in Perspective view! Flipping back between Ortho and Perspective (Numpad 5) you can see that the Axis Constraint works fine in Ortho, but not in Perspective. Once the bug is ‘found’, it is persistent… You can ShitSpacebar back to normal UI, all will work, but if you immediately ShiftSpacebar back to maximised, the constraint will fail again. Also, with regard to Blender version and operating system, I have noticed this bug for many, many years on multiple computers on both PC and Mac computers. Hope you can find it! Will report back if I figure out the exact reproduction steps… I currently have the bug in Edit Mode, but it can definitely happen in Object Mode too. Cheers Wayne
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @slowboy

Added subscriber: @slowboy

Added subscriber: @zeauro

Added subscriber: @zeauro

The fact that problem did not happen one day but was present next day makes me think that it might be relative to preferences or addons.

Next time, it happens try to save .blend file and to reload factory settings.

Currently, I did not succeed to reproduce on linux.

The fact that problem did not happen one day but was present next day makes me think that it might be relative to preferences or addons. Next time, it happens try to save .blend file and to reload factory settings. Currently, I did not succeed to reproduce on linux.

Added subscriber: @mont29

Added subscriber: @mont29

Am sorry, but we need a valid, stable way to reproduce an issue to investigate it. Cannot reproduce it here either (debian testing system with GTX850m and current NVidia drivers), this could be caused by a lot of stuff (buggy drivers, buggy hardware, …). First to try I’d say is to see if you can reproduce it on other systems (ideally same ones, or close to).

Am sorry, but we need a valid, stable way to reproduce an issue to investigate it. Cannot reproduce it here either (debian testing system with GTX850m and current NVidia drivers), this could be caused by a lot of stuff (buggy drivers, buggy hardware, …). First to try I’d say is to see if you can reproduce it on other systems (ideally same ones, or close to).
Author

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?
Thanks
Wayne

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? Thanks Wayne

Added subscriber: @AnthonyEdlin

Added subscriber: @AnthonyEdlin

Could not reproduce here on linux. Could be OS specific. File with bug happening for you would be needed.

Ubuntu 16.04.3 LTS
Blender 2.79 build master 66a6d16
NVIDIA 1080 driver 384.90

Could not reproduce here on linux. Could be OS specific. File with bug happening for you would be needed. Ubuntu 16.04.3 LTS Blender 2.79 build master 66a6d16 NVIDIA 1080 driver 384.90

Added subscriber: @fablefox

Added subscriber: @fablefox

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Fable Fox self-assigned this 2017-11-18 15:08:51 +01:00

Thanks for the report but it would be helpful if you add a blend-file to the report that demonstrates the issue at hand.

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.

Thanks for the report but it would be helpful if you add a blend-file to the report that demonstrates the issue at hand. Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.
Author

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'
Author

AxisConstraintsFails.blend
Very sorry for the late reply, guys - I somehow missed the request for an example file.
So, I've got one now, and reopened the bug, hope that's ok?

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?
Thanks
Wayne

[AxisConstraintsFails.blend](https://archive.blender.org/developer/F1163153/AxisConstraintsFails.blend) Very sorry for the late reply, guys - I somehow missed the request for an example file. So, I've got one now, and reopened the bug, hope that's ok? 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? Thanks Wayne

Added subscriber: @VukGardasevic

Added subscriber: @VukGardasevic

Some additional information was provided.

Marking as Needs Triage.

Some additional information was provided. Marking as Needs Triage.
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

cannot reproduce this, even with provided file (linux fedora 27, 970M with 384.98 drivers)

cannot reproduce this, even with provided file (linux fedora 27, 970M with 384.98 drivers)

Added subscriber: @FloridaJo

Added subscriber: @FloridaJo

I can't reproduce here on macOS.
Zoom in, zoom out, fullscreen, perspective, ortho, '.'
Constraint axis is always there for me.

I can't reproduce here on macOS. Zoom in, zoom out, fullscreen, perspective, ortho, '.' Constraint axis is always there for me.
Member

So, I think unless we find a reproducable case here [apparently this cannot be reproduced with provided file]: marking as incomplete again

So, I think unless we find a reproducable case here [apparently this cannot be reproduced with provided file]: marking as incomplete again
Author

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.

ps. Oh, by the way, Joel - it's definitely not an Ortho thing, 100% Perspective view - ortho is always fine.

Cheers
Wayne

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. ps. Oh, by the way, Joel - it's definitely not an Ortho thing, 100% Perspective view - ortho is always fine. Cheers Wayne

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

No point in keeping open something no developper can reproduce… Archiving for now, thanks for the report anyway.

No point in keeping open something no developper can reproduce… Archiving for now, thanks for the report anyway.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
8 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#53212
No description provided.