UI: Statistics Overlay Improvements #104663
No reviewers
Julian Eisel
Pablo Vazquez
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#104663
Loading…
Reference in New Issue
No description provided.
Delete Branch "Harley/blender:ObjectStats"
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?
Miscellaneous improvements to the Statistics 3DView Overlay. Shows
internal details for selected objects while in Object Mode, including
triangles. Removes the useless "0" shown in the stats while in Sculpt
mode.
Some miscellaneous changes suggested in the following thread: https://blenderartists.org/t/the-big-blender-sculpt-mode-thread-part-2/1395490/1245
Many users said they wished they could see mesh details without having to toggle each one into Edit Mode to do so. We have this information, but just don't display it. The only related change is to only show these extra details when an object is selected. And a dissonance is removed by not showing the " 0 /" for objects in that case. Easier to explain it all with a GIF:
The other issue fixed is in Sculpt Mode, where we always currently see two "0" values:
The above is just a mistake. The first values are total verts and total faces, but gathered in a way that is specific to that mode. The second value is actually the regular vert and face totals, but they are always zero because they are not calculated in sculpt mode. Basically an improvement was added (between 2.91 and 3.0) but the old value was left in, displaying incorrectly. This patch just removes those.
d7678a6a2fto10467179f232d9de03f3tod55979839cI was a bit unsure at first because when having large numbers (6 digits or more) it could get busy, but based on community feedback it seems most prefer it this way. Stats are off by default anyway so if people have them on is because they want precise stats. If it becomes an issue we could introduce a (per editor) setting, but I don't think it'd be necessary.
@blender-bot build