Hi, Me and @DavidMans are trying to make sense of the false output we get from the Mesh point inclusion component in the example illustrated below. Welding the mesh doesn’t seem to improve the result, but moving the point asymmetrically either along the X or Y direction seems to resolve it. Any ide…

Hi @emilpoulsen , We should have a fix in this week’s WIP release candidate. https://mcneel.myjetbrains.com/youtrack/issue/RH-57774 – Dale

Hi @emilpoulsen , @dave_m , I’m looking at this. – Dale

Excellent, thanks @dale . Let us know if we can help.

It’s not limited to your point, I guess it’s a known bug explained here: [image] C# Point in Closed Mesh, Mesh Inclusion Predicament: Attempting to cull specific 3d grid cells based on point inclusion from cellular automata. Problem: The normal Mesh Inclusion does not test all po… …

BTW: Also in R5 the Mesh.IsPointInside(…) Method yields occasionally incorrect results most notably if Mesh.IsClosed returns true AND Mesh.SolidOrientation() returns 0 (meaning propably inward/outward facing normals). If you are familiar with C# I could provide some temporary sort of solution.

Thanks, @PeterFotiadis - a C# workaround would be fantastic for the time being.

OK, I’ll prepare a simple case with 3 test options (IsPointInside and other 2) as used in some C# that attempts to “heal/fill” Concave Mesh faces on a per topology edge Face adjacency basis. Thus you can use portions of the code for your purposes.

Thanks @Mahdiyar - I didn’t know this issue had a history! Rotating the input mesh isn’t ideal, but definitely a good candidate for a temporary workaround. Many thanks for sharing your definition.

[image] emilpoulsen: Rotating the input mesh isn’t ideal Just to clarify, you only need to use the rotated mesh and points as inputs for MeshInclusion component. and obviously, elsewhere, you can use the original mesh and points.

[image] emilpoulsen: C# workaround Here’s the thing: As I said the scope of this is to locate edges that yield convex/concave dihedrals (in order to “relax” similar Meshes used for freaky MERO trusses, blah, blah). In order to find the edges 3 options are provited: 2 of them require answeri…

Thanks @Mahdiyar . For context, the inclusion logic will go straight into a rhinocommon based backend system where the check performed on a modified mesh might cause other issues downstream. The GH definition attached was just to demonstrate the issue. Thanks again!

Mesh point inclusion test reports unexpected result

Grasshopper

brian (Brian Gillespie) April 28, 2020, 10:46pm 15

RH-57774 is fixed in the latest Service Release Candidate

Topic		Replies	Views
Mesh Inclusion Error Grasshopper Developer	23	4269	December 17, 2024
Is Point In Mesh? Grasshopper rhinocommon	0	378	July 19, 2018
Bug: GH MeshInclusion (Minc) Grasshopper rhino5	0	606	June 18, 2017
IsPointInside - bug Rhino Developer	11	1501	August 16, 2022
Mesh.IsPointInside() persistent bug Rhino Developer	8	1426	March 24, 2026

Mesh point inclusion test reports unexpected result

Related topics