Getting started
ArcadeStudio is the workshop. ArcadeServer is the consumer that runs on the cabinet. Your work reaches the cabinet only after you publish a bundle.
What you need
Section titled “What you need”- A Windows PC for ArcadeStudio
- A Windows cabinet PC for ArcadeServer, or the same PC for an initial setup
- ROMs and media stored on the machine that will play the games
Install both applications before continuing. See Installation.
Trial and license
Section titled “Trial and license”The ArcadeStudio trial lasts 30 days. During the trial, the workshop and Publish are available. When the trial ends, the workshop still opens, but Publish requires a license.
Enter the purchase email and license key under Settings. The license belongs to the workshop operator; it is not licensed per cabinet.
The first cabinet loop
Section titled “The first cabinet loop”- Open ArcadeServer on the cabinet, then open ArcadeStudio. Home shows cabinet state, items that need attention, and the next action. Detailed runtime diagnostics remain behind Runtime log.
- Open Data Packs and install the packs you need.
- Open Data Management → Workshop and enable the installed packs in the Data Build Profile.
- Preview the build, then rebuild the working
Master.dbwhen Workshop asks for it. - Open Catalog to inspect games and Inbox to resolve unmatched play.
- Map the cabinet in Hardware, Controllers, and Cabinet. Save the cabinet before assigning LED channels.
- Open LED and assign channels to lights marked Needs channel.
- Review Rules, Automation, and Launch for behavior this cabinet needs. Test launches are sent through ArcadeServer.
- Use Overlay Editor to preview and assign the game-screen overlay when required.
- Open Publish, review readiness, and publish the cabinet bundle.
- Run the cabinet from ArcadeServer using that published bundle.
Three boundaries to remember
Section titled “Three boundaries to remember”Install is not enable
Section titled “Install is not enable”Data Packs installs packages. Data Management → Workshop enables optional data layers in the build profile.
Rebuild is not publish
Section titled “Rebuild is not publish”Rebuild updates Studio’s working Master.db. Publish copies the current working catalog and enabled rules snapshot into a cabinet bundle; it does not rebuild the catalog for you.
Server does not read the live workshop
Section titled “Server does not read the live workshop”ArcadeServer opens the published Master.db inside the bundle. It does not use Studio’s live working catalog as a second database.
Next: Data packs or ArcadeServer.