"bmesh.geometry.intersect_face_point" does not always return the correct information #43739

New Issue

Germano Cavalcante · 2015-02-19T22:30:22+01:00

2015-02-19 22:30:22 +01:00

System Information
Windows 64 bits

Blender Version
Broken: version 2.73 (sub 7), hash b'4ae6d58'

Short description of error
Test one point in different faces. Some face will return the value True despite the point not being in the face.

Exact steps for others to reproduce the error

Open the attached .blend
Copy and Paste this code (below) in Blender:
See if indeed the "True" statement is really true.

    import bpy, bmesh

    obj = bpy.context.active_object
    bm = bmesh.from_edit_mesh(obj.data)

    face = bm.faces[2] #The face more to the X
    point = bm.verts[21].co #The point highlighted in red

    print(bm.faces[2])
    print(bm.verts[21])
    """..."""
    print(bmesh.geometry.intersect_face_point(face, point))

To simplify the display of indices, in the attached .blend has the script: "view3d_idx_view.py" developed by Bartius Crouch, CoDEmanX and zeffii.
bug_bmesh.blend

**System Information** Windows 64 bits **Blender Version** Broken: version 2.73 (sub 7), hash b'4ae6d58' **Short description of error** Test one point in different faces. Some face will return the value True despite the point not being in the face. **Exact steps for others to reproduce the error** 1. Open the attached .blend 2. Copy and Paste this code (below) in Blender: 3. See if indeed the "True" statement is really true. ``` import bpy, bmesh obj = bpy.context.active_object bm = bmesh.from_edit_mesh(obj.data) face = bm.faces[2] #The face more to the X point = bm.verts[21].co #The point highlighted in red print(bm.faces[2]) print(bm.verts[21]) """...""" print(bmesh.geometry.intersect_face_point(face, point)) ``` To simplify the display of indices, in the attached .blend has the script: "view3d_idx_view.py" developed by Bartius Crouch, CoDEmanX and zeffii. [bug_bmesh.blend](https://archive.blender.org/developer/F144884/bug_bmesh.blend)

Germano Cavalcante commented

2015-02-19 22:30:22 +01:00

Changed status to: 'Open'

Campbell Barton was assigned by Germano Cavalcante

2015-02-19 22:30:22 +01:00

Germano Cavalcante commented

2015-02-19 22:30:22 +01:00

Added subscriber: @mano-wii

Campbell Barton was unassigned by Bastien Montagne

2015-02-20 10:53:31 +01:00

Bastien Montagne self-assigned this 2015-02-20 10:53:31 +01:00

Bastien Montagne commented

2015-02-20 10:53:31 +01:00

Added subscriber: @ideasman42

Bastien Montagne commented

2015-02-20 10:53:31 +01:00

Not a bug actually, this tests the projection of the point onto the face (using face's normal)… Py doc is ambiguous here at least, though, will fix that.

Not a bug actually, this tests the **projection** of the point onto the face (using face's normal)… Py doc is ambiguous here at least, though, will fix that.

blender-admin commented

2015-02-20 10:54:26 +01:00

This issue was referenced by 51b0ae8a85

This issue was referenced by 51b0ae8a85dbb47963f24fe3d79de878092cc6cc

Bastien Montagne commented

2015-02-20 10:56:26 +01:00

Changed status from 'Open' to: 'Resolved'

Bastien Montagne closed this issue

2015-02-20 10:56:26 +01:00

Bastien Montagne commented

2015-02-20 10:56:26 +01:00

Closed by commit 51b0ae8a85.

Closed by commit 51b0ae8a85.

Germano Cavalcante commented

2015-02-20 13:15:37 +01:00

Added subscriber: @mont29

Germano Cavalcante commented

2015-02-20 13:15:37 +01:00

Okay. Thanks for the clarification @mont29. But confirms if I really understood. What is happening is what is represented in this image?:

Okay. Thanks for the clarification @mont29. But confirms if I really understood. What is happening is what is represented in this image?: ![Do_be_that_way.png](https://archive.blender.org/developer/F144964/Do_be_that_way.png)

Bastien Montagne commented

2015-02-20 14:11:00 +01:00

Yes, that’s expected behavior (potential float precision issues taken into account, so in limit cases you may have 'surprises').

Germano Cavalcante commented

2015-02-20 15:02:28 +01:00

I Got. If the accretion option "projection distance" not much increase the calculation memory. I think it would be a good consideration.
Ex: bmesh.geometry.intersect_face_point (face, point, projection_distance).
Just a idea.

I Got. If the accretion option "projection distance" not much increase the calculation memory. I think it would be a good consideration. Ex: bmesh.geometry.intersect_face_point (face, point, projection_distance). Just a idea.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

"bmesh.geometry.intersect_face_point" does not always return the correct information #43739