Skip to content

Troubleshooting

Start with the boundary that causes most confusion: ArcadeStudio edits the workshop state, while ArcadeServer runs the last published cabinet bundle. Saving, rebuilding, installing, and publishing are separate actions.

  1. Save the page you changed. Publish copies saved state, not an open editor draft.
  2. If a Data Pack says Requires DB rebuild, open Data Management → Workshop and select Rebuild Master.db.
  3. Open Publish and publish the cabinet bundle.
  4. Confirm ArcadeServer is running and using that bundle.

Do not point ArcadeServer at Studio’s working database. The server consumes the published copy.

Publishing requires an active trial or license. The current development build starts with a 30-day trial; after it expires, Studio remains available but Publish is blocked until a valid license key is saved in Settings.

Also review Home → Needs attention for unsaved cabinet or LED work and pending database rebuilds.

A Data Pack still says Requires DB rebuild

Section titled “A Data Pack still says Requires DB rebuild”

The Rebuild catalog action on the Data Packs page refreshes the shop catalog only. It does not update Master.db.

Open Data Management → Workshop, review the installed enrichment, preview the build, and select Rebuild Master.db. Then publish the resulting cabinet bundle.

  • Confirm ArcadeServer is running; it may be in the notification area when background mode is enabled.
  • Refresh server discovery in Studio.
  • Confirm Studio and Server are using the same pairing token.
  • Review local firewall or network restrictions if the server is on another cabinet machine.

Keep the pairing token private. Release-mode server requests are expected to authenticate with it.

ArcadeServer records unmatched observations for Data Management → Inbox. Review the observation, fix catalog identity in Data Management, rebuild Master.db when needed, and publish again.

Use a local rule override only when catalog identity is correct and the remaining problem belongs to Detection or routing behavior.

  1. Open Hardware and select Find devices.
  2. Register the device with a logical type and primary player.
  3. Bind it to the saved Cabinet map.
  4. Return to Controllers, save the setup and mapping, then test it with ArcadeServer.

The Identify device listener currently handles supported pointer or motion activity. Keyboard and button-board HID devices must be selected from the discovery list instead.

A controller works in Studio but not in a game

Section titled “A controller works in Studio but not in a game”
  • Open Controllers → Test and select Check server readiness.
  • Confirm the mapping, tuning, and output plan were saved and published.
  • Check Priority and Rules only when more than one output route competes.
  • If the problem affects one game or emulator only, review its scoped profile rather than changing the device default.
  • Confirm ArcadeStudio Multi Overlay is installed in Data Packs.
  • Save the overlay profile and assign it to the intended machine, platform, or game.
  • Confirm the assignment is enabled.
  • Publish the cabinet again.
  • Confirm the official runtime package includes the backend used by the game process.

Studio preview is not proof that the published overlay is active on the cabinet.

The installer asks for administrator approval

Section titled “The installer asks for administrator approval”

ArcadeStudio and ArcadeServer are per-user applications and do not normally require administrator access. The optional ViGEm driver step can request elevation and may require a restart. HidHide is not installed by the ArcadeStudio installer.

Updating or uninstalling removed my configuration

Section titled “Updating or uninstalling removed my configuration”

The installer keeps user data during normal update and uninstall flows. If data appears missing, confirm you are signed in to the same Windows account and check the per-user ArcadeStudio data location before reinstalling or deleting anything.

Next: Getting started or FAQ.