Comentario
08-22-2017
05:05 PM
08-22-2017
05:05 PM
Allowing 3-dimensional Gridlines would be very powerful. Seems like inclusion of REFERENCE LINES at the Project Level would be a start. After that, allowing Reference Lines to be NAMED would be even better (as well as allowing access to a reference line's workplanes, both along its length and perpendicular planes at its ends, by Name). Then, add the rest of grid functionality (category assignment, grid bubble tagging options, breaks in grid per view, as well as structural member association).
In addition, after POLYLINES have been implemented in Revit, Multi-segmented grids could be made on the fly by joining grid segments-- this could work for 2D AND 3D grids. I know what you're thinking: how can we implement Reference Lines or 3D grids, which would likely be driven by end points that are sometimes shared among separate lines/grids and would want to be controlled by a shared POINT, if Reference POINTS aren't accessible at the Project Level? Answer: Reference POINTS should be accessible at Project Level, be namable, and be autonomous to move independent of Reference Planes. (This functionality is already somewhat possible using Adaptive point families).
Given the increase in parametric processes and structural integration, and that these workflows rely heavily on points, lines/arcs/curves, polylines/polycurves, and Nurbs curves, Revit should make a real and strategic effort to maintain and Improve these functionalities on its end, even if only to talk better with Dynamo, and hopefully in a way that is also useful without it.
In addition, after POLYLINES have been implemented in Revit, Multi-segmented grids could be made on the fly by joining grid segments-- this could work for 2D AND 3D grids. I know what you're thinking: how can we implement Reference Lines or 3D grids, which would likely be driven by end points that are sometimes shared among separate lines/grids and would want to be controlled by a shared POINT, if Reference POINTS aren't accessible at the Project Level? Answer: Reference POINTS should be accessible at Project Level, be namable, and be autonomous to move independent of Reference Planes. (This functionality is already somewhat possible using Adaptive point families).
Given the increase in parametric processes and structural integration, and that these workflows rely heavily on points, lines/arcs/curves, polylines/polycurves, and Nurbs curves, Revit should make a real and strategic effort to maintain and Improve these functionalities on its end, even if only to talk better with Dynamo, and hopefully in a way that is also useful without it.