> 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/toc161393790/toc161393846.md).

# Render Options

How to control surface shading and rendering percentages for members, shells, and bricks.

View > Render Options 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-5c35e01bf3148b3a213db0779569bb033c374075%2FFASTFR~1_img66.png?alt=media)

It allows you to turn on or off the shading of the surfaces of members, shells and bricks as though they were illuminated from multiple light sources. It provides a way for you to realistically visualize the image of the model. For shells, you have the option to render thickness as well as surface.

You have the option to apply different rendering percentages to different elements. Enter 100% for full rendering, 0% for no rendering, and anything in-between for partial rendering. The partial rendering (e.g. 50-80%) may be useful in identifying connectivity of elements to nodes.

{% hint style="info" %}
Note: *Rendering a model can be expensive in terms of memory and time usage by the program. You should turn off the rendering when it is not necessary.*
{% 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://enercalc.com/docs/e3d-user-manual/interface/toc175916526/toc161393790/toc161393846.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.
