Zoom stops at certain level and won't go further #93273

Open
opened 2021-11-22 01:06:00 +01:00 by Michał Pęczak · 19 comments

System Information
Operating system: Windows 10
Graphics card: GeForce GTX 1070

Blender Version
Broken: 2.92, 3.0 alpha

Short description of error
In this simple model, I cannot zoom my view closer to mesh than I already did. I saved the closest achievable view position in the .blend.
I can reach further close-ups using some more advanced navigation tools, like dolly zoom, but standard zoom won't let me.
The issue is linked to this particular model - if I copy the object (there's only one in the scene) to a new model, the issue is gone.
The model was originally saved in Blender 3.0 alpha, only then in stable 2.92. Could it be the cause of this bug?

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file:
zoom issue.blend

**System Information** Operating system: Windows 10 Graphics card: GeForce GTX 1070 **Blender Version** Broken: 2.92, 3.0 alpha **Short description of error** In this simple model, I cannot zoom my view closer to mesh than I already did. I saved the closest achievable view position in the .blend. I can reach further close-ups using some more advanced navigation tools, like dolly zoom, but standard zoom won't let me. The issue is linked to this particular model - if I copy the object (there's only one in the scene) to a new model, the issue is gone. The model was originally saved in Blender 3.0 alpha, only then in stable 2.92. Could it be the cause of this bug? **Exact steps for others to reproduce the error** Based on the default startup or an attached .blend file: [zoom issue.blend](https://archive.blender.org/developer/F11839855/zoom_issue.blend)

Added subscriber: @michalpe

Added subscriber: @michalpe

#88871 was marked as duplicate of this issue

#88871 was marked as duplicate of this issue
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'
Member

I can reach further close-ups using some more advanced navigation tools, like dolly zoom, but standard zoom won't let me.

Hi, thanks for the report. I don't think this is a bug. Few workarounds are also mentioned here: https://docs.blender.org/manual/en/3.1/troubleshooting/3d_view.html#invisible-limit-zooming-in

Will close the report since this this is expected behavior.
(Feel free to reopen if I misunderstood your report)

> I can reach further close-ups using some more advanced navigation tools, like dolly zoom, but standard zoom won't let me. Hi, thanks for the report. I don't think this is a bug. Few workarounds are also mentioned here: https://docs.blender.org/manual/en/3.1/troubleshooting/3d_view.html#invisible-limit-zooming-in Will close the report since this this is expected behavior. (Feel free to reopen if I misunderstood your report)

The doc says: "Use Auto Depth and Zoom to Mouse Position."
I have these settings ON in my Preferences, but it doesn't help at all.
What happens if you use both options? Does it solve the issue for you?

Other workarounds are not enough, while I can't properly use the most important navigation tool.

I don't know how to reopen a closed task here.

The doc says: "Use Auto Depth and Zoom to Mouse Position." I have these settings ON in my Preferences, but it doesn't help at all. What happens if you use both options? Does it solve the issue for you? Other workarounds are not enough, while I can't properly use the most important navigation tool. I don't know how to reopen a closed task here.
Member

Changed status from 'Archived' to: 'Needs Triage'

Changed status from 'Archived' to: 'Needs Triage'

The mere fact that you can orbit around means the camera has not reached the defined focal point.

The mere fact that you can orbit around means the camera has not reached the defined focal point.

Added subscriber: @hadrien

Added subscriber: @hadrien

Hello,

I am not entirely sure this is indeed what's mentioned in the manual. To help clarify things, here is my experience : there is indeed a hard zoom limit in the supplied file, something I have not encountered before -but in addition to that there is also some strange interaction between zoom and dolly that I encountered when trying to work around the issue : once the zoom limit is reached (something that in my experience should happen once the camera lens reaches the point of interest, which is not the case here), we can still dolly further with shift+ctrl+mmb. However this dollying pushes the point of orbit further than we would like to (beyond the point of interest), which is expected from a dolly, from there we're again able to orbit around the point of interest if and only if we use "auto depth" (PreferencesInput.use_mouse_depth_navigate). At that point however, trying to zoom or unzoom again results in the view immediately snapping back to the hard limit. So, all in all it seemed a little fishy to me... especially given it's all happening at the centimeter scale, so not especially close to where you see numerical problems creep in.

Hello, I am not entirely sure this is indeed what's mentioned in the manual. To help clarify things, here is my experience : there is indeed a hard zoom limit in the supplied file, something I have not encountered before -but in addition to that there is also some strange interaction between zoom and dolly that I encountered when trying to work around the issue : once the zoom limit is reached (something that in my experience should happen once the camera lens reaches the point of interest, which is not the case here), we can still dolly further with shift+ctrl+mmb. However this dollying pushes the point of orbit further than we would like to (beyond the point of interest), which is expected from a dolly, from there we're again able to orbit around the point of interest if and only if we use "auto depth" (PreferencesInput.use_mouse_depth_navigate). At that point however, trying to zoom or unzoom again results in the view immediately snapping back to the hard limit. So, all in all it seemed a little fishy to me... especially given it's all happening at the centimeter scale, so not especially close to where you see numerical problems creep in.

Added subscriber: @jenkm

Added subscriber: @jenkm

Added subscriber: @iss

Added subscriber: @iss

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'

This is because maximum zoom is derived from grid spacing. I haven't found reason for that.

IMO something like this wouldn't be bad idea

diff --git a/source/blender/editors/space_view3d/view3d_utils.c b/source/blender/editors/space_view3d/view3d_utils.c
index d6a1cd930fc..2aa470f03c9 100644
--- a/source/blender/editors/space_view3d/view3d_utils.c
+++ b/source/blender/editors/space_view3d/view3d_utils.c
@@ -118,7 +118,7 @@ Camera *ED_view3d_camera_data_get(View3D *v3d, RegionView3D *rv3d)

 void ED_view3d_dist_range_get(const View3D *v3d, float r_dist_range[2])
 {
-  r_dist_range[0] = v3d->grid * 0.001f;
+  r_dist_range[0] = min_ff(v3d->grid * 0.001f, v3d->clip_start);
   r_dist_range[1] = v3d->clip_end * 10.0f;
 }
This is because maximum zoom is derived from grid spacing. I haven't found reason for that. IMO something like this wouldn't be bad idea ``` diff --git a/source/blender/editors/space_view3d/view3d_utils.c b/source/blender/editors/space_view3d/view3d_utils.c index d6a1cd930fc..2aa470f03c9 100644 --- a/source/blender/editors/space_view3d/view3d_utils.c +++ b/source/blender/editors/space_view3d/view3d_utils.c @@ -118,7 +118,7 @@ Camera *ED_view3d_camera_data_get(View3D *v3d, RegionView3D *rv3d) void ED_view3d_dist_range_get(const View3D *v3d, float r_dist_range[2]) { - r_dist_range[0] = v3d->grid * 0.001f; + r_dist_range[0] = min_ff(v3d->grid * 0.001f, v3d->clip_start); r_dist_range[1] = v3d->clip_end * 10.0f; } ```

That's true. I've set grid scale to 100 in this model. Switched back to 1 and the issue is gone.

That's true. I've set grid scale to 100 in this model. Switched back to 1 and the issue is gone.

Added subscriber: @ManuelGrad

Added subscriber: @ManuelGrad

This comment was removed by @manuelgrad1

*This comment was removed by @manuelgrad1*
Member

Added subscriber: @lionheart001

Added subscriber: @lionheart001

Hello Team,

I am hitting this again. Seems to have re-surfaced. I am running latest daily builds; 3.1.
There was a fix where we could reverse the zoom 'slow down zone' which enabled us to zoom up to parts very close without issue. But that seems gone now or not working.

Bill Ortis

Hello Team, I am hitting this again. Seems to have re-surfaced. I am running latest daily builds; 3.1. There was a fix where we could reverse the zoom 'slow down zone' which enabled us to zoom up to parts very close without issue. But that seems gone now or not working. Bill Ortis
Philipp Oeser removed the
Interest
EEVEE & Viewport
label 2023-02-09 15:13:04 +01:00
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#93273
No description provided.