> For the complete documentation index, see [llms.txt](https://docs.polygonflow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.polygonflow.io/dash-tools/quickpipe.md). # Quick Pipe ## Short Description A tool for generating customizable mesh pipes around curves. ## Description Quick Pipe is a tool designed to create mesh pipes along specified input curves. It allows for customization of pipe properties such as radius, profile shape, and UV mapping to enhance the 3D modeling experience. ## Properties ### Base Properties * **Curves**: Curves to create a pipe around. * **Radius**: Controls the radius of the pipe. ### Pipe Settings * **Sides**: Controls the side divisions of the profile. * **Custom Profile**: You can pass another curve to use as your pipe's profile. * **Custom Profile Scale**: When a custom profile is provided, this value controls its size. * **Open Profile**: If checked, the profile's sides will be opened. * **Close Caps**: If checked, the pipes will be closed with a cap. * **Normalized UVs**: When turned off, the UVs will be tiled depending on the mesh length in the scene. * **Normals Angle**: Normals angle of the generated pipe mesh. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.polygonflow.io/dash-tools/quickpipe.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.