Array Along Path vid

Another great vid from JPW's Wayne Dickerson !

1. It would be great to be able to reference geometry from Ref attachments using something other than the Range Box. Item Type properties, maybe? This would provide a more robust link as the reference geometry would inevitably move about.

2. Start point: I think that a more common way to define this would be to use an intersection point defined by a line perpendicular to / crossing the path Curve, which the user would use Mstn tools to manipulate. Again, this would normally be in the Ref attachment and it would be good to link directly to the GC script without having to define Range Boxes. There will be a lot of this kind of input geometry... some of which may be nested in Cells.

3. OpenBuildings Grid Node - it would be good to be able to extract intersections, grid names etc. Possible already in U6?

4. Exceptions: is it possible to index one of the arrayed Cells and add something that is specific to that Cell? Eg Translation: this would save the user having to redo his array if there is a localised clash  or offset requirement. Delete / Suppress is another one that would be really useful. It would be great if the index would be displayed or extracted using a tool or simply by hovering over the Cell.

5. Performance: it would be good to understand how -if possible- the script can be speeded up. I understand that GNTs do not speed up processing. Not sure what a C++ coder would do if he was given a GC script file and asked to port it. Easy? This would mean that no further changes to the script would be possible, but it would be worth the speed up in the later design phases when things are more settled anyway.

6. Packaging: this kind of array tool could be packaged up a Cell and inserted into a model. It would be great to be able to provide a control panel that would be specific to the Cell.

7. ??

Parents Reply Children
No Data