FAQ

What is the difference between ArcadeStudio and ArcadeServer?

ArcadeStudio is the workshop where you prepare catalog data, cabinet hardware, controls, media, overlays, rules, automation, and launch behavior. ArcadeServer is the cabinet runtime. It consumes a published cabinet bundle and does not read Studio’s open editors or working files live.

Is ArcadeStudio available to download?

Not publicly yet. The website and documentation describe the current development build. A verified public download URL, supported-version matrix, and release date have not been published.

Does ArcadeStudio require administrator access?

Normal ArcadeStudio and ArcadeServer installation is per user and does not require administrator access. Installing the optional ViGEm driver can request elevation and may require a restart.

Does the installer add HidHide?

No. The current installer does not install HidHide.

What happens to my data when I update or uninstall?

Normal update and uninstall flows preserve per-user ArcadeStudio data. The optional driver is also left installed rather than silently removed.

How long is the trial?

The current development build evaluates a 30-day trial. The workshop remains available after the trial, but Publish requires an active trial or valid license.

Why did installing a Data Pack not change my cabinet?

Install only places the package content in Studio. Depending on the pack, you may still need to enable a layer, rebuild Master.db, map hardware, save a profile, turn an Automation flow Live, or publish the cabinet.

What is the difference between Rebuild catalog and Rebuild Master.db?

Rebuild catalog on the Data Packs page refreshes the shop catalog. Rebuild Master.db in Data Management → Workshop rebuilds the working game catalog and applies installed metadata enrichment.

Can ArcadeServer use Studio’s working Master.db?

No. ArcadeServer uses the Master.db included in the last published cabinet bundle. This keeps editor state separate from runtime state.

Where do unmatched games go?

When ArcadeServer cannot match a running game against the published catalog, it records an observation for Data Management → Inbox. Review the observation in Studio, correct the catalog identity, rebuild when required, and publish again.

Are official rules editable?

No. Official rules are read-only. Override creates a separate local draft; turning off My override returns the area to the lower official or optional layers.

Does Studio preview mean an overlay is live?

No. Preview checks the design inside Studio. Save the profile, assign it to a machine, platform, or game, and publish before ArcadeServer can activate it.

Which overlay backends are in the current build?

The official runtime and editor support DX11, DX12, OpenGL, and Vulkan. The cabinet chooses the backend used by the game process. Community-supplied native overlay DLLs are not supported in this build.

Where should I configure a controller?

Use Hardware to register the physical device, Cabinet to bind it to players and controls, Controllers to map and tune it, and Rules only when routes compete or fallback behavior needs to change.

Is Controller Automation the same as Automation?

No. Controller Automation handles controller-specific orchestration. The main Automation workspace handles room behavior such as lights, displays, and audio.

Where can I find public system requirements and compatibility lists?

They have not been verified for a public release. This documentation intentionally does not claim support for specific Windows editions, emulators, frontends, controllers, or cabinet hardware beyond behavior present in the current repositories.

Next: Troubleshooting or Releases.