Operation: Thunder

Partial

Gottlieb1992gottlieb.operation-thunder.1992

OPDB IPDB gottlieb/operation-thunder-1992.mdgottlieb/operation-thunder-1992.json

Wire it up

what an authoring tool needs first
Bind this ROM
opthund

1 ROM set 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
4–70 (28)
Solenoids
9–39 (21)

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.

28 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
65–72
Hover or tap an address to identify it.
28 shown
# Name Device ID Evidence
4
Start Button
switch.start-button candidate
10
Bumper10
switch.bumper10 candidate
11
Bumper11
switch.bumper11 candidate
12
Left Slingshot
switch.left-slingshot candidate
13
Right Slingshot
switch.right-slingshot candidate
16
Target16
switch.target16 candidate
17
Target17
switch.target17 candidate
20
Leave Left VUK
switch.leave-left-vuk candidate
21
Target21
switch.target21 candidate
26
Target26
switch.target26 candidate
27
Target27
switch.target27 candidate
30
Center VUK
switch.center-vuk candidate
31
Target31
switch.target31 candidate
33
Sol Vari Target Reset
switch.sol-vari-target-reset candidate
36
Target36
switch.target36 candidate
37
Target37
switch.target37 candidate
41
Target41
switch.target41 candidate
43
Sol Vari Target Reset
switch.sol-vari-target-reset-43 candidate
44
Spinner44
switch.spinner44 candidate
46
Trigger46
switch.trigger46 candidate
60
Trigger60
switch.trigger60 candidate
61
Trigger61
switch.trigger61 candidate
62
Trigger62
switch.trigger62 candidate
63
Trigger63
switch.trigger63 candidate
65
Trigger65
switch.trigger65 candidate
66
Underground Hole
switch.underground-hole candidate
67
Trigger67
switch.trigger67 candidate
70
Trigger70
switch.trigger70 candidate

Controlled devices

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

Coils, magnets & motors

21
21 shown
# Name Device ID Evidence
9
Leave Left VUK
coil.leave-left-vuk candidate
10
Leave Center VUK
coil.leave-center-vuk candidate
11
Sol Right VUK
coil.sol-right-vuk candidate
12
Sol Left Ramp Gate
coil.sol-left-ramp-gate candidate
13
Sol Right Ramp Gate
coil.sol-right-ramp-gate candidate
14
Sol Right Lane Flasher
coil.sol-right-lane-flasher candidate
15
Sol Left Lane Flasher
coil.sol-left-lane-flasher candidate
16
Sol Left Ramp Flasher
coil.sol-left-ramp-flasher candidate
17
Sol Top Right Flasher
coil.sol-top-right-flasher candidate
18
Sol Left Mountain Flasher Top
coil.sol-left-mountain-flasher-top candidate
19
Sol Left Mountain Flasher Mid
coil.sol-left-mountain-flasher-mid candidate
20
Sol Left Mountain Flasher Bot
coil.sol-left-mountain-flasher-bot candidate
21
Sol Top Mountain Flasher
coil.sol-top-mountain-flasher candidate
22
Sol Right Mountain Flasher Top
coil.sol-right-mountain-flasher-top candidate
23
Sol Right Mountain Flasher Bot
coil.sol-right-mountain-flasher-bot candidate
24
Sol Vari Target Reset
coil.sol-vari-target-reset candidate
25
Sol Spinning Disk
coil.sol-spinning-disk candidate
26
Sol GIBackbox
coil.sol-gibackbox candidate
32
Sol Game Over
coil.sol-game-over candidate
38
Sol Left Bumper Light
coil.sol-left-bumper-light candidate
39
Sol Right Bumper Light
coil.sol-right-bumper-light 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.opthund 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 opthund, description "Operation Thunder", manufacturer "Gottlieb", catalog year "1992".
  • OPDB record Gr3Lq-MJZo5 (IPDB 1721) names this machine "Operation: Thunder" (Gottlieb, manufacture date 1992-03-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 opthund; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • opthund (1992, Gottlieb).

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 49 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
opthundOperation Thunder 1992——

Parent set: opthund — 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.

opthund.map.json

gottlieb-system3v5format 0.7

maps/gottlieb/system3/opthund.map.json

Applies to ROMs
opthund
Sections
game_statehigh_scoresmode_champions
Map JSONMap sourcePlatform JSONPlatform source

gottlieb-system3 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

  • VPX script

    vpx-script.0a666fc3a93397d3

    vpxtable-scripts: Operation Thunder (Gottlieb 1992) (10.7) 1.4.vbs

    0c036bb61b4b
    by
    Authors credited in Operation Thunder (Gottlieb 1992) (10.7) 1.4.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    0a666fc3a933…

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