Elvis

Partial
Completion13%

Stern2004stern.elvis.2004 Updated 2026-08-30

OPDB IPDB stern/elvis-2004.mdstern/elvis-2004.json

Wire it up

what an authoring tool needs first
Bind this ROM
elvis

21 ROM sets resolve to this machine. Clones share the definition unless a hardware difference is listed.

Controller platform
Not determined
Displays

No display inventory recorded yet.

Address space
Switches
11–62 (15)
Solenoids
1–18 (4)

Coverage

Partial

Real evidence exists, but authoring requirements are still missing or in conflict. Verify before shipping a table.

Completion13%

Progress is derived from the fixed author-readiness requirements. It helps rank unfinished work, but only a 100% author-ready definition passes the publication gate.

Catalog Identity
validated
Address Enumeration
unknown
Semantic Naming
unknown
Physical Wiring
unknown
Mechanisms
unknown
Variant Coverage
candidate
Recreation Knowledge
unknown
Still missing · 14
Driver MappingController PlatformInput EnumerationInput SemanticsOutput EnumerationOutput SemanticsDisplay InventoryMechanism InventoryMechanism BehaviorPolarityVariant DifferencesRecreation NotesProvenanceSpatial Placement

Switches

The addresses PinMAME reports as closed. Numbers are the public API values, not matrix hardware pins.

15 addresses

Switch map

Sequential addresses, grouped in columns of eight.

used unused
 
+0
+1
+2
+3
+4
+5
+6
+7
1–8
9–16
17–24
25–32
33–40
41–48
49–56
57–64
Hover or tap an address to identify it.
15 shown
# Name Device ID Evidence
11
Trough1
switch.trough1 candidate
12
Trough2
switch.trough2 candidate
13
Trough3
switch.trough3 candidate
14
Trough4
switch.trough4 candidate
15
Trough Jam
switch.trough-jam candidate
16
Shooter
switch.shooter candidate
54
Start
switch.start candidate
55
Slam Tilt
switch.slam-tilt candidate
56
Tilt
switch.tilt candidate
57
Left Outlane
switch.left-outlane candidate
58
Left Inlane
switch.left-inlane candidate
59
Left Sling
switch.left-sling candidate
60
Right Outlane
switch.right-outlane candidate
61
Right Inlane
switch.right-inlane candidate
62
Right Sling
switch.right-sling candidate

Controlled devices

Everything the ROM can energise, grouped the way a table author builds it.

Coils, magnets & motors

4
4 shown
# Name Device ID Evidence
1
Trough
coil.trough candidate
2
Launch
coil.launch candidate
17
Left Sling
coil.left-sling candidate
18
Right Sling
coil.right-sling candidate

Recreation notes

Working knowledge that has no schema field yet — edition differences, tuning values, pitfalls.

Coverage: partial - machine identity plus candidate-only I/O attachments. Playfield devices, wiring, mechanisms, and behavior are evidenced only as unverified candidates.

This record was promoted from the generated catalog stub stub.pinmame.elvis by the catalog-wide identity pass of 2026-08-29. The promotion resolves machine identity and carries the catalog's residual driver grouping over unchanged, the platform and device attachments below were added by the 2026-08-29/30 candidate passes and assert nothing beyond candidate provenance. Every requirement in the definition's coverage.missing is genuinely outstanding.

Identity

  • PinMAME catalog: root driver elvis, description "Elvis (5.00)", manufacturer "Stern", catalog year "2004".
  • OPDB record G4qbX-MJw5r (IPDB 4983) names this machine "Elvis" (Stern, manufacture date 2004-08-01); the resolved identity rests on the agreement of the PinMAME catalog and this reviewed mapping.
  • The definition's driver list is exactly the clone tree PinMAME declares under elvis; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • elv100 (2004, Stern, clone of elvis).
  • elv302 (2004, Stern, clone of elvis).
  • elv302f (2004, Stern, clone of elvis).
  • elv302g (2004, Stern, clone of elvis).
  • elv302i (2004, Stern, clone of elvis).
  • elv302l (2004, Stern, clone of elvis).
  • elv303 (2004, Stern, clone of elvis).
  • elv303f (2004, Stern, clone of elvis).
  • elv303g (2004, Stern, clone of elvis).
  • elv303i (2004, Stern, clone of elvis).
  • elv303l (2004, Stern, clone of elvis).
  • elv400 (2004, Stern, clone of elvis).
  • elv400f (2004, Stern, clone of elvis).
  • elv400g (2004, Stern, clone of elvis).
  • elv400i (2004, Stern, clone of elvis).
  • elv400l (2004, Stern, clone of elvis).
  • elvis (2004, Stern).
  • elvisf (2004, Stern, clone of elvis).
  • elvisg (2004, Stern, clone of elvis).
  • elvisi (2004, Stern, clone of elvis).
  • elvisl (2004, Stern, clone of elvis).

PinMAME source contract (candidate)

  • The pinned PinMAME source declares elvis at src/wpc/sims/se/prelim/elvis.c:426 with machine module de_mSES3; no platform is declared (the de_mSES3 module serves several manufacturers and this record's catalog manufacturer (Stern) is not Data East).
  • The driver source's named switch/solenoid symbols are carried as 19 candidate devices in the definition.

What a curator must establish next

Controller platform from the pinned PinMAME driver source; full input, output, and display enumeration with semantic names; physical wiring and polarity; mechanism inventory and behavior; variant differences across the clone tree; recreation knowledge from a manual, schematic, or known-working table; runtime provenance; and a normalized spatial placement for every physical device. No manual, schematic, or runtime-harness evidence is retained for this machine yet; the candidate sections above are the only retained I/O evidence so far.

ROM sets

Every driver that resolves to this physical machine.

ROM set Description Year Parent Hardware
elvislElvis (5.00 Spanish) 2004elvis—
elvisiElvis (5.00 Italian) 2004elvis—
elvisgElvis (5.00 German) 2004elvis—
elvisfElvis (5.00 French) 2004elvis—
elvisElvis (5.00) 2004——
elv400lElvis (4.00 Spanish) 2004elvis—
elv400iElvis (4.00 Italian) 2004elvis—
elv400gElvis (4.00 German) 2004elvis—

Parent set: elvis — clones share this definition unless a hardware difference is noted.

Pinball memory maps

External source LGPL-3.0-only1 map

RAM layouts published by an independent project and mirrored here at a pinned commit. They are not part of this machine’s definition: nothing below was used as evidence for the definition, and none of it counts towards coverage. Check claims against the upstream project.

Upstream
tomlogic/pinball-memory-maps
Commit
d8693b9

This program makes use of content from the Pinball Memory Maps project.

elvis.map.json

whitestarv5format 0.8

maps/stern/whitestar/elvis.map.json

Applies to ROMs
elv100elv302elv302felv302gelv302ielv302lelv303elv303felv303gelv303ielv303lelv400
Sections
game_statehigh_scores
Map JSONMap sourcePlatform JSONPlatform source

whitestar defines the RAM layout this map’s offsets are read against — the map is not interpretable without it.

Evidence

Every claim above traces to one of these. When they disagree: a known-working VPX script wins on controller addresses and causality, the manual wins on wiring and construction, pinned PinMAME wins on emulator routing and display layout.

  • PinMAME catalog

    BSD-3-Clause

    pinmame.catalog.8371478a7640

    PinmameGetGames

    8371478a7640
    by
    PinMAME contributors
    rev
    8371478a7640

  • PinMAME source

    BSD-3-Clause

    pinmame.driver.elvis

    src/wpc/sims/se/prelim/elvis.c switch/solenoid #define block

    src/wpc/sims/se/prelim/elvis.c
    by
    PinMAME contributors
    rev
    8371478a7640
    sha256
    9d36797b3426…

Something wrong or missing?

This definition still has 14 unmet requirements, listed under Missing data below. Fixes belong in the definition itself — editing on GitHub forks it for you and opens the pull request.

Cite a source for anything you change — a manual page, a line in a working VPX script, PinMAME source, or a reading from the machine's own service menu. Claims without provenance cannot be validated.

Edit the definition Edit the note Report a problem
Before you startCONTRIBUTING.mdschemas/machine.schema.jsondocs/MACHINE_DEFINITIONS_PLAN.md How to read a definition

Missing data

What this game definition still needs to reach 100% and become author-ready.

  • ROM compatibility

    Verify which PinMAME drivers and firmware variants belong to this physical machine.

  • Controller hardware

    Identify the controller platform and validate its public address and routing rules.

  • Complete input inventory

    Account for every switch, service input and diagnostic address, including unused positions.

  • Input functions

    Validate which physical sensor or cabinet control each input represents and when it activates.

  • Complete output inventory

    Account for every coil, motor, lamp, flasher and general-illumination circuit, including unused addresses.

  • Output functions

    Validate the physical device, function and fitted quantity behind each output binding.

  • Displays

    Verify every display, its layout and its controller bindings.

  • Mechanism inventory

    Document every mechanism, its moving parts, actuators, sensors and connections.

  • Mechanism behavior

    Validate mechanism operation, ball paths, home positions, startup and reset behavior.

  • Switch construction and polarity

    Verify normally open or closed contacts and how PinMAME delivers their active states.

  • Edition and firmware differences

    Document supported hardware and firmware differences without combining incompatible editions.

  • Recreation knowledge

    Complete the source-backed behavior and assembly notes needed to recreate the machine.

  • Evidence and sources

    Back the remaining claims with attributable sources, exact locators, retained excerpts and verified hashes.

  • Physical device locations

    Establish validated playfield locations for every physical sensor, actuator and light emitter, including bulb counts and justified projections.

Missing locations · 19