Zira

Partial
Completion6%

Playmatic1981playmatic.zira.1981 Updated 2026-08-30

playmatic/zira-1981.mdplaymatic/zira-1981.json

Wire it up

what an authoring tool needs first
Bind this ROM
zira

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
11–48 (20)
Solenoids
7–7 (1)

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.

20 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
Hover or tap an address to identify it.
20 shown
# Name Device ID Evidence
11
W11
switch.w11 candidate
12
W12
switch.w12 candidate
13
W13
switch.w13 candidate
14
Spinner14
switch.spinner14 candidate
15
W15
switch.w15 candidate
16
W16
switch.w16 candidate
17
W17
switch.w17 candidate
18
W18
switch.w18 candidate
28
W28
switch.w28 candidate
31
W31
switch.w31 candidate
32
T32a
switch.t32a candidate
34
W34
switch.w34 candidate
39
Upper Sling Shot
switch.upper-sling-shot candidate
41
Right Sling Shot
switch.right-sling-shot candidate
42
W42a
switch.w42a candidate
43
W43a
switch.w43a candidate
45
Bumper1
switch.bumper1 candidate
46
Bumper2
switch.bumper2 candidate
47
W47
switch.w47 candidate
48
W48
switch.w48 candidate

Controlled devices

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

Coils, magnets & motors

1
1 shown
# Name Device ID Evidence
7
Sol7
coil.sol7 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.zira 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 zira, description "Zira", manufacturer "Playmatic", catalog year "1981".
  • 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 zira; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • zira (1981, Playmatic).

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 21 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
ziraZira 1981——

Parent set: zira — 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.0ee30ffcd1238de5

    vpxtable-scripts: Zira_VPX_1_1.vbs

    0c036bb61b4b
    by
    Authors credited in Zira_VPX_1_1.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    0ee30ffcd123…

Something wrong or missing?

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

  • Machine identity

    Verify the physical title, manufacturer, year and edition against attributable sources.

  • 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 · 21