Start by reproducing the symptom in the free No Gameplay Demo, then choose one branch: no input detection, a silent saved recording, silent playback, a wrong platform file, or a Pack that does not load. Keep the base game and one recent change separate while you test.

Unofficial symptom guide; not a guaranteed repair
Community reports can identify symptoms. Only the developer can confirm engine fixes or platform support. A 0.5.2-dev2 microphone test build is available, but it is not a stable release or a guaranteed repair.
Applies to: Current public microphone, recording, playback, platform, Pack-loading, and optional microphone-test-build guidance
Last checked: Aug 13, 2026
Official Aug 6 microphone test-build noteUse the free compatibility demo before changing Pack folders. These checks begin with the least risky changes and do not promise a single fix for every device.
Use this branch when the game cannot see the intended microphone or freezes while you select or change it. Record the version and device, restart, then test one direct microphone in the Demo before changing Packs.
If you can reproduce a recording problem on the stable release, the developer offers 0.5.2-dev2 specifically for feedback. It is not a stable release: note your operating system, selected device, and whether recording and playback change before reporting a result.
Use this branch when input appears active but a saved take is empty. Keep the baseline direct and test the Demo before changing Pack files.
Use this branch when the game shows a saved take but you cannot hear it. Focus on output selection and one direct playback path.
If a file opens in the wrong app on Windows, confirm you did not download the Linux build. Windows players should use the Windows executable package.
Remove the newest Pack folder, confirm the base game still works, then check the Pack type, target folder, file structure, and any Dub Pack OGV or metadata requirements.
In the official Aug 3, 2026 Q&A, the developer linked many recording reports to a Godot audio issue that may be more common with surround or multichannel setups. They described testing engine changes without reaching a general fix. This is useful context, not proof that any one player's device has the same cause.
The Aug 6 0.5.2-dev2 build is meant to test a possible microphone fix, not to certify every device. Confirm the same symptom on the stable release first, then report whether the test build changes detection, recording, playback, or stability.
Before changing drivers, virtual devices, or Pack folders, use one direct microphone and output path in the Demo. Record the version, device, and exact symptom so a result can be reproduced.
The developer's Q&A distinguishes an unresolved engine limitation from a guaranteed user-side fix. Recheck it when a new official version or support note appears.
Record the selected input, output, operating-system device, and whether the Demo can detect, save, and play back a short line.
If you test a virtual device, surround setting, external sound card, or streaming tool, change one item only and restart before retesting.
Restore the direct microphone and output path if the new route changes the symptom or creates a different failure.
Ready for a first round
Practical answers for the problems players keep repeating.
Next step
Once microphone recording and playback are stable, content packs are the fastest way to make the game feel complete.