> For the complete documentation index, see [llms.txt](https://help.depence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.depence.com/depence-construction/depence-atmosphere.md).
# Atmosphere
The Atmosphere object will automatically be added to your scene along with the terrain object after clicking on **Objects** > **"Create Environment"**. The atmosphere simulates the sunlight & shadows along with atmospheric scattering depending on the sun's position.
To adjust the sun's position click on the Lighting Icon on the left side of the viewport.
The first control element changes the direction while the second defines the height of the sun.
{% hint style="success" %}
To get fine sun height control, move your mouse far away after clicking and holding the mouse button on the sun.
The farthest is your cursor, the finest is the control.
{% endhint %}
The preset buttons on the right can be used to store a specific position. To store a position on a **preset button** hold your **CTRL-Key** while clicking on a button.
## Custom Map
HDR custom map applied to change the atmosphere background
From the **Atmosphere Settings** > **Custom Map**, you can import your own map:
{% hint style="success" %}
Light settings may be tuned to match your custom map
{% endhint %}
---
# 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://help.depence.com/depence-construction/depence-atmosphere.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.
