Your workspace starts
on Windows

Bring SysCubes widgets and controls to your Windows PC. SysCubes for Windows is available to download via Overwolf. Copy this page to plan your setup on your computer.

Recording troubleshooting

Game recording not working? Get your next clip ready.

Keep the next good play with a capture routine you have checked. Start with one practice clip, follow the result from save control to local file and verify picture and sound. SysCubes keeps recording beside your PC controls; these checks help you make that workflow ready for your next session.

By SysCubes documentation team · Content reviewed

  • 30s default Replay
  • Picture, audio & files
  • A clear first-save routine
SysCubes screenshot and recording controlsExample setup · sample data
Explore the interactive preview
Get your capture workflow readyManual checklist
0 / 4 checks marked
Follow one capture path

Try each step in SysCubes, then mark it here. Use the latest save message and a fresh playable clip to confirm what worked.

Choose the symptom and follow this manual checklist beside SysCubes. Mark each check after trying it.

Quick answer

Start with a new clip and its actual result

If game recording or Replay is not working, test one recorder first. SysCubes Replay defaults to 30 seconds and must be enabled before saving. Stop manual recording, save a fresh sample and inspect its path and playback. Missing files, black pictures and missing audio need different checks.

Isolate the failure

Run one deliberate capture test

Use the capture widget and its save confirmation as the starting point. Read the latest error before restarting. Choose a practice scene with obvious movement and sound, and avoid troubleshooting during a match you want to keep.

  1. Confirm the installation and source

    These checks describe the current Windows Overwolf build. A supported active game uses game capture; outside a game, Capture display selects a desktop monitor. A desktop test and a game test exercise different sources.

  2. Choose one capture mode

    Stop manual Record before enabling Replay. Start at the 30-second history default, let the counter fill, and save a new sample with the widget button. Try the assigned shortcut only after the button path works.

  3. Wait for the result

    Allow the pending save to finish. Holding the shortcut will not create useful extra exports. Read the new confirmation or error rather than relying on a notification from a previous clip.

  4. Open the returned file

    Play it in a separate media player. Confirm the picture, sound and opening context. If these are correct, repeat in the game and display mode you actually use before restoring other recording workloads.

SysCubes saves Replay when you choose the moment to keep. Enable history before playing and save afterward. Overwolf's Replay documentation explains the background history and export stages behind that workflow.

Use the dedicated Record and Replay controls to prepare one short test before an important session.Example setup · sample data

Know what the controls mean

The capture values worth checking

Current SysCubes Overwolf capture configuration
SettingVerified valueTroubleshooting implication
Replay history5-40 seconds; 30-second defaultNewly started or restarted history must fill again.
Recording qualityYour chosen preset; 1080p at 30 fps by defaultCheck the saved file's actual resolution, motion and playback.
Capture modes1 active mode: Record or ReplayStop the other mode before switching.
Audio defaultsSystem audio on; microphone offCheck each switch and listen to a fresh sample.

Shortening history changes retained footage, not all encoding work. The current UI does not expose a capture bitrate or quality-preset slider. For game slowdown, compare the same scene with capture off and on using the FPS drop diagnostic workflow.

Check the capture settings and audio choices before testing the saved picture and sound.Example setup · sample data
If a replay cannot be saved, an in-game toast says so. Open SysCubes for the details before trying again.Example setup · sample data

Use the evidence

Match the symptom to the next check

A failed key, failed capture and failed move are different problems
SymptomNext check
Save Replay is unavailableEnable Replay; confirm Record is stopped and wait for fresh history.
Button works, shortcut does notCheck this game's binding, focus and Replay registration.
Black or empty pictureCheck the game source, competing recorders and Overwolf GPU compatibility guidance.
Video saved, destination emptyOpen the returned path; relocation may have failed after capture succeeded.
Picture works, audio absentTest System audio and Microphone; game filtering can exclude another app.

If the message says no video is available yet, keep playing briefly and try a new save. Turning Replay off discards its current history. Switching between desktop and game sources can restart the buffer, so wait for new history rather than assuming the old scene remains available.

For black frames or stuttering, follow Overwolf's capture checks for drivers, competing recorders and dual-GPU compatibility. Change one item and repeat the same sample. If the clip plays correctly elsewhere, the original player may be the problem.

For storage errors, check free space and the chosen folder's access. Preserve the original capture when relocation fails. The save path is stronger evidence than a guessed folder name; do not delete captures to test whether the destination is working.

Make each test useful

Keep the result, simplify capture and listen to the file

01. Keep the message and file path

Read the latest result before restarting, then make a fresh test after any reset. This preserves the clue you need while the new Replay history fills.

  • Preserve the result

02. Test one recorder at a time

Use one capture service for a clear comparison. Once a playable sample succeeds, restore other tools individually and check the same scene again.

  • One capture path

03. Listen to the saved sample

Check game sound and your optional microphone in the actual file. In-game audio filtering can exclude other apps such as Discord, so verify each sound source you want before the session.

  • Verify the file

A useful support handoff

If a clean test still fails

Keep the game name, Windows and SysCubes build, display mode, GPU driver version, selected capture mode, exact error and returned path. Describe whether the same test fails on the desktop, in the game, or only in one player. Share a short non-sensitive sample when appropriate.

The game recorder and clipping feature lists the supported workflow. Once your test succeeds, prepare Replay for the next session with the same verified source, settings and shortcut.

Your questions, answered

Recording troubleshooting FAQ

What should I check first when game recording or Replay is not working?

If game recording or Replay is not working, test one recorder first. SysCubes Replay defaults to 30 seconds and must be enabled before saving. Stop manual recording, save a fresh sample and inspect its path and playback. Missing files, black pictures and missing audio need different checks.

Why does Save Replay work in the widget but not with the shortcut?

Check the active game's binding and make sure that game has focus and Replay is active. A new profile defaults to Alt+S, but existing profiles can differ. The Save Replay shortcut is registered only while Replay is on. A successful widget save narrows the problem to the key path.

Can I enable Replay and manual recording together?

No. These capture modes are mutually exclusive in the current SysCubes Overwolf implementation. Stop Record before enabling Replay, or turn Replay off before starting Record. A registration or button label does not override this prerequisite; read the action's result before trying another capture.

Why is the beginning of my clip missing?

Replay cannot recover history from before it started or before a source restart. The history setting is 5-40 seconds, with a 30-second default. Allow the fresh buffer to fill and save promptly after the action. Older footage leaves the rolling window as you keep playing.

Where is my recording if moving it to the selected folder failed?

Read the error and the returned original path. SysCubes moves finished video from Overwolf's capture location to the chosen destination. If relocation fails, the original path remains available. Open and preserve that file before retrying; a failed move does not necessarily mean capture failed.

Will disabling the overlay fix game capture?

Capture actions have their own prerequisites and can work independently of the overlay being visible. An absent overlay is therefore not proof of a capture failure. Check the game source, recording mode, actual capture error and saved file. Use the separate overlay troubleshooting page when the HUD itself is missing.

Your PC. In your hands.

Keep capture ready beside your PC controls.

Save your successful test and use the same source, audio settings and shortcut for your next session. Download SysCubes for Windows free to start clipping your gameplay today.

Download SysCubes for Windows

Your workspace starts
on Windows

Bring SysCubes widgets and controls to your Windows PC. SysCubes for Windows is available to download via Overwolf. Copy this page to plan your setup on your computer.

Free • No credit card or account needed • Instant 1-minute setup • Windows 10/11