If The Choicer Voicer keeps crashing, first record the exact boundary: before the main menu, while opening Settings, when leaving Settings, after selecting an audio device, when loading a pack, or during a Dub scene. Those are different failure paths. There is no published universal crash fix, so protect your working files and isolate one change at a time.
Preserve the evidence before reinstalling
Take a screenshot of the last visible screen and note the action immediately before the crash. If a terminal, Windows dialog, or log displays an error, save the text. Record the operating system, game version, archive name, selected input and output, and the newest pack or tool added.
Do not delete the entire folder as a first move. Copy custom-content folders, readmes, and source links to a separate backup. A blind reinstall can remove the file that caused the problem without teaching you which change to avoid, and it can also erase a previously working pack collection.
Create a clean official baseline
Download the current archive from YeahMaybe’s official itch.io page and extract it into a new empty folder. Do not place it on top of the crashing copy. Connect one microphone and one stereo output before launch, then close virtual mixers, voice changers, broadcast tools, and other applications controlling the same devices.
Run this baseline without community packs, a mod manager, or copied settings:
- Reach the main menu and wait for a minute.
- Open Settings without changing anything, then return to the menu.
- Select the intended microphone and output, save, and return again.
- Run one default prompt and listen to the saved take.
- Close and relaunch once before adding custom content.
| Baseline result | Next move |
|---|---|
| Clean copy crashes before the menu | Preserve the error and report system/version details |
| It crashes only after selecting a device | Simplify the audio path and test one device change |
| Settings works until old files are copied | Restore settings and packs separately |
| Default content works but one pack crashes | Remove that pack and inspect its structure and media |
| Standard play works but one Dub scene crashes | Test the OGV video and the pack metadata separately |
If the crash started after a pack or mod
Remove only the newest addition and repeat the exact action. Extract archives to a staging folder before copying them into the game, preserve their top-level directory, and stop if an ordinary content pack unexpectedly includes an executable. Use the GameBanana and mods guide to distinguish data packs from tools that change game behavior.
If several packs were added together, restore the clean backup and return them one by one. Launch and complete one default prompt between additions. This takes longer than copying a large modpack once, but it identifies the failing archive and keeps creator credits attached to the correct source.
If Settings is the crash boundary
Opening or leaving Settings can touch audio-device and configuration state. Begin with devices connected before launch and avoid switching between Bluetooth profiles mid-session. Change one input or output, return to the menu, and relaunch before changing another setting. If the clean copy succeeds, compare old configuration files without copying every file at once.
Do not treat a moving microphone meter as proof that saving the selected route will succeed. Complete a saved-playback test after the settings round trip. If the game remains open but the recording is silent or delayed, move to the silent-microphone guide or mic-delay guide instead of continuing crash steps.
Current Dub crash and preservation status
Two August 2026 topics in the official itch.io community contain repeated reports of crashes during Dub sessions, including short and long packs and both Windows and Linux experiences. They do not establish a single hardware cause. One thread also includes a Settings crash report, which is why the clean settings round trip above is kept separate from a long-session test.
On August 20, the developer replied that the next version was being tested with a “dub preservation” feature intended to save each clip during play and offer recovery after a crash. That is a planned recovery feature, not a released 0.5.2 crash fix, and the reply did not give a version number or release date. Check the official store before relying on it. Until it appears in a released file, assume an interrupted Dub session may still lose progress.
Some players report different results with a compatibility build or particular packs, while others report no improvement. Treat either result as a test for that installation, not a universal recommendation.
Report a reproducible sequence
A useful report is short and exact: “On Windows 11 with 0.5.2, the clean archive reaches the menu, then closes after I select device X and leave Settings.” Add whether the official demo behaves the same way and whether default content was used. Link the original page for any pack involved. Avoid declaring a version-wide defect from a single modified installation.