> 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/meshscatter.md). # Mesh Scatter ## Short Description Scatters objects on the components of an input mesh. ## Description The Mesh Scatter tool allows users to scatter objects across the components of an input mesh. It provides options for selecting component types and configuring the scaling and spinning of the scattered instances. ## Properties ### Base Properties * **Surface Meshes**: Meshes whose components will be used as the scatter coordinates. * **Scatter Meshes**: Meshes to scatter on the 'Surface Meshes' input. * **Component Type**: Select which component you want to scatter meshes on. * **Max Scale**: Maximum scale of every instance. * **Min Scale**: Minimum scale of every instance. * **Random Spin**: If checked, the 'Angle Spin' property is ignored, and all instances are randomly spun. * **Angle Spin**: Spins all instances towards the input angle. --- # 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/meshscatter.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.