> 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-release-notes/version-4.1.2.md).

# Version 4.1.2

#### Visualization

🪲 Fixed material UV rotation not being saved correctly

🪲 Fixed issues with some LED fixtures in Simple Modes.

🪲 Improved water surface reflections.

🪲 Fixed Viz-Key input channel offset in Logic and DMX View.

🪲 Fixed Atmosphere Moon Type setting not being saved.

🪲 Fixed missing Martin P3 output when RGB channels are set to zero.

#### Control

🪲 Fixed an issue with releasing selected channels in the Programmer.

🪲 Fixed V:Server firmware updates through Depence.

🪲 Fixed issues with Video Track fades.

#### General

🪲 Fixed missing MCP Server dependencies.


---

# 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-release-notes/version-4.1.2.md?ask=<question>&goal=<user_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.
