Convert mesh from text should return a clean mesh not having double vertices #40021

Closed
opened 2014-05-04 16:38:40 +02:00 by Oliver Bo · 15 comments

System Information
Operating system and graphics card

Blender Version
Broken: 2.70a and current dev version 2a3cdea

Short description of error
Converting a text to a mesh was not usable for boolean operations and likely other functions.
According to Thread
they found a solution that worked for me: remove double vertices

Exact steps for others to reproduce the error
Open attached blend file
Error:
Open the cubes modifier and select the convert object

  • Boolean operation didn't work

Good:
Select the removed doubles object in the cubes boolean operator

  • Works as expected

convertmeshbug.blend

**System Information** Operating system and graphics card **Blender Version** Broken: 2.70a and current dev version 2a3cdea **Short description of error** Converting a text to a mesh was not usable for boolean operations and likely other functions. According to [Thread ](http://www.blenderartist.org/forum/showthread.php?284855-Text-And-Boolean-Problems) they found a solution that worked for me: remove double vertices **Exact steps for others to reproduce the error** Open attached blend file Error: Open the cubes modifier and select the convert object - > Boolean operation didn't work Good: Select the removed doubles object in the cubes boolean operator - > Works as expected [convertmeshbug.blend](https://archive.blender.org/developer/F86905/convertmeshbug.blend)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @oliverbojahr

Added subscriber: @oliverbojahr

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2014-05-04 17:33:00 +02:00

This is producing such meshes by design, you can easily run a removedouble tool after conversion if needed… Not a bug, thanks for the report anyway.

This is producing such meshes by design, you can easily run a removedouble tool after conversion if needed… Not a bug, thanks for the report anyway.
Author

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'
Author

Hmm disagree somehow.

Why is there the need to Google, skip to several results.
If it's by design, do you see any other chance in giving the user a hint.

So, I did some more investigations, that puzzles me:
In Blender default font, a capital T is composed out of straight lines. (Handles scaled to 0)

Scenarios:

  1. Letter T -> Convert to Mesh -> "fine" it creates a triangulation
  2. Letter T -> Convert to Curve - Convert to Mesh -> like above (likely the algorithm/or Text is just a bunch of curves)
  3. Letter T slightly extruded -> Convert to Mesh -> Results into 16 duplicate vertices
  4. Curve/Circle slightly extruded -> Convert to Mesh -> fine it creates quads and no double vertices. But not filled
  5. Curve/Circle scaled all handles to 0 (Sqaure) slightly extruded -> like above
    4b, 5b) Filling the top and button does not introduce double vertices
  6. Drawing a T and extruded slightly -> Convert to Mesh -> Fine -> Fill top and bottom -> Triangulate -> Fine

I don't know the algorithm, but above examples might indicate, that there are other options than currently chosen.

Hmm disagree somehow. Why is there the need to Google, skip to several results. If it's by design, do you see any other chance in giving the user a hint. So, I did some more investigations, that puzzles me: In Blender default font, a capital T is composed out of straight lines. (Handles scaled to 0) Scenarios: 1) Letter T -> Convert to Mesh -> "fine" it creates a triangulation 2) Letter T -> Convert to Curve - Convert to Mesh -> like above (likely the algorithm/or Text is just a bunch of curves) 3) Letter T slightly extruded -> Convert to Mesh -> Results into 16 duplicate vertices 4) Curve/Circle slightly extruded -> Convert to Mesh -> fine it creates quads and no double vertices. But not filled 5) Curve/Circle scaled all handles to 0 (Sqaure) slightly extruded -> like above 4b, 5b) Filling the top and button does not introduce double vertices 6) Drawing a T and extruded slightly -> Convert to Mesh -> Fine -> Fill top and bottom -> Triangulate -> Fine I don't know the algorithm, but above examples might indicate, that there are other options than currently chosen.
Author

Additional comments:

Again the letter T extruded a bit and converted to a mesh, produces the following:

  1. The contour is connected and filled with quads and all vertices are connected and share the contour faces (like seen with curve extrusions)
  2. The filling appears to be incorrect
    2.1) The top and bottom faces do not share the vertices with the contour
    2.2) The filled faces of the upper rectangle of the T contain a zero face

For the case of the T the following manual steps worked great:

  1. Deleted the top and bottom fill faces
  2. Select each contour and fill face using 'F' command
  3. Triangulate faces command
  • Contour is connected with fill faces, no double vertices, and no zero face

I think you should somehow accept the reopen, especially in respect to the bug summary.

Additional comments: Again the letter T extruded a bit and converted to a mesh, produces the following: 1) The contour is connected and filled with quads and all vertices are connected and share the contour faces (like seen with curve extrusions) 2) The filling appears to be incorrect 2.1) The top and bottom faces do not share the vertices with the contour 2.2) The filled faces of the upper rectangle of the T contain a zero face For the case of the T the following manual steps worked great: 1) Deleted the top and bottom fill faces 2) Select each contour and fill face using 'F' command 3) Triangulate faces command - > Contour is connected with fill faces, no double vertices, and no zero face I think you should somehow accept the reopen, especially in respect to the bug summary.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Would have to ask Sergey the exact reason, but remember we closed other reports like this int the past… Again, a bug is something that does not work as intended, this works as intended!

Would have to ask Sergey the exact reason, but remember we closed other reports like this int the past… Again, a bug is something that does not work as intended, this works as intended!
Author

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'
Author

Bastien, could we ask for a second opinion.

The reason is, that it does not work as I intended and certainly needs an improvement. I cannot judge about priorities, schedule or complexity.
I'd expect a filled and good designed letter as the T is to create a manifold, non zero face, non duplicate and non intersecting mesh.
That's what I expect from a function called: "Mesh from text with fill set to true"

Hence: To me the text fill option does not do a good job in the case of the letter T and possible others.

If I follow your arguments, that it was intended to create meshes of bad quality by intention, I'd expect to read this in the documentation and expect there are good reasons for it.

From manual:
Fill
The fill options control how the text curves are filled in when text is Extruded or Beveled in the Geometry Panel.

Front
Fills in the front side of the surface.
Back
Fills in the back side of the surface.
Fill Deformed
Fills the curves after applying shape keys and modifiers.

- Might appended with (not meant offending, really)

Creation of filled text is a complicated task. Fiilled text does create non manifold, unconnected and zero faces. Filled faces are not connected to the contour. So it is not recommended to use this function for 3D print, sculpting and boolean operations without cleaning up. In these cases we recommend to use the function remove duplicate vertices, which might solve some problems. You might also consider the remesh modifier or better filling faces manually.

Bastien, could we ask for a second opinion. The reason is, that it does not work as I intended and certainly needs an improvement. I cannot judge about priorities, schedule or complexity. I'd expect a filled and good designed letter as the T is to create a manifold, non zero face, non duplicate and non intersecting mesh. That's what I expect from a function called: "Mesh from text with fill set to true" Hence: To me the text fill option does not do a good job in the case of the letter T and possible others. If I follow your arguments, that it was intended to create meshes of bad quality by intention, I'd expect to read this in the documentation and expect there are good reasons for it. From manual: **Fill** The fill options control how the text curves are filled in when text is Extruded or Beveled in the Geometry Panel. **Front** Fills in the front side of the surface. **Back** Fills in the back side of the surface. **Fill Deformed** Fills the curves after applying shape keys and modifiers. - Might appended with (not meant offending, really) Creation of filled text is a complicated task. Fiilled text does create non manifold, unconnected and zero faces. Filled faces are not connected to the contour. So it is not recommended to use this function for 3D print, sculpting and boolean operations without cleaning up. In these cases we recommend to use the function remove duplicate vertices, which might solve some problems. You might also consider the remesh modifier or better filling faces manually.
Bastien Montagne removed their assignment 2014-05-04 21:19:13 +02:00
Sergey Sharybin was assigned by Bastien Montagne 2014-05-04 21:19:13 +02:00

Added subscriber: @mont29

Added subscriber: @mont29

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

This is a known behavior of current text tessellator which produces open manifold. I'm not sure why you mention that likely other functions would have issues boolean is really a special case which expects closed manifolds. And even if the text case is supported, it's still possible to confuse boolean modifier with other meshes.

It's always possible to improve the things, but such things are out of the bug tracker.

Thanks for the report, but it is a TODO which is already listed there http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Text_Editing_.283D.29

This is a known behavior of current text tessellator which produces open manifold. I'm not sure why you mention that likely other functions would have issues boolean is really a special case which expects closed manifolds. And even if the text case is supported, it's still possible to confuse boolean modifier with other meshes. It's always possible to improve the things, but such things are out of the bug tracker. Thanks for the report, but it is a TODO which is already listed there http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Text_Editing_.283D.29
Author

The fill algorithm creates non manifold and zero faces and do prevent functions like 3d printing, boolean operations and Sculpting (likely more).

I understand it's a known limitation. I'd rather make a note in the manual and would also adopt the text in the todo list

Text Editing (3D)
When converting filled/beveled text into a mesh - there are many doubles and zero faces.

The fill algorithm creates non manifold and zero faces and do prevent functions like 3d printing, boolean operations and Sculpting (likely more). I understand it's a known limitation. I'd rather make a note in the manual and would also adopt the text in the todo list **Text Editing (3D)** When converting filled/beveled text into a mesh - there are many doubles and zero faces.
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
3 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#40021
No description provided.