> For the complete documentation index, see [llms.txt](https://docs.archisketch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archisketch.com/guide/enterprise-en/manage-furniture/modify-furniture-finishing/effector.md).

# Effector

## What is Effector?

**Effector**is a feature provided by Archisketch **furniture material editing feature**a tool that lets you adjust various properties (roughness, metalness, opacity, etc.) so you can express furniture surface materials in a way similar to reality.

### How to Access Effector

Effector can be used through the following two paths.

1. **Editor** → **Edit Material**
2. **Dashboard** → **Check 3D Modeling**

{% hint style="info" %}
Both paths provide the same Effector functionality, but **material saving method**there is a difference.

* **Editor**where it applies only within the project **one-time save**is possible.
* **Dashboard**by modifying the product's own material **permanent saving**is possible.
  {% endhint %}

### Realistic Material Expression Using Effector

#### Key Properties

**Roughness**

* **1**The higher it is, the rougher the surface becomes
* **0**The lower it is, the smoother the surface appears

**Metalness**

* **1**The higher it is, the stronger the metallic feel (increased reflectivity)
* **0**The lower it is, the weaker the metallic feel (non-metal material)

**Opacity**

* **1**The higher it is, the more opaque it becomes
* **0**The lower it is, the more transparent it becomes (e.g., glass)

### Typical material value examples

| **Material Type** | **Roughness** | **Metalness** | **Opacity** |
| ----------------- | ------------- | ------------- | ----------- |
| Wood              | 0.8           | 0             | -           |
| Curtain           | 0.98          | 0             | 0.2         |
| Plastic (glossy)  | 0.3           | 0             | -           |
| Plastic (matte)   | 0.9           | 0             | -           |
| Mirror            | 0             | 1             | -           |
| Glass             | 0             | 1             | 0.2         |
| Wood (glossy)     | 0.3           | 0             | -           |
| Fabric            | 0.9           | 0             | -           |

### Want a more realistic material expression?

Try using the Normal property!

**What is a Normal Map?**

A normal map is a feature that expresses detailed surface bumps, **adding depth to the texture to create a more realistic material**.

**Normal Map application effect**

* Adds fine details to the surface (e.g., wood grain, fabric texture, etc.)
* Expresses shading and a sense of depth without adding actual modeling
* Can be combined with roughness, metalness, etc. for a more vivid expression

{% hint style="info" %}
You will need to prepare the image to apply to the normal map yourself.
{% 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://docs.archisketch.com/guide/enterprise-en/manage-furniture/modify-furniture-finishing/effector.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.
