Incremental snapping is constant (not adapting to orthographic viewport scale) #56499
Labels
No Label
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Content
Type
Design
Type
Report
Type
To Do
Type
Web Development
No Milestone
No project
No Assignees
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: studio/blender-studio#56499
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Xbuntu / AMD
Blender Version
21f0906
Short description of error
When using incremental snapping in the viewport, it's always set to 1 meter regardless of whether you're zoomed into the viewport and 1 meter is far greater than your view. Basically it should adapt to the viewport like it used to do in 2.79.
Exact steps for others to reproduce the error
New file
go to orthographic side view
select the cube and zoom into it
move it in x-axis while holding down Ctrl
...it jumps between 0 and 1 even though your view might only be looking at something closer to 0.01 in size...
Added subscriber: @Hjalti
Added subscriber: @Martantoine
This bug is also on windows 10 x64
Incremental snapping is constant (not adapting to viewport)to Incremental snapping is constant (not adapting to orthographic viewport scale)Added subscriber: @mano-wii
Analyzing the code, it seens that this pre2.80 behavior came by accident.
The distance between the snap points is calculated by
rv3d->gridview
which is apparently a member created to draw the grid in blender 2.79.On 2.80 the grid drawing was completely rewritten, and the
gridview
member became deprecated.We can simulate the same behavior seen in 2.79 with this:
P771: Fix #56499
Or we can change the default behavior to just consider the
grid_scale
.Added subscriber: @brecht
I don't think the behavior was by accident, snapping to the visible grid resolution is by design. But it wasn't obvious at all that this variable is used for snapping.
The
rv3d->gridview
variable can be removed, and instead there can be a 3D view utility function that computes it. Then it can also be used by the snap to grid operators, since those have the same problem as the transform operator.If that is the case, the grid drawing has also changed, so in the orthographic views when RV3D_VIEW_IS_AXIS the number of subdivisions in blender2.80 is less than in previous versions.
Not to mention that now in blender2.80, in any position, the grid adapts the drawing of subvisions.
I think a new behavior still needs to be discussed.
In my opinion a middle ground would always be to adapt the distance between the grid snap points (not just if RV3D_VIEW_IS_AXIS) and change the default
grid_scale
from 1.0 to 0.01.Added subscriber: @cunabula
This was something I posted about in Right Click Select:
https://blender.community/c/rightclickselect/HQbbbc/
Copy/pasted here:
Added subscriber: @zeauro
Absence of subdivisions is a problem.
A user losts a useful info about proportions. This is my unit. And this is one half, one third or one tenth of my unit.
I want my object 3 units large. So, that detail of this object should be large of 2 tenth of unit.
It is how user is thinking during the modeling process.
It helps a lot to make a decision to see subdivisions of grid.
Currently, with default grid scale at 1, subdivisions are invisible.
With grid scale at 0.1, they become visible. But now, it means that grid increment is set to 0.1 unit.
At grid scale at 1, if I set amount of subdivisions to 3 to see thirds of my unit, I obtain a grid with thicker lines every 3 units and subdivision lines corresponding to 1 unit.
A default for grid scale to 0.01, does not make sense. User wants grid units corresponding to its unit system, not to a portion of it.
Subdivisions should behave as subdivisions, not as a way to specify these first units have thiner lines.
Basically user wants to be able to switch between a grid increment relative to thick lines and a grid increment relative to thiner lines.
It could be an option for grid increment snapping. There is no need to mess up grid display for that.
A problem about grid increment snapping is a snapping problem. Solution should modify snapping.
A problem about grid display, is a display problem. Solution should modify display.
But please, don't try to solve a problem with an inappropriate solution.
This issue was referenced by blender/blender@c8e6134386
Changed status from 'Open' to: 'Resolved'