Programming Cautions (11) Rumble Pak

Rumble Pak

The following cautions should be observed when programming games that use the Rumble Pak. For additional information on the Rumble Pak (including instructions on how to create a Rumble Pak Tester), please refer to Developer News 1.9: Recurring Problems with N64 Software Submissions.

11-1 Operating Mode (Required)
11-2 Rumble Pak Motor Start/Stop (Required)
11-3 Rumble Pak Errors (Required)
11-4 Rumble Pak Stop (Required)
11-5 Avoiding Rumble Pak Failure (Recommended)

11-1 Operating Mode (Required)

Caution
Ensure that there is no normal operating mode which causes the Rumble Pak to operate continuously.

Discussion
Operation on a continuous basis resulting from the user pushing a button is not desirable for the user's health or the life span of products.

11-2 Rumble Pak Motor Start/Stop (Required)

Caution
During Reset and when the game is paused, stop the Rumble Pak motor. Do not start the Rumble Pak motor until an input is received from the Controller.

Discussion
A rumbling Controller may not be in the hands of the user during Reset or when the game is paused. If the Rumble Pak motor continues to run during these periods, the Controller and/or Rumble Pak may be damaged (such as a Controller rumbling off a table to the floor). Please call osMotorInit() before calling osMotorStop() three times to ensure that the motor will be stopped (please refer to 11-4 Rumble Pak Stop, below).

11-3 Rumble Pak Errors (Required)

Caution
When an error occurs after entering osMotorInit(), do not execute osMotorStart() or osMotorStop().

Discussion
If an error occurs after entering osMotorInit(), something other than the Rumble Pak may be inserted into the Controller.

11-4 Rumble Pak Stop (Required)

Caution
When turning off the Rumble Pak motor, execute osMotorStop() more than three times in a row per video frame.

Discussion
This process will ensure that the Rumble Pak will stop.

11-5 Avoiding Rumble Pak Failure (Recommended)

Caution
Call osMotorInit() at appropriate occasions, such as when changing to a new screen.

Discussion
On occasion, a Rumble Pak may misfunction. Calling osMototInit() at appropriate occasions, such as when changing to a new screen, will ensure that the Rumble Pak will start when osMotorStart() is called.