Shark (Taito)

Partial

Taito1982taito.shark-taito.1982

Wire it up

what an authoring tool needs first
Bind this ROM
sharkt

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
3–75 (23)
Solenoids
2–17 (4)

Coverage

Partial

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

Completion6%

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 · 15
IdentityDriver 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

Column × row matrix — the address is column·row.

used unused
 
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
Hover or tap an address to identify it.

Outside the matrix3, 4 — dedicated, diagnostic or flipper-column addresses. See the table below.

23 shown
# Name Device ID Evidence
3
Sw3
switch.sw3 candidate
4
Sw4
switch.sw4 candidate
12
Sw12
switch.sw12 candidate
13
Spinner1
switch.spinner1 candidate
14
Sw14
switch.sw14 candidate
22
Sw22
switch.sw22 candidate
23
Left Sling Shot
switch.left-sling-shot candidate
24
Sw24
switch.sw24 candidate
32
Sw32
switch.sw32 candidate
33
Right Sling Shot
switch.right-sling-shot candidate
34
Sw34
switch.sw34 candidate
35
Sw35
switch.sw35 candidate
42
Sw42
switch.sw42 candidate
43
Sw43
switch.sw43 candidate
44
Sw44
switch.sw44 candidate
53
Sw53
switch.sw53 candidate
54
Sw54
switch.sw54 candidate
63
Sw63
switch.sw63 candidate
64
Sw64
switch.sw64 candidate
65
Sw65
switch.sw65 candidate
73
Bumper1
switch.bumper1 candidate
74
Sw74
switch.sw74 candidate
75
Left Sling Shot1
switch.left-sling-shot1 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
2
Sol Saucer
coil.sol-saucer candidate
3
Sol Lock Release
coil.sol-lock-release candidate
9
Gi Effect
coil.gi-effect candidate
17
Sol Gi
coil.sol-gi 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.sharkt 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 sharkt, description "Shark (Taito)", manufacturer "Taito", catalog year "1982".
  • No OPDB record is mapped for this driver in machines/opdb_id.csv, so the name above comes from the PinMAME catalog alone and is unverified.
  • The definition's driver list is exactly the clone tree PinMAME declares under sharkt; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • sharkt (1982, Taito).

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 27 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
sharktShark (Taito) 1982

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

    by
    PinMAME contributors
    rev
    8371478a7640
  • VPX script

    vpx-script.6956bc689f1d80b2

    vpxtable-scripts: Shark (Taito do Brasil - 1982) v601.vbs

    by
    Authors credited in Shark (Taito do Brasil - 1982) v601.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    6956bc689f1d…

Something wrong or missing?

This definition still has 15 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.