Difference between revisions of "ComplianceDetails/DC"
From Sega Retro
| Line 130: | Line 130: | ||
• Add "In cooperation with"… to the display area of the OEM company name.}}{{ | • Add "In cooperation with"… to the display area of the OEM company name.}}{{ | ||
#vardefine:page|29}} | #vardefine:page|29}} | ||
| − | |||
|6={{ | |6={{ | ||
| Line 343: | Line 342: | ||
|15.2.3={{ | |15.2.3={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|Unless saving data, swapping memory cards will the power is on should be supported. }}{{ |
#vardefine:fulldesc|Except for during actual saves, memory card hot plugs (removing and inserting a memory card with the power ON) should be supported. However, access to Visual Memory is not possible when using the gun controller. For that reason, this rule does not apply, but include it anyway so as not to confuse the user.}}{{ | #vardefine:fulldesc|Except for during actual saves, memory card hot plugs (removing and inserting a memory card with the power ON) should be supported. However, access to Visual Memory is not possible when using the gun controller. For that reason, this rule does not apply, but include it anyway so as not to confuse the user.}}{{ | ||
#vardefine:page|66}} | #vardefine:page|66}} | ||
| Line 425: | Line 424: | ||
|15.8={{ | |15.8={{ | ||
| − | #vardefine:shortdesc|Software must not copy files which have the copy-protection attribute is set (though the software can create such files). }}{{ | + | #vardefine:shortdesc|Software must not copy files which have the copy-protection attribute is set (though the software can create such files).}}{{ |
#vardefine:fulldesc|The application should not copy files in which the copy-protection attribute is set. (However, applications may create such files.)}}{{ | #vardefine:fulldesc|The application should not copy files in which the copy-protection attribute is set. (However, applications may create such files.)}}{{ | ||
#vardefine:page|73}} | #vardefine:page|73}} | ||
| Line 506: | Line 505: | ||
|18.1.1={{ | |18.1.1={{ | ||
#vardefine:shortdesc|DESC HERE PLS}}{{ | #vardefine:shortdesc|DESC HERE PLS}}{{ | ||
| − | #vardefine:fulldesc| | + | #vardefine:fulldesc| |
| − | + | *Sega Dreamcast currently uses four control ports, however, should additional ports become available check the current to make sure that it is safe to use the fifth Jump Pack. (Up to four Jum Packs can be plugged into the front of the console, one in each port, without any need to check the current.) | |
| − | + | *Allow vibration function for each controller, starting with port A, and continuing until the maximum current draw has been reached. | |
| + | *Disable vibration support for any remaining ports.}}{{ | ||
#vardefine:page|88}} | #vardefine:page|88}} | ||
|18.2a={{ | |18.2a={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|The software keyboard should always be supported as an option, even if a hardware keyboard is plugged in.}}{{ |
#vardefine:fulldesc|When the hardware keyboard is supported in an application, the software keyboard (or character input screen) should be displayed as an option and the user should be able to input by the software keyboard when the hardware keyboard is not connected. A software keyboard is enabled when a hardware keyboard is supported by the application.}}{{ | #vardefine:fulldesc|When the hardware keyboard is supported in an application, the software keyboard (or character input screen) should be displayed as an option and the user should be able to input by the software keyboard when the hardware keyboard is not connected. A software keyboard is enabled when a hardware keyboard is supported by the application.}}{{ | ||
#vardefine:page|89}} | #vardefine:page|89}} | ||
| Line 530: | Line 530: | ||
#vardefine:fulldesc|Follow the key input rules below for inputting the following items using operation of the software and hardware keyboards. It is not necessary to allocate all the functions defined below.}}{{ | #vardefine:fulldesc|Follow the key input rules below for inputting the following items using operation of the software and hardware keyboards. It is not necessary to allocate all the functions defined below.}}{{ | ||
#vardefine:page|90}} | #vardefine:page|90}} | ||
| − | |||
|18.3.1={{ | |18.3.1={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|{{A}} and {{C}} should "accept" (perform) and {{B}} should "cancel" (reject) an operation, unless redefined by the user.}}{{ |
#vardefine:fulldesc|Use the A and C buttons as "Accept" buttons (perform operation), and the B button as the "Cancel" button (reject operation). Allocation of "Accept" and "Cancel" to the respective A and B buttons is assumed, but that doesn't not mean the B button must be removed from key configuration when the accept key is defined by pressing the button to allocate keys in key configuration.}}{{ | #vardefine:fulldesc|Use the A and C buttons as "Accept" buttons (perform operation), and the B button as the "Cancel" button (reject operation). Allocation of "Accept" and "Cancel" to the respective A and B buttons is assumed, but that doesn't not mean the B button must be removed from key configuration when the accept key is defined by pressing the button to allocate keys in key configuration.}}{{ | ||
#vardefine:page|95}} | #vardefine:page|95}} | ||
| Line 543: | Line 542: | ||
|18.4a={{ | |18.4a={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|{{A}} should "accept" (perform) and {{B}} should "cancel" (reject) an operation, unless redefined by the user.}}{{ |
#vardefine:fulldesc|Use the A button as the "Accept" button (perform operation) and the B button as the "Cancel" button (reject operation). Allocation of "Accept" and "Cancel" to the respective A and B buttons is assumed, but that doesn't not mean the B button must be removed from key configuration when the accept key is defined by pressing the button to allocate keys in key configuration.}}{{ | #vardefine:fulldesc|Use the A button as the "Accept" button (perform operation) and the B button as the "Cancel" button (reject operation). Allocation of "Accept" and "Cancel" to the respective A and B buttons is assumed, but that doesn't not mean the B button must be removed from key configuration when the accept key is defined by pressing the button to allocate keys in key configuration.}}{{ | ||
#vardefine:page|96}} | #vardefine:page|96}} | ||
| Line 553: | Line 552: | ||
|18.4.2={{ | |18.4.2={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|The [[software reset]] must be implemented with {{A}}+{{B}}+{{X}}+{{Y}}+{{start}}.}}{{ |
#vardefine:fulldesc|When the START button is pressed while the A button + B button + X button + Y button are all held down, "Soft Reset" must be put into effect.}}{{ | #vardefine:fulldesc|When the START button is pressed while the A button + B button + X button + Y button are all held down, "Soft Reset" must be put into effect.}}{{ | ||
#vardefine:page|96}} | #vardefine:page|96}} | ||
|18.5.1={{ | |18.5.1={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|{{A}} (trigger) should "accept" (perform) and {{B}} should "cancel" (reject) an operation, unless redefined by the user.}}{{ |
#vardefine:fulldesc|Use the trigger (A button) as the "Accept" button (perform operation), and the B button as the "Cancel" button (reject operation). Allocation of "Accept" and "Cancel" to the respective A and B buttons is assumed, but that doesn't not mean the B button must be removed from key configuration when the accept key is defined by pressing the button to allocate keys in key configuration.}}{{ | #vardefine:fulldesc|Use the trigger (A button) as the "Accept" button (perform operation), and the B button as the "Cancel" button (reject operation). Allocation of "Accept" and "Cancel" to the respective A and B buttons is assumed, but that doesn't not mean the B button must be removed from key configuration when the accept key is defined by pressing the button to allocate keys in key configuration.}}{{ | ||
#vardefine:page|97}} | #vardefine:page|97}} | ||
| Line 568: | Line 567: | ||
|18.5.3={{ | |18.5.3={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|Software must implement a calibration mode.}}{{ |
#vardefine:fulldesc|Prepare the calibration mode to adjust the aim of the gun controller in the application.}}{{ | #vardefine:fulldesc|Prepare the calibration mode to adjust the aim of the gun controller in the application.}}{{ | ||
#vardefine:page|97}} | #vardefine:page|97}} | ||
| Line 578: | Line 577: | ||
|18.5.5a={{ | |18.5.5a={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|For software sold in the US, display a warning if the gun controller has not been commercially approved for the region.}}{{ |
#vardefine:fulldesc|For games that support a gun controller for use in the U.S., display a warning that contains content such as the following. | #vardefine:fulldesc|For games that support a gun controller for use in the U.S., display a warning that contains content such as the following. | ||
| Line 585: | Line 584: | ||
|18.5.5b={{ | |18.5.5b={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|For software sold in the US, do not allow guns to function which have not been coommercially approved.}}{{ |
#vardefine:fulldesc|Also, when a gun controller with a territory code (see table below) for places other than the United States is connected during application operation, the gun mode should not be able to be used. In the United States, the federal government has declared that there are limitations on the colors of toys that resemble guns. This measure is effected to prevent the importation of real guns alongside the toys from other sales regions by gray importers.}}{{ | #vardefine:fulldesc|Also, when a gun controller with a territory code (see table below) for places other than the United States is connected during application operation, the gun mode should not be able to be used. In the United States, the federal government has declared that there are limitations on the colors of toys that resemble guns. This measure is effected to prevent the importation of real guns alongside the toys from other sales regions by gray importers.}}{{ | ||
#vardefine:page|99}} | #vardefine:page|99}} | ||
|18.6={{ | |18.6={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|{{A}} (trigger) should "accept" (perform) and {{B}} should "cancel" (reject) an operation, unless redefined by the user.}}{{ |
#vardefine:fulldesc|Use Trigger (A button) as the "Accept" button (perform operation) and the B button as the "Cancel" button (reject operation). Allocation of "Accept" and "Cancel" to the respective A and B buttons is assumed, but that doesn't not mean the B button must be removed from key configuration when the accept key is defined by pressing the button to allocate keys in key configuration.}}{{ | #vardefine:fulldesc|Use Trigger (A button) as the "Accept" button (perform operation) and the B button as the "Cancel" button (reject operation). Allocation of "Accept" and "Cancel" to the respective A and B buttons is assumed, but that doesn't not mean the B button must be removed from key configuration when the accept key is defined by pressing the button to allocate keys in key configuration.}}{{ | ||
#vardefine:page|100}} | #vardefine:page|100}} | ||
| Line 621: | Line 620: | ||
|19.3a={{ | |19.3a={{ | ||
#vardefine:shortdesc|DESC HERE PLS}}{{ | #vardefine:shortdesc|DESC HERE PLS}}{{ | ||
| − | #vardefine:fulldesc|When downloading files (that can be saved on the memory card), download and save according to the information of the definition file together with the save file. | + | #vardefine:fulldesc|When downloading files (that can be saved on the memory card), download and save according to the information of the definition file together with the save file. |
| + | |||
| + | Currently, downloadable files on the SEGA Dreamcast Gaming Network (working title) site mention the file name and file size in the definition file if it is the same as the execution file during flagging and saving. Downloading according to definition files (only if there are definition files) makes downloading of regular PC files not possible. When following regularly issued definition files, Visual Memory Single Application files are saved as single application files with the final three spaces in the 12-space file name "_vm".}}{{ | ||
#vardefine:page|102}} | #vardefine:page|102}} | ||
| Line 640: | Line 641: | ||
|20.2={{ | |20.2={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|Program data must be written to and executed from the high-density area of a GD-ROM, not the single-density "CD-ROM" area or a memory card.}}{{ |
#vardefine:fulldesc|For security reasons, the Sega Dreamcast program execution code cannot be written to any area other than the Sega Dreamcast-specific disc high-density area. Sega Dreamcast program execution code should not be written to Sega Dreamcast-specific disc single-density area, save data, or Visual Memory special games.}}{{ | #vardefine:fulldesc|For security reasons, the Sega Dreamcast program execution code cannot be written to any area other than the Sega Dreamcast-specific disc high-density area. Sega Dreamcast program execution code should not be written to Sega Dreamcast-specific disc single-density area, save data, or Visual Memory special games.}}{{ | ||
#vardefine:page|106}} | #vardefine:page|106}} | ||
|24={{ | |24={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|If third-party middleware is used, logos and trade names should be displayed at the specified location.}}{{ |
#vardefine:fulldesc|When using a software library provided by another company, and when using a patent that is owned by another company, depending on the terms of the licensing contract, that company's logo and trade name must be displayed at the specified location.}}{{ | #vardefine:fulldesc|When using a software library provided by another company, and when using a patent that is owned by another company, depending on the terms of the licensing contract, that company's logo and trade name must be displayed at the specified location.}}{{ | ||
#vardefine:page|115}} | #vardefine:page|115}} | ||
| − | |||
|25.1={{ | |25.1={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|{{A}} should "accept" (perform) and {{B}} should "cancel" (reject) an operation.}}{{ |
#vardefine:fulldesc|Use the A button for "Accept" (perform operation) and the B button for "Cancel" (reject operation).}}{{ | #vardefine:fulldesc|Use the A button for "Accept" (perform operation) and the B button for "Cancel" (reject operation).}}{{ | ||
#vardefine:page|121}} | #vardefine:page|121}} | ||
| Line 661: | Line 661: | ||
|25.2b={{ | |25.2b={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|Copyright details must be displayed on the title screen.}}{{ |
#vardefine:fulldesc|Display the copyright on the title screen.}}{{ | #vardefine:fulldesc|Display the copyright on the title screen.}}{{ | ||
#vardefine:page|122}} | #vardefine:page|122}} | ||
|25.3a={{ | |25.3a={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|Pressing {{A}}+{{B}} on the title loop should start the game.}}{{ |
#vardefine:fulldesc|Pressing the A and B buttons together from the Title Display/Loop (27.2) starts the main game | #vardefine:fulldesc|Pressing the A and B buttons together from the Title Display/Loop (27.2) starts the main game | ||
(game start).}}{{ | (game start).}}{{ | ||
| Line 672: | Line 672: | ||
|25.3b={{ | |25.3b={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|"Press {{A}}+{{B}}" should be displayed on the title screen.}}{{ |
#vardefine:fulldesc|"Press A+B" should be displayed on the Title Screen.}}{{ | #vardefine:fulldesc|"Press A+B" should be displayed on the Title Screen.}}{{ | ||
#vardefine:page|122}} | #vardefine:page|122}} | ||
| Line 682: | Line 682: | ||
|25.5={{ | |25.5={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|When a low-voltage interrupt occurs, software should finish writing any data, display a message suggesting the batteries be replaced, and disable further input.}}{{ |
#vardefine:fulldesc|When a low-voltage interrupt occurs, the application should finish storing any data and other processes, and then immediately display a caution message such as "Please replace the batteries," and disable any further input from the mode buttons or other keys.}}{{ | #vardefine:fulldesc|When a low-voltage interrupt occurs, the application should finish storing any data and other processes, and then immediately display a caution message such as "Please replace the batteries," and disable any further input from the mode buttons or other keys.}}{{ | ||
#vardefine:page|123}} | #vardefine:page|123}} | ||
Revision as of 05:57, 26 August 2024
| : [1] |
| Compilance | Screenshot(s) | Pass/fail | Comments |
|---|---|---|---|
| Pass | dsfahukjsadgihkdgsali afsdifads iljfd sijlafds aijl |