Wwise UE Fixer

Repeated Perforce syncs broke Wwise references in Unreal. I automated the repair path from manual reconnecting to a backup-first button press.

Role Tool Developer
Type Dev Tool
Year 2024-2025
Stack Batch Script, Python
Python Batch Script Wwise Unreal Engine Perforce

Why This Exists

Repeated Perforce syncs on Shadow Frames followed the same pattern. Sync, open the project, silence. Wwise paths broken, actors muted, plugin settings missing. Then about 20 minutes of manually reconnecting things before anyone could hear a single sound.

After the third morning in a row doing this, I wrote a script. It checks Wwise-related project and config references, validates selected asset paths, restores plugin settings, and rebuilds the configs it can safely touch. One click. It timestamps a backup of your project first, because I learned the hard way what happens when you do not.

The Shadow Frames team used it after Perforce syncs. In our daily workflow, a repair that took about 20 minutes by hand became a roughly 10-second button press. It started as a small internal tool, then became a faster way for the team to get audio working again after syncs.

How It Works

Detects Broken References

Walks Wwise-related project and config references, plus selected asset paths. If a Wwise reference points to nothing, it flags it and lists the dead links it can detect.

Rebuilds the Repair Path

Restores plugin settings, updates configs, and rebuilds the broken Wwise references it detects. The same repeated manual repair path, except it takes seconds.

Archives Before Changes

Timestamps a full backup of the project before changing a single file. If anything goes wrong, the team can roll back instead of guessing which config changed.

Features

Change Log

Files it touches get logged with a reason. When someone asks "what did your tool do to my project?" you can show them line by line.

Leaves Non-Audio Files Alone

The repair path is scoped to Wwise-related files. Blueprints, meshes, levels, and materials stay outside that path.

Used on a Real Project

We used it daily on Shadow Frames while the full team pulled from Perforce. During production it stayed within Wwise-related files and backed up the project before changes, which mattered more than any feature list.