Surface.PointAtParameter

[vykrum]

Dynamo version

1.0.1.1250

Operating system

Windows 10

What did you do?

Surface.PointAtParameter

What did you expect to see?

Points confined to within the surface like on this other lofted surface..

What did you see instead?

[andydandy74]

Sometimes this is actually useful. But there should be an easy way of eliminating points that are not loacted within a trimmed surface, perhaps a boolean toogle in the Surface.PointAtParameter node.

[vykrum]

@andydandy74 Agree it could be useful in some cases as a sort of bounding grid
But in this case, the points beyond the surface are placed at elevations corresponding to part of some geometry that has been split and removed. Not sure if such phantom points that retain memory of discarded geometry are desirable.
In any case, the behavior of the node needs to be consistent, considering both the images attached above were generated from the same version.

[mccrone]

@vykrum if you want to discard the points that are past the surface, use the test: Geometry.DoesIntersect with the surface, then discard the points that return a false result with FilterByBoolMask.

[vykrum]

@mccrone Earlier, had to use Point.Project in a similar way as a work around while using Surface.PointAtParameter. As of mid last month thought that wouldn't be necessary anymore. But seems like in some cases might still need to resort to that approach while in some other cases it won't be necessary as it works well.

[kronz]

@aparajit-pratap

[riteshchandawar]

Here is the issue for internal tracking. http://adsk-oss.myjetbrains.com/youtrack/issue/MAGN-9320
Although the issue not similar to the above but while fixing that issue we can to consider this scenario as well.

Thanks,
Ritesh

[aparajit-pratap]

@riteshchandawar 9320 is an unrelated issue. That is related to the ASM scaling issue. Marking this as an improvement.