> 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/sel-faq/using-the-software/general-operation/3d-renderings.md).

# 3D Renderings

How to resolve ENERCALC SEL 3D rendering issues with Aero themes and AMD processors, and how to disable renderings.

## The 3D renderings tab causes old versions of Windows to convert from the Aero theme to the classic theme. What can I do?

The Windows Aero theme is known to be incompatible with the OpenGL system used to render 3D graphics in Windows apps. So the display will revert to Windows Classic while running ENERCALC SEL, and then back to Aero when SEL is closed.

## The 3D renderings aren't visible on my computer. Why?

Check to see if the computer has an AMD processor. There is a known conflict between AMD processors and the system used to generate the 3D renderings. We continue to monitor for solutions, and will implement a change or recommendations when something becomes available.

## How can I disable the 3D renderings, and why would I want to?

There is a registry entry in Computer`\HKEY_CURRENT_USER\Software\ENERCALC\V20\Debug named DisableCoin3D. When it is set to zero`, the 3D renderings are enabled. To disable the 3D renderings, such as for diagnostic purposes, set that registry value to 1.


---

# 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/sel-faq/using-the-software/general-operation/3d-renderings.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.