> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/e3d-user-manual/interface/toc175916526/toc442029162/toc161393989.md).

# Colors

How to set the display colors of graphical model entities and image-capture backgrounds in ENERCALC 3D.

Settings & Tools > Colors prompts you with the following dialog.

![](https://560001759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWNe8U6EBBBdUJHdb2X9G%2Fuploads%2Fgit-blob-52a3a429e5799ee621eae4e4cc93cdfec0c91c0c%2FFASTFR~1_img218.png?alt=media)

It allows you to set colors of different graphical entities in the model. You may modify the color(s) of one or more items at a time. By checking “Use color cues for different materials”, concrete, steel and wood materials will show different colors in rendering mode.

By checking “Use white background for image captures”, a white background will be used for the captured image even if a different background color is used in the model views. This option will reduce the amount of ink required to print the images. Color settings can be optionally saved for future use.


---

# 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://enercalc.com/docs/e3d-user-manual/interface/toc175916526/toc442029162/toc161393989.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.
