Return to previous page | Return to menu | Go to next page

1. Basic items (common items for all input peripherals)

1) Supported input peripheral setting principles

For input peripherals (corresponding P) that can be used in applications, the following principles in accordance with 〈Pad Setting Principles〉 of “Software Creation Criteria” must be observed.

2) Check input peripherals

As a general rule, check as often as possible while the power is on, and at the very least deal with it so as not to run out of control .
Refer to the following recommended specifications for what kind of check is performed at which timing.

《Recommended Specifications》

◆ Check for compatible P (valid terminal registration)

• Check whether the connected peripheral is compatible P or not. A terminal connected to the corresponding P is an effective terminal .
• Unsupported P is regarded as not connected , or a warning is displayed and the user is requested to replace it.
• Checks are performed as frequently as possible in [Title Loop] as well as [Pad Check] timing after power ON.

  * Especially for applications that do not support a mouse, be careful not to cause unstable operation when a mouse is connected.

  * In multiplayer games with different start timings for each player (possible participation during the course), check frequently at every timing, including in the main game.

◆ Start application

• In principle, play is started by 1P (corresponding to P of main unit terminal 1) .
• In principle, the mode selection and option settings during the game are also performed by 1P <.

  * In multiplayer games where participation is possible, it may be possible to start from other than 1P.

  * In a multiplayer game, each player may be allowed to play the content individually set.

◆ Determining the terminal used

• At the start, determine the terminal to be used in the game from the valid terminals .

  * Terminals that exceed the maximum number of players are not selected.

◆ Check for insertion / removal

• When removing / inserting (and adding) input peripherals in [Main Game], it must be dealt with so that no problems occur regardless of the user's intentional error > .

(i) When removed

• If the used P is removed during play, it is determined that there is no input . (Or perform “System Pause” and display a warning at the same time)
  → The terminal will be “Available terminal”.
• Ignore if unused P or unsupported P is removed . (Does not obscure the game progress)

• When the multi terminal is disconnected while using the multi terminal.
• If no action is taken, the gameplay will go in a very unfavorable direction for the user.

  * “System Pause” can be released from any use P when the removed use P is returned (when the application determines that it is ready to be used again).

  * If the system pose shifts to “system pose” during user pose, the user pose will be automatically canceled when “system pose” is canceled. (For example, when a peripheral is pulled out during user pause)

(ii) When connected

• Resuming input only when P corresponding to “Available terminal” is returned . (If paused, wait for release)
• Other than that, don't affect the game .

  * Even when a use P other than the extracted use P is returned, if it is a corresponding P, input is resumed.

(iii) When added

In applications where
• [participation] is performed, the corresponding P may be additionally added to the invalid terminal. In this case, even if it is in progress of the [main game], it may be used as an effective terminal and further as a use terminal.
• In this case, Be careful not to affect the game with the connection behavior .

  * Re-determine the terminal to be used at the following timing.

  1. At the start of the next game.
  2. Perform immediately after connection. However, in this case, it is necessary to take necessary measures such as requiring the start button to be input before the game starts for the participating user.

  * Terminals that exceed the maximum number of players are not selected.

The terminal state transitions based on the checks so far are shown below.

Figure Separate volume 2-1: Transition diagram of terminal states

3) Correspondence of optional items

When an application is associated with each input peripheral, it must be able to be operated with CONTROL PAD, except in special cases. Therefore, at a minimum, the optional control setting (CONTROL) must correspond to both input peripherals (CONTROL PAD and each corresponding input peripheral). Follow the following rules to make the options correspond to each input peripheral.

• Increase items that seem to be necessary for each input peripheral
  → "Cursor speed" with the mouse (cursor movement speed), etc.
• Automatically detects input peripherals that are connected and displays the corresponding screen (item)
  → Check the pad (connection status) when you enter the option screen
  (Furthermore, it is desirable to do it frequently in the option screen)
• Remember all settings for each peripheral

4) In-game terminology

If it is necessary to display the name of each input peripheral in the game, in principle, it should be unified with the name used in this creation standard.

Multi terminal
Racing controller
Shuttle mouse (mouse) etc.

(1. Basic items, finished)

Return to previous page | Return to menu | Go to next page