---
name: "ctrlSetFade"
type: command
status: ok
groups: ["GUI Control"]
arma3_since: "0.50"
locality: {"argument": null, "effect": null, "server_exec": false}
source: https://community.bistudio.com/wiki/ctrlSetFade
revid: 369232
updated: 2024-09-03T10:35:00Z
---

# ctrlSetFade

*Command · GUI Control · Arma 3 v0.50 · introduced in Armed Assault v1.00*

## Description

Sets wanted transparency for control animation. Requires [ctrlCommit](../commands/ctrlCommit.md) to commit changes. To hide or show a control instantly, use [ctrlShow](../commands/ctrlShow.md).

> [!NOTE]
> If there are multiple (interactable) controls on top of each other but the top-most control is faded using `ctrlSetFade 1`,
> this control will interfere with other controls that were defined earlier and in the exact same position.
> To counter that, the faded control **must** be disabled with [ctrlEnable](../commands/ctrlEnable.md).

## Syntax

```sqf
controlName ctrlSetFade fade
```

**Parameters:**

- `controlName`: [Control](../topics/Control.md)
- `fade`: [Number](../topics/Number.md)

**Returns:** [Nothing](../topics/Nothing.md)

## Examples

### Example 1

```sqf
_control ctrlSetFade 1;
_control ctrlCommit 5;
```

## Problems

Despite having `fade = 1;` in a control's config, [ctrlFade](../commands/ctrlFade.md) will still report a fade of 0 - resulting in `ctrlSetFade 0` doing nothing.

To counter that, first use `ctrlSetFade 1`, then `ctrlCommit 0` to apply it, and only then [ctrlSetFade](../commands/ctrlSetFade.md) can be used as usual.

## See also

[ctrlFade](../commands/ctrlFade.md) · [cutFadeOut](../commands/cutFadeOut.md) · [ctrlCommit](../commands/ctrlCommit.md)

## Community notes

**Nelis75733126** — 2024-04-16

in Arma 3 2.17, when `ctrlSetFade` is used on a CtrlToolbox or RscToolbox, it only has effect on the text of it.

<sub>Source: [BI Community Wiki — ctrlSetFade](https://community.bistudio.com/wiki/ctrlSetFade) (revision 369232).</sub>