Python data do not accord with the value that show_extra_face_area displays. #44316

Closed
opened 2015-04-09 01:48:20 +02:00 by perfection cat · 7 comments

System Information
Windows XP/SP3 32bits

Blender Version
Broken: version 2.74 (sub 4), branch b'master', commit date b'2015-04-08' b'00:38', hash b'8c539b0', b'Release'
Worked: unknown

Short description of error
Python data do not accord with the value that show_extra_face_area displays.
Exact steps for others to reproduce the error
The value of the area that I can access in Python does not agree with the value of an area displayed by 3DView.
face_area.png
face_area.blend

**System Information** Windows XP/SP3 32bits **Blender Version** Broken: version 2.74 (sub 4), branch b'master', commit date b'2015-04-08' b'00:38', hash b'8c539b0', b'Release' Worked: unknown **Short description of error** Python data do not accord with the value that show_extra_face_area displays. **Exact steps for others to reproduce the error** The value of the area that I can access in Python does not agree with the value of an area displayed by 3DView. ![face_area.png](https://archive.blender.org/developer/F159985/face_area.png) [face_area.blend](https://archive.blender.org/developer/F159987/face_area.blend)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @sindra1961

Added subscriber: @sindra1961

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Campbell Barton self-assigned this 2015-04-09 02:20:57 +02:00

This isnt really a bug.

Whats happening is there are 2 different methods used to calculate area:

  • View-port drawing accumulates tessellated triangle areas.
  • The Python API uses the cross product of a polygon divided by its length.

We could use the same method for both but the first method is faster, so its used for drawing.

In you example the faces are non-planar, (not flat) so the answers are slightly different.

closing.

This isnt really a bug. Whats happening is there are 2 different methods used to calculate area: - View-port drawing accumulates tessellated triangle areas. - The Python API uses the cross product of a polygon divided by its length. We could use the same method for both but the first method is faster, so its used for drawing. In you example the faces are non-planar, (not flat) so the answers are slightly different. closing.
Author

I understood what you meant.
But is there predominantly more object which is not flat?
Then may I recognize that python data shows the accurate area of the shape?

I understood what you meant. But is there predominantly more object which is not flat? Then may I recognize that python data shows the accurate area of the shape?

@sindra1961, for non flat faces - the area is undefined. (you get different answers depending on how you calculate it.)

In this case though, I think Python's result is more accurate, since its always the same - independent of triangle tessellation.

@sindra1961, for non flat faces - the area is undefined. *(you get different answers depending on how you calculate it.)* In this case though, I think Python's result is more accurate, since its always the same - independent of triangle tessellation.
Author

I thank for what you replied.
I think that nobody is at a loss if python API document has the explanatory note about it.
Finally I thank for your correspondence once again.

I thank for what you replied. I think that nobody is at a loss if python API document has the explanatory note about it. Finally I thank for your correspondence once again.
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
2 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#44316
No description provided.