> 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-materials.md). # Materials Depence is based on a PBR *(Physical Based Rendering)* Material concept. Instead of traditional rendering approaches, where artistic values and colors were taken to design a 3D scene, a PBR approach takes more physically correct parameters into account. Especially when it comes to lighting computation, several natural scientific mathematics and rules are used to simulate lighting and materials as realistically as possible. One important aspect of a PBR pipeline is the definition of materials, which is now not only a color or texture, it is more a physical representation of a surface usually called "PBR Material" or "Substance". ![](https://content.gitbook.com/content/SJPsyh5CBOise9BtVNGO/blobs/wd0LcDEAZ4mfVAwFgijW/41254928.png) ![](https://content.gitbook.com/content/SJPsyh5CBOise9BtVNGO/blobs/dvaY9XXvalnkXUbtm4rD/40894503.png) For detailed information about PBR Rendering see:\ \ Create your own PBR Materials:\ Source for ready-to-use high-quality PBR Materials:\ [https://gametextures.com/](https://beta.gametextures.com/) ## Change a Material Type Once an 3D Model is selected, go to the Material Tab in the Settings window, click on Material button. --- # 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-materials.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.