Heavy Metal Meltdown

Partial

Bally1987bally.heavy-metal-meltdown.1987

OPDB IPDB bally/heavy-metal-meltdown-1987.mdbally/heavy-metal-meltdown-1987.json

Wire it up

what an authoring tool needs first
Bind this ROM
hvymetal

2 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
3–35 (23)
Solenoids
10–11 (2)

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.

23 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
Hover or tap an address to identify it.
23 shown
# Name Device ID Evidence
3
Sw3
switch.sw3 candidate
4
Sw4
switch.sw4 candidate
12
Sw12
switch.sw12 candidate
13
Sw13
switch.sw13 candidate
17
Bumper1
switch.bumper1 candidate
18
Bumper2
switch.bumper2 candidate
19
Bumper3
switch.bumper3 candidate
20
Left Sling Shot
switch.left-sling-shot candidate
21
Right Sling Shot
switch.right-sling-shot candidate
22
Sw22
switch.sw22 candidate
23
Sw23
switch.sw23 candidate
24
Sw24
switch.sw24 candidate
25
Sw25
switch.sw25 candidate
26
Sw26
switch.sw26 candidate
27
Sw27
switch.sw27 candidate
28
Sw28
switch.sw28 candidate
29
Sw29
switch.sw29 candidate
30
Sw30
switch.sw30 candidate
31
Sw31
switch.sw31 candidate
32
Sw32
switch.sw32 candidate
33
Sw33
switch.sw33 candidate
34
Sw34
switch.sw34 candidate
35
Sw35
switch.sw35 candidate

Controlled devices

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

Coils, magnets & motors

2
2 shown
# Name Device ID Evidence
10
Pin Up Not
coil.pin-up-not candidate
11
Sol Pin Down Sol11
coil.sol-pin-down-sol11 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.hvymetal 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 hvymetal, description "Heavy Metal Meltdown", manufacturer "Bally", catalog year "1987".
  • OPDB record GRo3e-MQ7OW (IPDB 1150) names this machine "Heavy Metal Meltdown" (Bally, manufacture date 1987-01-08); 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 hvymetal; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • hvymetag (1987, Bally, clone of hvymetal).
  • hvymetal (1987, Bally).

VPX script candidates (candidate)

  • 1 retained community table script(s) declare this machine's driver; their extracted switch/lamp/solenoid/GI candidates are carried as 25 candidate devices. When curator work weighs sources, a retained script outranks emulator-derived candidates for runtime semantics, but every device here is still a candidate until a known-working table is verified against this exact physical machine.

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
hvymetalHeavy Metal Meltdown 1987——
hvymetagHeavy Metal Meltdown (German) 1987hvymetal—

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

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

  • VPX script

    vpx-script.e618ef7149c6b77d

    vpx-standalone-scripts: Heavy Metal Meltdown (Bally 1987)/Heavy Metal Meltdown (Bally 1987).vbs

    15d112648a1b
    by
    Authors credited in Heavy Metal Meltdown (Bally 1987)/Heavy Metal Meltdown (Bally 1987).vbs and repository contributors
    rev
    15d112648a1b
    sha256
    e618ef7149c6…

Something wrong or missing?

This definition still has 14 unmet requirements, listed under Coverage above. 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