Navigation screen controls don't always work #67320

Closed
opened 2019-07-20 14:25:15 +02:00 by Chris Winslow · 9 comments

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce GT 540M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-18 14:52, hash: 38d4483c6a
Worked: (optional)

Short description of error
[The functionality of "Move the View" & "Zoom in/out in the view" icons fail to function as expected after using them to pan and zoom the screen over large distances.]

Exact steps for others to reproduce the error
[NOTE: You can enable or disable "Auto Depth" in the Preference> Navigation, The problem will still exist.

  • Open Blender and start by clicking on the General option on the splash screen.
  • Zoom in close to the cube and a little past it and zoom way out to the point it can't be seen, do this around 5 five times then while also panning the screen in any random direction, all while using the two icons in the navigation area.
  • Zoom out of the view of the cube but not too far that you can not see it, then use the XYZ Gizmos so the "Z" view is on top "X" in the centre and "Y" is on the right, then quickly pan the cube to the right of the screen then right using fast movements
  • Finally, pan/move the cube to the centre of the view and try to zoom into the cube and you should find that zooming in using the icon or the scroller on the mouse will get slower and slower, zooming out to will also be slow once zoomed it, the panning icon will also not work at all

]
[Based on the default startup, No files need to be attached as you can reproduce the error simply by using the default "General" screen on start up]

**System Information** Operating system: Windows-7-6.1.7601-SP1 64 Bits Graphics card: GeForce GT 540M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35 **Blender Version** Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-18 14:52, hash: `38d4483c6a` Worked: (optional) **Short description of error** [The functionality of "Move the View" & "Zoom in/out in the view" icons fail to function as expected after using them to pan and zoom the screen over large distances.] **Exact steps for others to reproduce the error** [**NOTE: You can enable or disable "Auto Depth" in the Preference> Navigation, The problem will still exist.** - Open Blender and start by clicking on the General option on the splash screen. - Zoom in close to the cube and a little past it and zoom way out to the point it can't be seen, do this around 5 five times then while also panning the screen in any random direction, all while using the two icons in the navigation area. - Zoom out of the view of the cube but not too far that you can not see it, then use the XYZ Gizmos so the "Z" view is on top "X" in the centre and "Y" is on the right, then quickly pan the cube to the right of the screen then right using fast movements - Finally, pan/move the cube to the centre of the view and try to zoom into the cube and you should find that zooming in using the icon or the scroller on the mouse will get slower and slower, zooming out to will also be slow once zoomed it, the panning icon will also not work at all ] [Based on the default startup, No files need to be attached as you can reproduce the error simply by using the default "General" screen on start up]
Author

Added subscriber: @chris_saturn

Added subscriber: @chris_saturn

Added subscriber: @ZedDB

Added subscriber: @ZedDB

Do you have Auto depth off in the navigation user settings?

Do you have `Auto depth` off in the navigation user settings?
Author

No, I have Auto depth switched on (ticked) in the user settings. But as I said, Auto depth makes NO difference if it is on or off in the user settings, as the zoom and panning controls fail and become stuck after a short while (within a few minutes normally) and this happens using the one screen icons or the mouse.

No, I have `Auto depth` switched on (ticked) in the user settings. But as I said, `Auto depth` makes NO difference if it is on or off in the user settings, as the zoom and panning controls fail and become stuck after a short while (within a few minutes normally) and this happens using the one screen icons or the mouse.

Can you attach a .blend file where you have gotten stuck like this?

Can you attach a .blend file where you have gotten stuck like this?

Added subscriber: @SpectreFirst

Added subscriber: @SpectreFirst

I think I can easily reproduce this on b63f0266a0 from 2019-07-23. This is how it works on my side:

  1. Open new scene
  2. Hold left mouse on “Move the view” icon and pan left or right
  3. Hold left mouse on “Zoom in\out in the view” icon and drag your mouse up. As a result both Pan and Zoom viewport controls will stuck and cease to function until you do something like Frame Selected or some other action that resets pan and zoom.

I have Auto Depth disabled by default but enabling it doesn't make any difference - pan right, zoom forward, get stuck. To be more precise, both controls seems to keep working but they are doing that by extremely small increments which can be easily mistaken for not working.

I think I can easily reproduce this on b63f0266a056 from 2019-07-23. This is how it works on my side: 1. Open new scene 2. Hold left mouse on “Move the view” icon and pan left or right 3. Hold left mouse on “Zoom in\out in the view” icon and drag your mouse up. As a result both Pan and Zoom viewport controls will stuck and cease to function until you do something like Frame Selected or some other action that resets pan and zoom. I have Auto Depth disabled by default but enabling it doesn't make any difference - pan right, zoom forward, get stuck. To be more precise, both controls seems to keep working but they are doing that by extremely small increments which can be easily mistaken for not working.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sebastian Parborg self-assigned this 2019-07-24 12:08:47 +02:00

Right, this is known limitation with the zoom system. Not a bug.

Right, this is known limitation with the zoom system. Not a bug.
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
3 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#67320
No description provided.