SysCubesA workspace for each game
Build a focused overlay for competitive play and a fuller dashboard for a longer session. SysCubes per-game profiles remember widget choices, overlay placement, shortcuts and supported app audio, so each recognized game starts with the workspace you prepared.
Playing Game A · Editing Game A
The editing scope and active game currently match.
Try separate dashboard and overlay choices, then create an example game from your defaults. Fictional games illustrate the settings; this preview does not inspect or change your PC.
Quick answer
Save the game's widget choices, overlay layout and shortcuts. New detected games copy your chosen defaults into their own profiles. Use Playing and Editing to see the live game and your settings target; audio follows the actual active game, while dashboard selection follows the editing scope.
Remember useful differences
Pick dashboard and compact Overlay widgets separately. A short competitive session can use a restrained HUD while a longer session keeps more reference tools on the second monitor. Saved choices belong to the selected game profile.
Rebind SysCubes actions for one game's conflicts without copying the change into every other profile. Defaults provide a starting point for newly detected games. Check that the action's prerequisites are satisfied when testing the shortcut.
Successful app volume and mute changes made during a game can be remembered for that active game's matching playback sessions. Apps must expose a live Windows audio session. This controls playback rather than separating captured audio tracks.
| Setting | Scope to understand |
|---|---|
| Dashboard widget visibility | Saved per game; New games provides the shared starting selection. |
| Compact overlay widget placement | Per-game visible widgets and layout from the ten eligible compact widgets. |
| SysCubes shortcuts | Copied into each new profile, then independently editable. |
| Saved app playback level/mute | The active game's matching live audio sessions. |
| Desktop grid arrangement | Shared across games; the dashboard widget selection is saved per game. |
| General widget settings | Shared where applicable; check the selected scope before editing. |
| GPU tuning and in-game graphics | Managed in their own game or driver interfaces. |
Check the name before you change a setting
The active game comes from the running-game information supplied by Overwolf. That game determines the actual in-game Overlay and the native audio profile. Selecting a different saved game in settings changes the edit target; it does not launch that game or change which process is active.
The widget list and dashboard selection use the editing scope, so a saved profile can be configured while another game runs. The interface can display Playing and Editing together. Use that distinction to prepare another game deliberately rather than interpreting a dashboard change as a change to the running Overlay.
Opening settings normally aligns the selected scope with the running game. If you then choose another profile, that is an editing choice for the current settings session. Check the scope again on your next visit, especially before changing a layout or shortcut.
A starting point, copied once
Choose a sensible baseline dashboard selection, supported Overlay widgets and positions, and shortcuts. Prefer the few controls you use in most games. This scope is also useful before a detected game has a saved profile.
The current native implementation creates a profile when it first recognizes a running game without one. It copies the current default selections and shortcuts. That gives the game its own editable choices rather than a permanent link to the defaults.
Select the new game profile, check placement and adjust conflicts. A later change under New games does not rewrite that existing profile. Update existing games individually when you want them to match a new baseline.
Auto-detection gives recognized games a useful starting workspace. Check overlay, capture and telemetry availability for the title separately, then refine the tools it supports. That keeps your baseline reusable while each game's overlay layout stays deliberate.
Two placement choices on one row
| Widget family | Dashboard | Compact Overlay |
|---|---|---|
| Performance, media, brightness, volume, timer | Available as desktop widgets. | Supported compact versions, subject to runtime/device capability. |
| Notes, tasks, stopwatch and network | Fuller list, timing and network controls. | Compact versions for supported games. |
| Capture | Recording, replay and screenshot controls. | Compact capture widget and supported action shortcuts. |
| Processes, incident reporting and calculator | Detailed inspection, reports and arithmetic tools. | Keep these three widgets on the dashboard; incident capture has a separate shortcut. |
Use the second-screen dashboard when a game needs reference tools without adding them over the scene. The setup guide explains the Windows display arrangement. For the HUD, choose only supported widgets and keep their placement clear of the game information you need.
Save the mix where it is used
While a game is active, successful per-app level and mute changes are saved against that game and an app identity. The native service can restore those stored values when the matching app playback session is present. An application with no live session cannot be controlled as though it were already playing.
Keep app levels with the game and choose the overall listening level separately. Windows master volume and output device remain separate controls; explicit audio presets can save those too. After changing the output, check the matching sessions on the new device.
Verify the playback result with the game, voice app and music source you actually use. If an app is missing, follow the missing mixer app checks. For captured sound, use the recording audio guide; live playback levels and independently recorded tracks are different concerns.
Make one useful profile first
Open SysCubes settings and check the game name. If no saved profile exists, the native runtime creates one from the current baseline. A name in the list does not prove that Overlay injection succeeded, so check the running game's status separately.
Set the two placement choices independently. Keep richer tools on the desktop and a small supported set over the game. Arrange the selected game's Overlay, then return to play and check that useful game information remains visible.
Use the hotkey controls for the selected game. Test one action at a time with the game focused and required modes enabled. Save Replay requires an active buffer; Overlay actions require that game's Overlay to be enabled.
With the intended game actually running, set the app session levels you want. Revisit a session and verify the relevant playback values and placements. Update only the differences that matter instead of rebuilding the entire workspace each time.
When something looks different
| What you notice | Check first |
|---|---|
| A widget changed on the desktop but not in-game | Dashboard and Overlay choices are independent; confirm the selected game and runtime Overlay status. |
| The wrong game seems to have been edited | Read the Playing and Editing names, then return to the current game scope. |
| Old games did not receive a new default | Expected: defaults initialize new profiles. Edit the saved game to update it. |
| An app's saved volume did not apply | Confirm the active game, output device and matching live playback session. |
| A shortcut is saved but does nothing | Check game focus, Overlay enablement where required, Replay state and binding conflicts. |
Try one profile, one placement and one action, then build from what works. A familiar workspace makes your chosen controls easier to find during play. Visit the download page to get SysCubes for Windows and start setting up your game profiles.
Your questions, answered
A profile remembers the dashboard widgets, supported overlay placement, overlay enablement, shortcuts and saved app playback levels for that game. Keep a focused HUD for one title and a richer workspace for another. The desktop grid arrangement stays shared across games; profiles change its widget selection. Live audio edits follow the active game.
The current Windows Overwolf implementation uses detected running-game information. When a recognized game has no saved profile, it creates one using the current new-game dashboard selection, Overlay defaults and default shortcuts. Game detection does not guarantee Overlay injection, event highlights or compatibility with every game.
No. New-game selections and shortcuts provide starting values when a profile is created. Existing profiles retain their saved choices. Change a particular game's scope when you want to update that game, and check each surface separately. A default change is not a bulk apply-to-all-games action.
Yes. The widget scope can point to a saved game other than the running one, and the interface distinguishes Playing from Editing. That selection does not switch the running game or redirect its live audio profile. Opening settings normally aligns the scope with the running game, so confirm it again before making changes.
Choose them separately so each screen gets the tools it needs. The current dashboard has 13 widgets; ten have compact overlay views, including performance, media, brightness, volume, timer, network, capture, stopwatch, notes and tasks. Processes, incident reports and calculator stay on the dashboard. The overlay requires a supported running game and enablement.
The native audio service saves successful per-app level and mute changes to the active game's profile and reapplies saved values to matching live audio sessions. An application must have an available playback session to control it. Master volume and output-device selection are separate from those saved per-app values; this is not recorded-audio track editing.
They bring back the useful widget choices, shortcuts and supported app audio you prepared for that game. Spend the session using a familiar workspace instead of rebuilding it. Profiles organize SysCubes controls; game graphics, driver tuning and gameplay automation remain separate.
Your PC. In your hands.
Keep your chosen widgets, shortcuts and app audio together in SysCubes. Download SysCubes for Windows free to build and customize your game profiles today.
Free • No credit card or account needed • Instant 1-minute setup • Windows 10/11