Parks wants procedural softscape edges driven by per-vertex width on a path mesh. What should authors add?
Select an answer to reveal the explanation.
Short Explanation
Softscape edge widths are geometry data—add a vertex width primvar on the path mesh. Relationships to empty overs and visibility toggles do not feed procedural widths. Put the numbers where the points live.
Full Explanation
Parks procedural softscape that follows path edges needs geometric width data on the path mesh itself. Authors should add a vertex-interpolated width primvar on that mesh so the procedural edge system can sample per-vertex widths along the path. Primvars are the OpenUSD mechanism for binding varying geometric parameters to topology; vertex interpolation matches smoothly changing softscape borders without inventing a parallel non-USD channel.
Adding only a relationship to an empty over prim creates a pointer with no width payload and does not feed procedural generators. A boolean visibility opinion on the root layer can hide content but cannot encode continuous edge widths. Setting metersPerUnit to the path length in feet abuses stage unit metadata—metersPerUnit defines the stage’s linear unit, not a per-path softscape parameter—and using feet in a meters field invites scale bugs across the twin.
Exam caveat: if the procedural tool expects a specific primvar name or type (float vs float[]), match the pipeline schema; the conceptual answer remains a vertex width primvar on the mesh, not stage metadata or visibility hacks.
Operational check: author the width primvar with vertex interpolation on a sample path, run the softscape generator, verify edge widths track the authored values at several vertices, and confirm the primvar survives composition when the path is referenced into a parks master layer.