Below is an example of a divided poygonal flat surface. The vertical grid is based on fixed distance u-grid, the horizontal on intersect list. Most nodes at the surface boundary are not constructed.
1. The exception (circled in red) is where the adjoining grid segment lengths exceed 5000 mm and the opposing panel edge is based on an intersect.
2. The rectangular pattern looks correct, save for pentagonal surface segment where a boundary node is involved.
3. Pattern-based panel: panels are simply trimmed at the surface boundaries, except where boundary nodes exist. Here the panels are constructed completely (as desired).
4. Repeat adaptive panel: panel is only repeated at boundaries where nodes exist. It is also not possibly to place boundary panels manually, as the nodes are missing.
Note only u/v-grids are used, boundary nodes are missing completely.
You can probably get the best results by starting with patterning (as opposed to repeat)
For cut off, 4 point conditions using patterning, try selecting individual components and setting the "component extents" property to "fit to tile". They should snap into position
For 3 and 5 point conditions, you will need to make 3 and 5 point adaptive components to manually sew into place.
If you change the divided surface representation from Surface, to Pattern, you will be able to snap the manual placement of Adaptive Components to the endpoints of the pattern lines, even though there are no nodes. This has some drawbacks, as the orientation of the individual points of the AC will be relative to the lines, whereas the ones that rely on “nodes” derive their orientation from the surface normal. This may or may not be a concern for your particular panels.
Thanks for those very helpful hints.
I still have some issues because my panel has a special mullion at the top (highlighted in red).
I still think it would make more sense if the pattern boundary intersections automatically generated pattern points (as already happens in some rare cases), so I will submit an enhancement request.
Hi there,
I stumbled across this old post having the same problem. I was wondering if you guys have any new information on this issue?
Just like @Anonymous said, I´d like to avoid manual placement, since it is quite nasty aswell...
Thanks in advance!
@Anonymous wrote:
I still think it would make more sense if the pattern boundary intersections automatically generated pattern points (as already happens in some rare cases), so I will submit an enhancement request.
Did you submit this as an idea?
If so, I´d like to go vote for it!