Report statistics for all on-screen geometry #69887
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
13 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#69887
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?
This task proposes to ignore instancing when reporting statistics.
Currently statistics ignores instanced duplicates.
I'm not sure if this is desirable behavior, because for many use cases
the final poly-count is significant:
The down-side is that there are cases where you might not need to
be aware of the extra geometry created by instancing - for file-size,
or in cases the instances end up not being duplicated in memory.
Posting this since there is a patch to show geometry for selection
that doesn't make much sense with the current behavior - see: D5762: Show the number of verts & faces for selected objects in object mode
Added subscriber: @ideasman42
#95958 was marked as duplicate of this issue
#83812 was marked as duplicate of this issue
#71020 was marked as duplicate of this issue
In my opinion, we could show both. If we move scene stats to either:
1: The viewport
2: A 'Statistics' panel in Properties > Scene
This would give us loads more space to add way more scene info, which also doesn't have to be persistent when you don't need it.
Added subscriber: @nokipaike
it would be great if it reported the actual data + the instantiated ones, highlighting somehow that they are instantiated and not "real"
Added subscriber: @DamianWinnichenko
For the future implementation of statistics, I would suggest showing vert\poly counts in outliner.
Also, outliner might have shown a distinction between real geometry\collection and instanced one.
Added subscribers: @AlbertoVelazquez, @lichtwerk, @MarcinTwarowski
Yes, it must be by default. Few days ago I had the bad experience of don't take this in account and that my project with good polycount was out of specs only when I export the meshes...
I don't see reason to have the option to see the polycount of only not instance objects. In any case the user only will want to know the polycount of a specific object and he can see only with select that object and edit.
Added subscriber: @ckohl_art
Added subscriber: @temeddix
I also encountered a situation where many particle instances makes Blender crash while rendering. This was because I could not predict the polycount because instances were not included in the statistics. It would be nice to see statistics take instances into account.
Added subscriber: @LinoThomas
I can attest, that this feature would be greatly appreciated. I do struggle to keep an eye on poly budgets when using instanced geometry, which i heavily rely on.
Added subscriber: @kenjii
Yes, we could use that... a direct reading of the "real/total" polycount :
Added subscriber: @lictex_1
Added subscriber: @endike