Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Holes in intersect result #5

Closed
GoogleCodeExporter opened this issue Jul 11, 2015 · 3 comments
Closed

Holes in intersect result #5

GoogleCodeExporter opened this issue Jul 11, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

Open the attached file, there are 2 OBJ files containing triangles only.

# The model 'c.obj' was made this way.
intersect --obj a.obj A_MINUS_B b.obj > c.obj

Notice that there are holes in the resulting model, 'B' for brown.

I included c.obj in the archive also.

Original issue reported on code.google.com by ideasma...@gmail.com on 2 Jun 2009 at 3:24

Attachments:

@GoogleCodeExporter
Copy link
Author

My code indicates that c.obj consists of 22 closed surfaces. If you look at it 
in view, you'll see that all the 
faces are closed. Loading it into blender shows partial faces. Is this a bug 
with blender's triangulation code?

Running the result through my triangulator:

src/triangulate --obj c.obj > c_tri.obj

Produces a result that loads into blender without holes.



Original comment by tobias.s...@gmail.com on 2 Jun 2009 at 8:55

@GoogleCodeExporter
Copy link
Author

your right, its blenders scanfill at fault. please close this report.

Original comment by ideasma...@gmail.com on 3 Jun 2009 at 2:59

@GoogleCodeExporter
Copy link
Author

Original comment by tobias.s...@gmail.com on 3 Jun 2009 at 11:45

  • Changed state: Invalid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant