Super Orbit

Partial
Completion13%

Gottlieb1983gottlieb.super-orbit.1983 Updated 2026-08-30

OPDB IPDB gottlieb/super-orbit-1983.mdgottlieb/super-orbit-1983.json

Wire it up

what an authoring tool needs first
Bind this ROM
sorbit

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
1–67 (14)
Solenoids
8–10 (3)

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.

14 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.
14 shown
# Name Device ID Evidence
1
Sw01t
switch.sw01t candidate
2
Bumper1
switch.bumper1 candidate
11
Sw11t
switch.sw11t candidate
12
Bumper2
switch.bumper2 candidate
21
Gate3
switch.gate3 candidate
22
Bumper3
switch.bumper3 candidate
31
Spinner
switch.spinner candidate
32
Right Sling Shot
switch.right-sling-shot candidate
41
Sw41
switch.sw41 candidate
51
Sw51
switch.sw51 candidate
52
Sw52
switch.sw52 candidate
61
Sw61
switch.sw61 candidate
62
Sensor62
switch.sensor62 candidate
67
Slot1
switch.slot1 candidate

Controlled devices

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

Coils, magnets & motors

3
3 shown
# Name Device ID Evidence
8
Sol Knocker
coil.sol-knocker candidate
9
Sol Trough
coil.sol-trough candidate
10
Game Over
coil.game-over 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.sorbit 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 sorbit, description "Super Orbit", manufacturer "Gottlieb", catalog year "1983".
  • OPDB record G4EPE-ML14r (IPDB 2437) names this machine "Super Orbit" (Gottlieb, manufacture date 1983-05-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 sorbit; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • sorbit (1983, Gottlieb, clone of gts80a).

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 17 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
sorbitSuper Orbit 1983gts80a—

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.a6327351f42cbd9b

    vpxtable-scripts: special_audiopan_and_audiofade_patched/Super Orbit (Gottlieb 1983) v2.0.1.vbs

    0c036bb61b4b
    by
    Authors credited in special_audiopan_and_audiofade_patched/Super Orbit (Gottlieb 1983) v2.0.1.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    a6327351f42c…

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 · 17