Technical information

Sega Saturn Software Development Standards, SOA version 2.0 3
2. Peripheral Check
Required A check for peripherals (typically a Control Pad) connected to the
Compliance Item Sega Saturn must be performed by the application before the game is
started.
For more detailed information on Sega Saturn input peripheral support
guidelines, please consult Section 8.2.4: Sega Saturn Input Peripheral
Software Development Standards.
2.1 When Must the Checks Occur?
Peripheral checks should be active during the Title Loop
sequence in addition to the start of the game (see Figure 1.1
above).
Required Peripheral check routines must be incorporated throughout
Compliance Item the game to accommodate possible errors that may occur
from (un)intentional peripheral device disconnection.
2.2 What Must be Checked?
Required The absence of a peripheral or a peripheral connected only
Compliance Item at Control Port 2 is equivalent to null controller input state
(i.e., no controller input is sensed. The game cannot be started in
this state).
If an active peripheral is disconnected during the course of an action
or time-oriented game, detect the disconnect as a “null input” state,
followed by a system pause or a warning display. In either case, the
game must not continue while the peripheral is disconnected. The
affected port becomes an unused active port.
Required If the peripheral is reconnected, the user must be able to
Compliance Item resume a normal game session. After the game is placed in
pause mode prior to the disconnection of the peripheral, the
game must resume by pressing the “START” button after
reconnection of the peripheral.
2.3 Mandatory Peripheral Compatibility
Required Compatible peripherals must support transparent recovery
Compliance Item from input peripheral disconnect/reconnect activity during
the game session (prior to or after game start).
Required Support for incompatible peripherals within the game
Compliance Item application is defined as software measures to prevent