> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.playability.gg/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Improve PlayAbility Performance and Resolve Power Warnings

PlayAbility performs best when the computer is plugged in and the operating system is not limiting performance. Its GPU preference and the operating-system power mode are separate controls: changing one does not change the other.

## Resolve a battery or power-mode warning

PlayAbility displays a yellow alert at the bottom of the window when the computer is running on battery or a detected power mode can reduce performance.

1. Read the alert to determine whether it reports battery power, an energy-saving mode, a reduced-performance mode, or a combination.
2. Connect the computer to AC power when possible.
3. If the alert includes **Open power settings**, select it.
4. Choose an appropriate operating-system power mode:
   - **Windows:** Energy Saver, Better Battery, and Balanced can trigger a warning. Best, High, or Maximum Performance modes are accepted.
   - **macOS:** Turn off Low Power Mode. Automatic is accepted; High Power Mode is not required and is available only on selected Macs.
   - **Linux:** Power Saver triggers a warning. Balanced triggers one only when a Performance profile is also available.
5. Return to PlayAbility and allow the status to update.
6. Test tracking and the affected mappings again.

## Choose the PlayAbility GPU

1. Open **Settings → Advanced**.
2. Find **Performance Settings**.
3. Keep **Internal GPU (Recommended)** for normal use.
4. Select **Discrete GPU (Advanced)** only when you are investigating a specific graphics or tracking problem and the computer has a suitable discrete GPU.
5. When PlayAbility reports that a restart is required, select **Restart Now** or exit and reopen the app.
6. Test the same profile and trigger after the restart.

The GPU selection takes effect only after PlayAbility restarts. A discrete GPU can use more power and is not automatically faster for every computer.

## Reduce rendering while PlayAbility is in the background

1. Open **Settings → Advanced → Performance Settings**.
2. Turn on **Suspend UI when window is inactive**.
3. Focus the game or target application.
4. Confirm that PlayAbility continues processing the required mappings while performance-intensive PlayAbility pages stop rendering in the background.

This setting affects inactive-window rendering. It does not turn off **Main Output**.

## Verify the result

1. Restart PlayAbility if you changed its GPU preference.
2. Confirm that the yellow warning clears after AC power and an accepted power mode are detected.
3. Start the face, head, voice, or other detection required by the profile.
4. Turn on **Main Output** and the required output type.
5. Check live feedback for smooth, consistent trigger response.
6. Test the same action in the target game or application.

Change one setting at a time so you can identify which adjustment helped.

## Troubleshooting and limitations

### The warning remains while using a performance mode

The battery warning remains until the computer is connected to AC power, even when the selected performance mode is accepted.

On Windows, Balanced can still be classified as reduced performance. On Linux, Balanced warns only when the system reports that a higher Performance profile exists.

### Open power settings is not shown

Open the operating-system power settings manually when this shortcut is unavailable. It does not appear for a battery-only warning and may be unavailable on Linux.

### The warning was dismissed and did not return

Dismissing the alert hides the current incident. It becomes eligible to appear again only after all battery and reduced-performance warning conditions clear, then a new warning condition occurs.

### The GPU choice did not change

Select **Restart Now** or completely exit and reopen PlayAbility to apply the change.

### Discrete GPU performs worse or uses too much power

Return to **Internal GPU (Recommended)** and restart PlayAbility. The discrete option is an advanced troubleshooting choice, not a general requirement.

### Performance drops without a warning

The absence of a power warning does not rule out another performance problem. Check system temperature, cooling, other camera- or GPU-intensive applications, and operating-system diagnostics.

### Tracking is smooth in PlayAbility but slow in the game

Check foreground-app output rules, the active profile, the required output toggle, and the game's own performance.

## Related articles

- [Find Reliable Face Gestures with Face Tester](https://help.playability.gg/en/article/find-reliable-face-gestures-with-face-tester-1geknm/)
- [Use One Webcam with PlayAbility and OBS](https://help.playability.gg/en/article/use-one-webcam-with-playability-and-obs-1uljit0/)
- [Use Head Tracking as a Joystick or Mouse](https://help.playability.gg/en/article/use-head-tracking-as-a-joystick-or-mouse-2w0l5d/)
- [Troubleshoot Virtual Controller Output](https://help.playability.gg/en/article/troubleshoot-virtual-controller-output-2hf6eq/)