> 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/fogcardtool.md). # Fog Card ## Short Description A tool for editing fog card properties in a scene. ## Description The Fog Card tool allows users to edit various properties related to fog and cloud effects. It provides controls for adjusting the appearance and behavior of clouds in a scene, including color, density, and movement. This customization enhances the visual fidelity of fog in the user's environment. ## Properties ### Base Properties * **Objects**: Objects to work on. * **Base Color Tint**: Sets the base color tint of the fog card. * **Cloud Density**: Adjusts the density of the clouds. * **Cloud Brightness**: Adjusts the brightness of the clouds. * **Cloud Contrast**: Sets the contrast of the clouds. * **Edge Fading Distance**: Controls the distance for edge fading of the fog. * **Camera Fading Distance**: Controls the camera fading distance to fog. * **Wind Speed**: Adjusts the wind speed affecting clouds. * **Wind Direction**: Sets the wind direction affecting clouds. * **Cloud Wind Tilling**: Adjusts the tiling of cloud wind patterns. --- # 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/fogcardtool.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.