bpy.context.space_data.overlay.grid_scale returns inconsistent view3D grid scale in multi-view #110845
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#110845
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
Operating system: win 10
Graphics card: RTX 3090
Blender Version
Broken: This was observed in 3.5 alpha but I don't think that is relevant
Worked: N/A
Short description of error
bpy.context.space_data.overlay.grid_scaledoes not apply to multi-view functionally, and any interaction with the 3D navigation sphere only effects the main window portion of multi-view.See attached video for a demonstration of some of the odd behavior.
See attached blend to reproduce the error.
Enter multi-grid view: ctrl+alt+q (mismatched transform grid) The main window is top right.
Click any axis sphere in any 3D view that isn't the top right quadrant, only the main window transforms.
You will also notice that the main window also inherits the grid scale of the multi-view windows.
Places to look maybe? A B
Not sure if this is by design, to me that snapping to dynamic sized grid makes more sense in XYZ quad view, and grid scale seems to behave correctly across multiple views.
3D view seems to always snap to the smallest grid that can be displayed. I'm not sure if you mean that 3D view should also snap to dynamic grid too? Note that in 3D view the farther you go, the grid become less visible, so if you were to snap to a 3d grid, shuold we snap to any "visible grid"? Or "Smallest visible unit"?
I see what you mean in terms of snapping to the dynamic grid in axis view and by extension quad view.
bpy.context.space_data.overlay.grid_scaleapplies toview3d.dollybut notview3d.view_axis, which uses dynamic grid size instead.I think The confusion stems from a visual discontinuity when using operators that transform from ortho/axis to perspective/axis view after having modified the grid scale, Where the dynamic grid continues to be displayed, but snaps to the modified grid instead.
One would expect the modified grid to be displayed, especially when navigating with "zoom to mouse position" enabled.
Iv'e attached a video demonstration of the clarified recreation steps. The blend file has overlay.grid_scale already modified.
Steps (in this order):
numpad 3 - Transforms to axis view. Modified grid replaced with dynamic grid both functionally and visually
numpad 5 - Transforms to perspective. Dynamic grid continues to be displayed but snaps to the modified grid instead
mouse ± || numpad ± - Continues to display dynamic grid, even when navigating with dolly "zoom to mouse position"
numpad 9 - Briefly displays the modified grid while transforming between +X and -X
numpad 6 - Dynamic grid replaced by modified grid visually, which lines up with the snapping, the change from axis view is subtle.
Hi, AFAICS, grid scale changes for other views as well if value is tweaked from the overlays popover.
I guess you've reported multiples issues here:
Re: snapping behavior.
@ChengduLittleA 's observation seems right to me.
To me the whole "grid subdiv" thing seems weird, since you already have adaptive subdivisions and i think this feature should be deprecated from 3d viewport, unless we have a specific option to enable an absolute grid and that way the size/subdiv adjustment can actually make sense
This maybe by design, not very sure about it. Could you open a new report for it?
@ChengduLittleA , are you able to replicate this?
@PratikPB2123 Yes that's how it works here for me.
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
Thanks again for the report. If the problem persists please open a new report with the required information.
Guess here is misunderstanding about how these features work
apologies, there was. Didn't realize this issue was still open.