API mathutils.geometry.tessellate_polygon returns bad results sometimes #68554
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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-addons#68554
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: Mint 19
Graphics card: Nvidia 860M
Blender Version
Broken: 2.80
Short description of error
API mathutils.geometry.tessellate_polygon returns bad results sometimes
Exact steps for others to reproduce the error
Open attached file, and run the script.
See on console that sometimes, tessellate returns (0, 0, 0) indices for triangles
minicube.blend
Added subscriber: @JulienDuroure
Added subscriber: @JacquesLucke
Can confirm that. Looks like it is caused by degenerate geometry. There are four faces with zero area.
Added subscriber: @dr.sybren
This is a limitation of the current implementation, and not so much a bug. I've added this limitation to the documentation to make it explicit.
Changed status from 'Confirmed' to: 'Resolved'