Difference between revisions of "ComplianceDetails/DC"
From Sega Retro
m |
|||
| (12 intermediate revisions by 2 users not shown) | |||
| Line 17: | Line 17: | ||
|2.2.1={{ | |2.2.1={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|In single-player games, it must be possible to start and operate software from any of the four controller ports (A-through-D).}}{{ |
#vardefine:fulldesc|In games that can be played by only one person, as well as in multi-player games, it must be possible to start and operate the game from any of the four front-panel ports (A through D) to which a compatible controller is connected. | #vardefine:fulldesc|In games that can be played by only one person, as well as in multi-player games, it must be possible to start and operate the game from any of the four front-panel ports (A through D) to which a compatible controller is connected. | ||
}}{{ | }}{{ | ||
| Line 23: | Line 23: | ||
|2.2.2={{ | |2.2.2={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|In multi-player games, the number of ports from which games can be started and operated must not exceed the number of supported players. For example, if three controllers are connected in a two-player game, the third controller should not work.}}{{ |
| − | #vardefine:fulldesc|Unless an expansion socket is used (as described in Chapter 12, "Pause,") the number of ports from which games can be started or operated must not exceed the number of users playing a game. (When an expansion socket is used, it doesn't matter if the ports being used exceed the number of players. Even if you use a memory card to save a game that is being played by only one or two people, it won't cause any problems if an unused expansion socket happens to be plugged in.) | + | #vardefine:fulldesc|Unless an expansion socket is used (as described in Chapter 12, "Pause,") the number of ports from which games can be started or operated must not exceed the number of users playing a game. (When an expansion socket is used, it doesn't matter if the ports being used exceed the number of players. Even if you use a memory card to save a game that is being played by only one or two people, it won't cause any problems if an unused expansion socket happens to be plugged in. |
| + | |||
| + | Example 1 | ||
| + | In a fighting game (a type of game normally designed for either one or two players), it should be possible | ||
| + | to connect standard controllers to ports A and B. Starting or playing from port D should not be possible. | ||
| + | |||
| + | Example 2 | ||
| + | In a four-player fighting game, it should be possible to connect standard controllers to all four ports on | ||
| + | the front of the Sega Dreamcast console. Consequently, it should be possible to start and play from all | ||
| + | ports with compatible controllers connected.) | ||
}}{{ | }}{{ | ||
#vardefine:page|9}} | #vardefine:page|9}} | ||
|2.2.3={{ | |2.2.3={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|If a controller is connected after the system turns on, software should recognise it.}}{{ |
#vardefine:fulldesc|Even though a compatible controller is not connected to a port when power is turned on, if it is connected before a game begins, it must be properly recognized and enabled for start and operation. So your application must test the ports frequently in the Title Loop before starting a game. | #vardefine:fulldesc|Even though a compatible controller is not connected to a port when power is turned on, if it is connected before a game begins, it must be properly recognized and enabled for start and operation. So your application must test the ports frequently in the Title Loop before starting a game. | ||
}}{{ | }}{{ | ||
| Line 35: | Line 44: | ||
|2.2.6={{ | |2.2.6={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|For games where only one controller type is used and the user swaps controller ports mid-game, play should not be resumed.}}{{ |
#vardefine:fulldesc|In an application in which single player uses a single controller, play is not resumed. | #vardefine:fulldesc|In an application in which single player uses a single controller, play is not resumed. | ||
}}{{ | }}{{ | ||
| Line 41: | Line 50: | ||
|3.2={{ | |3.2={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|Upon booting software, the stereo/monaural output setting should be changed to match the [[Sega Dreamcast/Boot ROM|boot ROM]].}}{{ |
#vardefine:fulldesc|Immediately upon loading an application (before the Title Loop starts), the stereo/monaural output setting should be changed to match the Boot ROM settings of the Main Unit. Even if sound output is not listed in Chapter 9, Options, an application internally determines if it is stereo or monaural, so the settings must be changed to correspond to the Main Unit Boot ROM settings on the application side. Currently, the stereo/monaural output settings are saved on the Main Unit, and should not be saved under any circumstances to the memory card. Refer to Chapter 9.2, Storing Option Settings, for more details. | #vardefine:fulldesc|Immediately upon loading an application (before the Title Loop starts), the stereo/monaural output setting should be changed to match the Boot ROM settings of the Main Unit. Even if sound output is not listed in Chapter 9, Options, an application internally determines if it is stereo or monaural, so the settings must be changed to correspond to the Main Unit Boot ROM settings on the application side. Currently, the stereo/monaural output settings are saved on the Main Unit, and should not be saved under any circumstances to the memory card. Refer to Chapter 9.2, Storing Option Settings, for more details. | ||
}}{{ | }}{{ | ||
#vardefine:page|15}} | #vardefine:page|15}} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|4.1.2a={{ | |4.1.2a={{ | ||
| Line 58: | Line 61: | ||
|4.1.2b={{ | |4.1.2b={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|If the current controller means the pressing of {{A}}+{{B}}+{{X}}+{{Y}}+{{start}} for a software reset is difficult or impossible, implement an option in software for performing a software reset (e.g. a menu item).}}{{ |
#vardefine:fulldesc|For controllers such as racing controllers, gun controllers and the keyboard (for which the soft reset operation of pressing the A + B + X + Y buttons and the START button simultaneously is difficult or impossible), applications must make soft resets possible using the method outlined in Chapter 18, Development Standards for Peripherals, or through either a software keyboard or another procedure displayed in a separate menu. When soft reset is supported using a procedure described in a separate menu, your application is not required to display that menu at all times if that would adversely affect your game. Nonetheless, the soft reset option should be clearly displayed on a suitable menu and made selectable for the user. | #vardefine:fulldesc|For controllers such as racing controllers, gun controllers and the keyboard (for which the soft reset operation of pressing the A + B + X + Y buttons and the START button simultaneously is difficult or impossible), applications must make soft resets possible using the method outlined in Chapter 18, Development Standards for Peripherals, or through either a software keyboard or another procedure displayed in a separate menu. When soft reset is supported using a procedure described in a separate menu, your application is not required to display that menu at all times if that would adversely affect your game. Nonetheless, the soft reset option should be clearly displayed on a suitable menu and made selectable for the user. | ||
}}{{ | }}{{ | ||
| Line 70: | Line 73: | ||
|4.1.4.1a={{ | |4.1.4.1a={{ | ||
| − | #vardefine:shortdesc|Performing a [[software reset]] from the title loop must return to the | + | #vardefine:shortdesc|Performing a [[software reset]] from the title loop must return to the [[Sega Dreamcast/Boot ROM|boot ROM]].}}{{ |
#vardefine:fulldesc|Soft reset from the Title Loop must jump to the Main Unit Boot ROM Menu.}}{{ | #vardefine:fulldesc|Soft reset from the Title Loop must jump to the Main Unit Boot ROM Menu.}}{{ | ||
#vardefine:page|19}} | #vardefine:page|19}} | ||
| Line 80: | Line 83: | ||
|4.2.1={{ | |4.2.1={{ | ||
| − | #vardefine:shortdesc|The | + | #vardefine:shortdesc|The [[Sega Dreamcast/Boot ROM|boot ROM]] must appear within ten seconds of opening the disc lid, save for situations where legitimate disc swapping is required.}}{{ |
#vardefine:fulldesc|The Main Unit Boot ROM menu must appear when the Main Unit "OPEN button" is pressed and the disc lid is opened. Please note the alternative cases described in 4.2.2, Exceptions when the Disc Lid is Open, 4.2.3, When the Disc Lid is Opened during Saves, and 4.2.4, When File Loading Fails from the Disc,. When the disc lid is opened, your application must go to the Main Unit Boot ROM menu within ten seconds.}}{{ | #vardefine:fulldesc|The Main Unit Boot ROM menu must appear when the Main Unit "OPEN button" is pressed and the disc lid is opened. Please note the alternative cases described in 4.2.2, Exceptions when the Disc Lid is Open, 4.2.3, When the Disc Lid is Opened during Saves, and 4.2.4, When File Loading Fails from the Disc,. When the disc lid is opened, your application must go to the Main Unit Boot ROM menu within ten seconds.}}{{ | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
#vardefine:page|20}} | #vardefine:page|20}} | ||
|4.2.3={{ | |4.2.3={{ | ||
| − | #vardefine:shortdesc|Any operation that returns to the | + | #vardefine:shortdesc|Any operation that returns to the [[Sega Dreamcast/Boot ROM|boot ROM]] must wait until a save has finished.}}{{ |
#vardefine:fulldesc|When executing saves, do not go to the Main Unit Boot ROM main screen until that save is finished. (This requirement is imposed to avoid the loss of the file being saved). Go to the main screen as soon as the save is finished.}}{{ | #vardefine:fulldesc|When executing saves, do not go to the Main Unit Boot ROM main screen until that save is finished. (This requirement is imposed to avoid the loss of the file being saved). Go to the main screen as soon as the save is finished.}}{{ | ||
#vardefine:page|21}} | #vardefine:page|21}} | ||
| Line 105: | Line 103: | ||
|5.2.7={{ | |5.2.7={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|License and middleware logos should observe the standards outlined in the contract document in Chapter 24}}{{ |
#vardefine:fulldesc|To display the license logo and library logo, observe the following standards: | #vardefine:fulldesc|To display the license logo and library logo, observe the following standards: | ||
1. Follow the rules outlined in the contract document regarding the content of logo display. | 1. Follow the rules outlined in the contract document regarding the content of logo display. | ||
| Line 114: | Line 112: | ||
|5.2.8={{ | |5.2.8={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|The use of team or series logos must be approved by license holders and Sega's legal department. Do not use the words "Presents", "Presented by" or "Produced by" to avoid complications of rights ownership.}}{{ |
#vardefine:fulldesc|To display a team logo and series logo, observe the following standards: | #vardefine:fulldesc|To display a team logo and series logo, observe the following standards: | ||
1. When creating a team logo or series logo, obtain approval for its use and register the trademark. | 1. When creating a team logo or series logo, obtain approval for its use and register the trademark. | ||
| Line 123: | Line 121: | ||
|5.2.9={{ | |5.2.9={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|OEM logos must be approved by Sega's legal department. "In cooperation with" must be added to the OEM company name.}}{{ |
#vardefine:fulldesc|When displaying OEM logos other than manufacture and sales permit licensers, these are the standards to follow: | #vardefine:fulldesc|When displaying OEM logos other than manufacture and sales permit licensers, these are the standards to follow: | ||
1. When you want to display an OEM logo, the logo display content is regulated in the development contract document. | 1. When you want to display an OEM logo, the logo display content is regulated in the development contract document. | ||
| Line 130: | Line 128: | ||
• 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={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|A title screen must display a title logo and the text "PRESS START BUTTON" (or for non-English software, a term that signifies that pressing {{start}} will start a game. Copyright information must also be displayed unless specified otherwise by the contract document, or there is not enough space.}}{{ |
#vardefine:fulldesc|The Title Screen displays the Title Logo, "PRESS START BUTTON" and a copyright, unless specified otherwise by contract document or difficulty (such as a movie title) to display the copyright because of lack of space. If "PRESS START BUTTON" is displayed in any language other than English, express the idea that pressing the start button will start the game as simply as possible.}}{{ | #vardefine:fulldesc|The Title Screen displays the Title Logo, "PRESS START BUTTON" and a copyright, unless specified otherwise by contract document or difficulty (such as a movie title) to display the copyright because of lack of space. If "PRESS START BUTTON" is displayed in any language other than English, express the idea that pressing the start button will start the game as simply as possible.}}{{ | ||
#vardefine:page|32}} | #vardefine:page|32}} | ||
| Line 158: | Line 155: | ||
|8.1={{ | |8.1={{ | ||
| − | #vardefine:shortdesc|Any menus must exist separately | + | #vardefine:shortdesc|Any menus must exist separately from the title screen.}}{{ |
#vardefine:fulldesc|The Start/Option Selection screen exists separately from the Title Screen. If a "Menu" selection such as Start/Option is needed, it should appear when the START button is pressed at the Title Screen. Objects other than the Menu can be used and combined as needed. | #vardefine:fulldesc|The Start/Option Selection screen exists separately from the Title Screen. If a "Menu" selection such as Start/Option is needed, it should appear when the START button is pressed at the Title Screen. Objects other than the Menu can be used and combined as needed. | ||
}}{{ | }}{{ | ||
| Line 164: | Line 161: | ||
|8.2={{ | |8.2={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|Menu items should always be shown, even if the controller state means they cannot be used. When items cannot be used, (e.g. versus mode, when only one controller is connected) they should be greyed out.}}{{ |
#vardefine:fulldesc|According to the controller connection state, items that are unusable should be displayed in the menu, but not be selectable. If a second controller is not present, "vs" mode should be grayed out. If the phone line is not plugged in, the network selection should be grayed out.}}{{ | #vardefine:fulldesc|According to the controller connection state, items that are unusable should be displayed in the menu, but not be selectable. If a second controller is not present, "vs" mode should be grayed out. If the phone line is not plugged in, the network selection should be grayed out.}}{{ | ||
#vardefine:page|35}} | #vardefine:page|35}} | ||
| Line 174: | Line 171: | ||
|9.2={{ | |9.2={{ | ||
| − | #vardefine:shortdesc|The stereo/monaural setting must not be saved. The default setting is saved in the | + | #vardefine:shortdesc|The stereo/monaural setting must not be saved. The default setting is saved in the [[Sega Dreamcast/Boot ROM|boot ROM]].}}{{ |
#vardefine:fulldesc|If the option settings are to be backed up according to the above, the Stereo/Monaural setting should not be saved. On the Sega Dreamcast, the Stereo/Monaural settings are saved in the Main Unit, considering the case where the same data is to be used to play in another environment.}}{{ | #vardefine:fulldesc|If the option settings are to be backed up according to the above, the Stereo/Monaural setting should not be saved. On the Sega Dreamcast, the Stereo/Monaural settings are saved in the Main Unit, considering the case where the same data is to be used to play in another environment.}}{{ | ||
#vardefine:page|39}} | #vardefine:page|39}} | ||
|9.3={{ | |9.3={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|If the stereo/monaural setting is changed in-game, the [[Sega Dreamcast/Boot ROM|boot ROM]] setting must be changed too.}}{{ |
#vardefine:fulldesc|When the user changes the value of the voice output setting on the application option screen, the Main Unit Boot ROM setting should also be set to the same value before the option screen is exited. Wait until the user confirms. As used in the procedures of 3.1, 9.2 and 9.3, the Stereo/Monaural setting refers to Main Console setting, and other option settings refer to the saved data (if present).}}{{ | #vardefine:fulldesc|When the user changes the value of the voice output setting on the application option screen, the Main Unit Boot ROM setting should also be set to the same value before the option screen is exited. Wait until the user confirms. As used in the procedures of 3.1, 9.2 and 9.3, the Stereo/Monaural setting refers to Main Console setting, and other option settings refer to the saved data (if present).}}{{ | ||
#vardefine:page|39}} | #vardefine:page|39}} | ||
| Line 188: | Line 185: | ||
*8 pixels horizontally or 16 pixels vertically from the game screen (for 320x240 pixel displays). | *8 pixels horizontally or 16 pixels vertically from the game screen (for 320x240 pixel displays). | ||
*8 pixels horizontally or 32 pixels vertically from the game screen (for 640x480 pixel displays).}}{{ | *8 pixels horizontally or 32 pixels vertically from the game screen (for 640x480 pixel displays).}}{{ | ||
| − | + | #vardefine:page|41}} | |
|10.4={{ | |10.4={{ | ||
| Line 196: | Line 193: | ||
|10.5={{ | |10.5={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|Colours with more than 75% brightness (0xC0) should not be allowed to persist for more than 300 seconds or cover more than two thirds of the screen.}}{{ |
| − | #vardefine:fulldesc|Screen display of more than 0XC0 (75% brightness) should not be allowed to persist for a long time | + | #vardefine:fulldesc|Screen display of more than 0XC0 (75% brightness) should not be allowed to persist for a long time (more than 300 seconds), or cover more than 2/3 of the screen. Sega Dreamcast image output is set to 800mV, to display bright white briefly, so if 0XC0 (not only white, but also yellow or other colors) is displayed for a long time on an NTSC/PAL TV, the screen phosphor could be burned. However, there is no problem displaying 0XFF (100% bright white) briefly and in small screen regions. We suggest using values below 0XC0 for large screen regions in applications where screen simulations are likely to be frozen. Currently, even the Boot ROM has the background white display corresponding to 0XC0. The standard brightness of the white color used for the screen flash when using the gun controller is 0x90; for a VGA monitor, it is 0xC0. |
| − | (more than 300 seconds), or cover more than 2/3 of the screen. Sega Dreamcast image output is set to 800mV, to display bright white briefly, so if 0XC0 (not only white, but also yellow or other colors) is displayed for a long time on an NTSC/PAL TV, the screen phosphor could be burned. However, there is no problem displaying 0XFF (100% bright white) briefly and in small screen regions. We suggest using values below 0XC0 for large screen regions in applications where screen simulations are likely to be frozen. Currently, even the Boot ROM has the background white display corresponding to 0XC0. The standard brightness of the white color used for the screen flash when using the gun controller is 0x90; for a VGA monitor, it is 0xC0. | ||
The brightness of the white color used for the screen flash is closely related to gun performance and may be hard on your eyes. You may want to lower the brightness of the flash to make it easier on your eyes, but so doing shortens the detection range of the peripheral device. The degree of brightness depends on the type and manufacturer of the monitor on which you view it, but in general, VGA monitors have a lower degree of brightness than a TV monitor. Taking the above conditions into consideration, the brightness of the flash is 0x90 for a TV screen, and 0xC0 for a VGA monitor.}}{{ | The brightness of the white color used for the screen flash is closely related to gun performance and may be hard on your eyes. You may want to lower the brightness of the flash to make it easier on your eyes, but so doing shortens the detection range of the peripheral device. The degree of brightness depends on the type and manufacturer of the monitor on which you view it, but in general, VGA monitors have a lower degree of brightness than a TV monitor. Taking the above conditions into consideration, the brightness of the flash is 0x90 for a TV screen, and 0xC0 for a VGA monitor.}}{{ | ||
#vardefine:page|43}} | #vardefine:page|43}} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|12={{ | |12={{ | ||
| Line 253: | Line 244: | ||
|15={{ | |15={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|If a [[VMU]] is detected, software must make use of it to save data.}}{{ |
#vardefine:fulldesc|If a VMU device is present, the application must make use of the card to save game data. The minimum save-game support should be for game preferences and high scores.}}{{ | #vardefine:fulldesc|If a VMU device is present, the application must make use of the card to save game data. The minimum save-game support should be for game preferences and high scores.}}{{ | ||
#vardefine:page|55}} | #vardefine:page|55}} | ||
|15.1={{ | |15.1={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|Save files must always be registered. The file name must be easily recognisable and resemble the name of software.}}{{ |
| − | #vardefine:fulldesc|The save file for a Dreamcast application must always be registered. (Please make sure the "Back up" section of the Master ROM Release form has been completely filled out.) Create a file name that is easily recognizable and bears an intuitive resemblance to the name of the game.}}{{ | + | #vardefine:fulldesc|The save file for a Dreamcast application must always be registered. (Please make sure the "Back up" section of the Master ROM Release form has been completely filled out.) |
| + | |||
| + | Create a file name that is easily recognizable and bears an intuitive resemblance to the name of the game.}}{{ | ||
#vardefine:page|55}} | #vardefine:page|55}} | ||
| Line 273: | Line 266: | ||
|15.1.1c={{ | |15.1.1c={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|If multiple files are saved by one piece of software, the first 9 characters must be the same (only the last 3 may differ). This is to ensure the batch copy function works in the [[Sega Dreamcast/Boot ROM|boot ROM]].}}{{ |
#vardefine:fulldesc|When multiple files are saved by one game, the first 9 characters of each file name must be the same (only the last 3 may differ). In the Boot ROM file menu, the first 9 characters determine files associated with each game. Consequently, if these characters are not the same, the files are not recognized as belonging to the same game, and the batch copy function will not work.}}{{ | #vardefine:fulldesc|When multiple files are saved by one game, the first 9 characters of each file name must be the same (only the last 3 may differ). In the Boot ROM file menu, the first 9 characters determine files associated with each game. Consequently, if these characters are not the same, the files are not recognized as belonging to the same game, and the batch copy function will not work.}}{{ | ||
#vardefine:page|56}} | #vardefine:page|56}} | ||
|15.1.2={{ | |15.1.2={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|VMU comments should consist of up to 16 single-byte ASCII characters (20 to 7D and A0 to DF). Character 7E (~) should not be used as it does not represent a character in the VMU.}}{{ |
#vardefine:fulldesc|VMU Comments shall consist of up to 16 single-byte ASCII characters (20 to 7D and A0 to DF). Character 7E (tilde) should not be used as it does not represent a character in VMU.}}{{ | #vardefine:fulldesc|VMU Comments shall consist of up to 16 single-byte ASCII characters (20 to 7D and A0 to DF). Character 7E (tilde) should not be used as it does not represent a character in VMU.}}{{ | ||
#vardefine:page|57}} | #vardefine:page|57}} | ||
|15.1.3a={{ | |15.1.3a={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|[[Sega Dreamcast/Boot ROM|Boot ROM]] comments may consist of up to 32 single-byte or 16 double-byte upper-case English characters.}}{{ |
#vardefine:fulldesc|Boot ROM comments may consist of up to 32 single-byte or 16 double-byte upper-case English characters (double-byte characters display as 24x24 dots with the Boot ROM, and single-byte characters as 24x12 dots).}}{{ | #vardefine:fulldesc|Boot ROM comments may consist of up to 32 single-byte or 16 double-byte upper-case English characters (double-byte characters display as 24x24 dots with the Boot ROM, and single-byte characters as 24x12 dots).}}{{ | ||
| − | + | #vardefine:page|58}} | |
|15.1.3b={{ | |15.1.3b={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|The game title (shortened if necessary) should be written as a [[Sega Dreamcast/Boot ROM|boot ROM]] comment (name + status is also allowed).}}{{ |
#vardefine:fulldesc|The game title (or a shortened form of the title, if necessary) is written as a Boot ROM Comment. Display of "Game name + game status" is also possible.}}{{ | #vardefine:fulldesc|The game title (or a shortened form of the title, if necessary) is written as a Boot ROM Comment. Display of "Game name + game status" is also possible.}}{{ | ||
#vardefine:page|58}} | #vardefine:page|58}} | ||
|15.1.4={{ | |15.1.4={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|If multiple files are to be created append 01, 02 etc. so as not to confuse the sorting order.}}{{ |
#vardefine:fulldesc|When preparing multiple types of data to sort in the same game and changing the sorting order of save data in the same game, use sort data such as "Same game sort data + 01, 02" so as not to confuse the sorting order with another game.}}{{ | #vardefine:fulldesc|When preparing multiple types of data to sort in the same game and changing the sorting order of save data in the same game, use sort data such as "Same game sort data + 01, 02" so as not to confuse the sorting order with another game.}}{{ | ||
#vardefine:page|58}} | #vardefine:page|58}} | ||
|15.1.5={{ | |15.1.5={{ | ||
| − | #vardefine:shortdesc|A save file should have its | + | #vardefine:shortdesc|A save file should have its own unique icon so it can be clearly recognised in the [[Sega Dreamcast/Boot ROM|boot ROM]].}}{{ |
#vardefine:fulldesc|Each application should have its own unique icon. The unique icon allows each application's save files to be recognized in the Boot ROM File Control Menu.}}{{ | #vardefine:fulldesc|Each application should have its own unique icon. The unique icon allows each application's save files to be recognized in the Boot ROM File Control Menu.}}{{ | ||
#vardefine:page|59}} | #vardefine:page|59}} | ||
|15.1.6={{ | |15.1.6={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|Observe the rules outlined in section 23, "Ethics Considerations" when producing "Visual Comments" (the "data" icon)}}{{ |
#vardefine:fulldesc|When preparing Visual Comments, observe the rules outlined in "23. Ethics Considerations" to avoid improper ethics in the comments.}}{{ | #vardefine:fulldesc|When preparing Visual Comments, observe the rules outlined in "23. Ethics Considerations" to avoid improper ethics in the comments.}}{{ | ||
#vardefine:page|59}} | #vardefine:page|59}} | ||
|15.1.7={{ | |15.1.7={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|For save files, allocate the maximum number of blocks of memory required at the start, even if not all the space is used from the beginning. Do not save filler data in the empty space.}}{{ |
#vardefine:fulldesc|For files where the size will grow over time, allocate the maximum number of blocks at the start. For example, if level one data takes two blocks to store the game progress, but level two takes four blocks, then you should allocate four blocks for all level data. In this case, when the data to be saved is smaller than the number of blocks allocated, do not save filler data in the empty space.}}{{ | #vardefine:fulldesc|For files where the size will grow over time, allocate the maximum number of blocks at the start. For example, if level one data takes two blocks to store the game progress, but level two takes four blocks, then you should allocate four blocks for all level data. In this case, when the data to be saved is smaller than the number of blocks allocated, do not save filler data in the empty space.}}{{ | ||
#vardefine:page|60}} | #vardefine:page|60}} | ||
|15.2.1.1a={{ | |15.2.1.1a={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|On the memory card selection screen, allow controllers and cards to be selected even if they are not available or compatible.}}{{ |
#vardefine:fulldesc|Regardless of whether the port (controller) is being used (compatible), or not used (compatible), make the memory card inserted in either expansion socket selectable.}}{{ | #vardefine:fulldesc|Regardless of whether the port (controller) is being used (compatible), or not used (compatible), make the memory card inserted in either expansion socket selectable.}}{{ | ||
#vardefine:page|63}} | #vardefine:page|63}} | ||
|15.2.1.1b={{ | |15.2.1.1b={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|The selected port and expansion socket for a memory card must be clearly indicated.}}{{ |
#vardefine:fulldesc|When allowing the user to select the port and expansion socket for a memory card, the user's selection (for example, Port A Expansion Socket 2) should be clearly indicated.}}{{ | #vardefine:fulldesc|When allowing the user to select the port and expansion socket for a memory card, the user's selection (for example, Port A Expansion Socket 2) should be clearly indicated.}}{{ | ||
#vardefine:page|63}} | #vardefine:page|63}} | ||
| − | |15.2. | + | |15.2.2={{ |
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|If an autosave feature is in effect and memory card is removed during play, the game must be paused and a message displayed asking that the memory card be reinserted when it is time to save. If a save file with an identical timestamp and checksum is detected, the game should resume.}}{{ |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
#vardefine:fulldesc|If a memory card is removed during the game, play must be paused and a message displayed asking that the memory card be replaced at the time of saving. If a memory card having the same save file (identical time stamp and checksum) as that removed is reinserted, the game resumes.}}{{ | #vardefine:fulldesc|If a memory card is removed during the game, play must be paused and a message displayed asking that the memory card be replaced at the time of saving. If a memory card having the same save file (identical time stamp and checksum) as that removed is reinserted, the game resumes.}}{{ | ||
#vardefine:page|66}} | #vardefine:page|66}} | ||
|15.2.3={{ | |15.2.3={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|Unless saving data, swapping memory cards while 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}} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|15.4a={{ | |15.4a={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|A message notifying that the game is saving (and not to turn the power off) should be displayed on-screen while a save is in progress. With games which autosave, this message only needs to appear if the save lasts for more than one second.}}{{ |
#vardefine:fulldesc|Except in the case of autosaving, a caution message such as "Saving, do not turn Power off" should be displayed on the TV screen while a save is in progress. It can be assumed that data may be lost if power is turned off or a reset performed while saving, so the caution message is important. Also, even when using auto save, display a message on the TV screen such as "Executing save. Do not turn off the power" as a warning when save time lasts for more than one second.}}{{ | #vardefine:fulldesc|Except in the case of autosaving, a caution message such as "Saving, do not turn Power off" should be displayed on the TV screen while a save is in progress. It can be assumed that data may be lost if power is turned off or a reset performed while saving, so the caution message is important. Also, even when using auto save, display a message on the TV screen such as "Executing save. Do not turn off the power" as a warning when save time lasts for more than one second.}}{{ | ||
#vardefine:page|67}} | #vardefine:page|67}} | ||
| Line 373: | Line 346: | ||
|15.4e={{ | |15.4e={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|If overwriting a VMU executable software file, a message (mentioning that it is an executable) must be displayed asking if it is okay to overwrite.}}{{ |
#vardefine:fulldesc|Before overwriting a VMU Executable Game file (A game that is designed to run on an undocked VMU) in a Sega Dreamcast application, a caution message such as "A VMU Game is installed. Okay to overwrite? | #vardefine:fulldesc|Before overwriting a VMU Executable Game file (A game that is designed to run on an undocked VMU) in a Sega Dreamcast application, a caution message such as "A VMU Game is installed. Okay to overwrite? | ||
(YES/NO)" and allow the user to make the choice. No particular message display is needed during 15.2.2, Autosave or when 15.2.3, High scores, etc. are saved.}}{{ | (YES/NO)" and allow the user to make the choice. No particular message display is needed during 15.2.2, Autosave or when 15.2.3, High scores, etc. are saved.}}{{ | ||
| Line 379: | Line 352: | ||
|15.5a={{ | |15.5a={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|If when executing a save and no memory card is inserted, display a messasge notifying the user of a lack of memory card, and the number of blocks required to save.}}{{ |
#vardefine:fulldesc|When no memory card is installed, indicate the required space (number of blocks) and display a warning message such as "A memory card with at least xx blocks of space is required for saving. Cancel save? | #vardefine:fulldesc|When no memory card is installed, indicate the required space (number of blocks) and display a warning message such as "A memory card with at least xx blocks of space is required for saving. Cancel save? | ||
(YES/NO)".}}{{ | (YES/NO)".}}{{ | ||
| Line 385: | Line 358: | ||
|15.5b={{ | |15.5b={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|If there are not enough free blocks on a memory card to save, display a message indicating how many blocks are needed. Check all memory cards for space.}}{{ |
#vardefine:fulldesc|When there is not enough free space (blocks) on an inserted memory card, indicate the lack of empty space (number of blocks) and display a warning message such as "There are not enough free memory blocks. XX empty blocks are required for saving. Cancel save? (YES/NO)". Check all installed memory cards to determine if any memory card has enough space (blocks).}}{{ | #vardefine:fulldesc|When there is not enough free space (blocks) on an inserted memory card, indicate the lack of empty space (number of blocks) and display a warning message such as "There are not enough free memory blocks. XX empty blocks are required for saving. Cancel save? (YES/NO)". Check all installed memory cards to determine if any memory card has enough space (blocks).}}{{ | ||
#vardefine:page|69}} | #vardefine:page|69}} | ||
| Line 395: | Line 368: | ||
|15.5d={{ | |15.5d={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|If the user cannot save, the user should be told that saving cannot occur and be asked whether to continue.}}{{ |
#vardefine:fulldesc|For the times when one of the above-written messages "Empty space not sufficient" or "Memory card not inserted" or when auto saving with 15.2.2 or 15.2.3 are displayed, a warning message such as "A memory card with at least xx blocks of space is required for saving. The game can continue, but saving will not be possible. Continue game? (YES/NO)" should also be displayed. Also, after displaying the warning message, if a memory card is inserted, auto save (warning screen sequence) should be restarted. When a warning message is displayed once, it is not necessary to display the message again unless power to the main unit is turned off, except in cases when the memory card is inserted as mentioned above.}}{{ | #vardefine:fulldesc|For the times when one of the above-written messages "Empty space not sufficient" or "Memory card not inserted" or when auto saving with 15.2.2 or 15.2.3 are displayed, a warning message such as "A memory card with at least xx blocks of space is required for saving. The game can continue, but saving will not be possible. Continue game? (YES/NO)" should also be displayed. Also, after displaying the warning message, if a memory card is inserted, auto save (warning screen sequence) should be restarted. When a warning message is displayed once, it is not necessary to display the message again unless power to the main unit is turned off, except in cases when the memory card is inserted as mentioned above.}}{{ | ||
#vardefine:page|69}} | #vardefine:page|69}} | ||
|15.5e={{ | |15.5e={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|If the save location of high scores and configuration data is assigned to port A, extension socket 1 (according to 15.2.3), messages should reflect the need to place a memory card in this location.}}{{ |
#vardefine:fulldesc|If the save location of high scores and configuration data is assigned to Port A extension socket 1 according to 15.2.3, the port and expansion socket should be indicated in the caution message, such as "A memory card is not inserted in Port A Extension Socket 1. Please insert a memory card at this location to save High Score."}}{{ | #vardefine:fulldesc|If the save location of high scores and configuration data is assigned to Port A extension socket 1 according to 15.2.3, the port and expansion socket should be indicated in the caution message, such as "A memory card is not inserted in Port A Extension Socket 1. Please insert a memory card at this location to save High Score."}}{{ | ||
#vardefine:page|69}} | #vardefine:page|69}} | ||
| Line 425: | Line 398: | ||
|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}} | ||
|15.10.1={{ | |15.10.1={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|When saving, an on-screen indicator should be displayed to show a save is in progress.}}{{ |
#vardefine:fulldesc|(While saving) When returning to normal processing after starting a save, an on-screen indicator (such as a progress bar at the bottom) must be provided to show the user that a save is in progress. Soft reset and CD door open conditions should be indicated in a manner that is compatible with the normal save indication.}}{{ | #vardefine:fulldesc|(While saving) When returning to normal processing after starting a save, an on-screen indicator (such as a progress bar at the bottom) must be provided to show the user that a save is in progress. Soft reset and CD door open conditions should be indicated in a manner that is compatible with the normal save indication.}}{{ | ||
#vardefine:page|74}} | #vardefine:page|74}} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|16.1={{ | |16.1={{ | ||
| Line 443: | Line 411: | ||
#vardefine:fulldesc|When loading a file from a disc, display a message such as "Loading..." on the screen when reading takes longer than 10 seconds, or otherwise indicate to the user that the delay is not due to a hangup from a bug.}}{{ | #vardefine:fulldesc|When loading a file from a disc, display a message such as "Loading..." on the screen when reading takes longer than 10 seconds, or otherwise indicate to the user that the delay is not due to a hangup from a bug.}}{{ | ||
#vardefine:page|77}} | #vardefine:page|77}} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|17.3={{ | |17.3={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|For multi-disc games (with the lid closed), performing a [[software reset]] should return to the current disc's title screen (i.e. if using disc 2, do not prompt for disc 1).}}{{ |
#vardefine:fulldesc|Except as stated in section 17.3.1, a soft reset after starting a game must result in a jump to the Title Screen of the disc currently inserted in the Main Unit (for instance, a reset with Disc 3 installed results in display of the Disc 3 Title Screen). As described in Chapter 4.1.4.2, Omnibus System Case, executing a soft reset from the Title Loop of any disc brings up the Main Unit Boot ROM Menu (the Multi-Player screen in Saturn).}}{{ | #vardefine:fulldesc|Except as stated in section 17.3.1, a soft reset after starting a game must result in a jump to the Title Screen of the disc currently inserted in the Main Unit (for instance, a reset with Disc 3 installed results in display of the Disc 3 Title Screen). As described in Chapter 4.1.4.2, Omnibus System Case, executing a soft reset from the Title Loop of any disc brings up the Main Unit Boot ROM Menu (the Multi-Player screen in Saturn).}}{{ | ||
#vardefine:page|80}} | #vardefine:page|80}} | ||
|17.3.1={{ | |17.3.1={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|At the disc swapping screen with the lid open, a [[software reset]] must return to the [[Sega Dreamcast/Boot ROM|boot ROM]].}}{{ |
#vardefine:fulldesc|At the disc switching screen, doing a soft reset when the disc lid is open moves the user to the Main Unit Boot ROM screen. Setting the soft reset jump destination to the Main Unit Boot ROM Menu allows the user to check the title and saved files on the menu if he inserts the wrong disc. When a soft reset is done before the disc lid is opened on the disc switching screen, jump to the "Disc title screen".}}{{ | #vardefine:fulldesc|At the disc switching screen, doing a soft reset when the disc lid is open moves the user to the Main Unit Boot ROM screen. Setting the soft reset jump destination to the Main Unit Boot ROM Menu allows the user to check the title and saved files on the menu if he inserts the wrong disc. When a soft reset is done before the disc lid is opened on the disc switching screen, jump to the "Disc title screen".}}{{ | ||
#vardefine:page|80}} | #vardefine:page|80}} | ||
| Line 465: | Line 428: | ||
|17.4b={{ | |17.4b={{ | ||
| − | #vardefine:shortdesc|After swapping discs, execute the disc check routine in the | + | #vardefine:shortdesc|After swapping discs, execute the disc check routine in the [[Sega Dreamcast/Boot ROM|boot ROM]].}}{{ |
#vardefine:fulldesc|After switching discs, always execute the Disc Check routine in the Boot ROM.}}{{ | #vardefine:fulldesc|After switching discs, always execute the Disc Check routine in the Boot ROM.}}{{ | ||
#vardefine:page|82}} | #vardefine:page|82}} | ||
| Line 485: | Line 448: | ||
|17.5={{ | |17.5={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|If a save file is loaded which requires a different disc, display a message stating it is the incorrect disc, alongside the procedure to swap the disc.}}{{ |
#vardefine:fulldesc|When a save file is loaded for a disc other than the one currently inserted, a caution message must be displayed, such as "Press the OPEN button to open the disc lid and replace the Disc. After inserting Disc X, close the disc lid."}}{{ | #vardefine:fulldesc|When a save file is loaded for a disc other than the one currently inserted, a caution message must be displayed, such as "Press the OPEN button to open the disc lid and replace the Disc. After inserting Disc X, close the disc lid."}}{{ | ||
#vardefine:page|85}} | #vardefine:page|85}} | ||
| Line 495: | Line 458: | ||
|18.1b={{ | |18.1b={{ | ||
| − | #vardefine:shortdesc|Stop vibration from the [[Jump Pack]] when paused or returning to the | + | #vardefine:shortdesc|Stop vibration from the [[Jump Pack]] when paused or returning to the [[Sega Dreamcast/Boot ROM|boot ROM]].}}{{ |
#vardefine:fulldesc|Stop vibration with the Jump Pack during pause or when transferring to the Main Unit Boot ROM. In the rules up to now, whether or not to stop vibration of the Jump Pack "during transfer to the Main Unit Boot ROM" was not specially regulated, but from this version, stopping the vibration on the application side is regulated.}}{{ | #vardefine:fulldesc|Stop vibration with the Jump Pack during pause or when transferring to the Main Unit Boot ROM. In the rules up to now, whether or not to stop vibration of the Jump Pack "during transfer to the Main Unit Boot ROM" was not specially regulated, but from this version, stopping the vibration on the application side is regulated.}}{{ | ||
#vardefine:page|87}} | #vardefine:page|87}} | ||
| Line 505: | Line 468: | ||
|18.1.1={{ | |18.1.1={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|Only support up to four Jump Packs. If a fifth is detected, only enable the first four (starting with port A, working towards port D).}}{{ |
| − | #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 (or character input screen) 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}} | ||
|18.2b={{ | |18.2b={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|Clearly distinguish to the user whether the hardware or software keyboard is being used.}}{{ |
#vardefine:fulldesc|During hardware keyboard input, allow the user to distinguish which input mode is currently being used. When displaying the software keyboard screen and input palette screen, the user should know which input is currently possible.}}{{ | #vardefine:fulldesc|During hardware keyboard input, allow the user to distinguish which input mode is currently being used. When displaying the software keyboard screen and input palette screen, the user should know which input is currently possible.}}{{ | ||
#vardefine:page|89}} | #vardefine:page|89}} | ||
|18.2.2a={{ | |18.2.2a={{ | ||
| − | #vardefine:shortdesc|The {{key|S1}} and {{key|S2}} should be mapped to {{L}} and {{R}}, respectively.}}{{ | + | #vardefine:shortdesc|The {{key|S1}} and {{key|S2}} keys should be mapped to {{L}} and {{R}}, respectively.}}{{ |
#vardefine:fulldesc|Use the special keys on the hardware keyboard, S1 and S2, as the left and right triggers, respectively.}}{{ | #vardefine:fulldesc|Use the special keys on the hardware keyboard, S1 and S2, as the left and right triggers, respectively.}}{{ | ||
#vardefine:page|90}} | #vardefine:page|90}} | ||
|18.2.2b={{ | |18.2.2b={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|When using a standard controller alongside a keyboard, {{A}} should accept, {{B}} should be backspace and {{Y}} should be delete. The d-pad should be used for controlling the cursor and the analogue stick used to scroll the page.}}{{ |
#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 506: | ||
|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 516: | ||
|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 531: | ||
|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}} | ||
|18.5.4={{ | |18.5.4={{ | ||
| − | #vardefine:shortdesc|Due to televisions or monitors with potential overscan, the screen should have a 16 (for 640x480 resolutions) or 8 (for 320x240 resolutions) pixel margin where user cannot aim.}}{{ | + | #vardefine:shortdesc|Due to televisions or monitors with potential overscan, the screen should have a 16 (for 640x480 resolutions) or 8 (for 320x240 resolutions) pixel margin where the user cannot aim.}}{{ |
#vardefine:fulldesc|Depending on the TV or monitor manufacturer and the type of monitor, the entire screen may not be displayed at the edges. For this reason, the margins on all sides on the screen should be at least 16 pixels (for a 640x480 pixel screen) or 8 pixels (for a 320x240 pixel screen) within which the user cannot aim.}}{{ | #vardefine:fulldesc|Depending on the TV or monitor manufacturer and the type of monitor, the entire screen may not be displayed at the edges. For this reason, the margins on all sides on the screen should be at least 16 pixels (for a 640x480 pixel screen) or 8 pixels (for a 320x240 pixel screen) within which the user cannot aim.}}{{ | ||
#vardefine:page|98}} | #vardefine:page|98}} | ||
|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 548: | ||
|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 commercially 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 610: | Line 573: | ||
|19.1c={{ | |19.1c={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|When connecting to network applications (web browsers, email, chat), use the connection details saved in the [[Sega Dreamcast/Boot ROM|boot ROM]].}}{{ |
#vardefine:fulldesc|When connecting to a network applications like a Web Browser, Mailer, or Chat, confirm the setting data for connecting to an IP address in Main Unit memory and connect based on that setting.}}{{ | #vardefine:fulldesc|When connecting to a network applications like a Web Browser, Mailer, or Chat, confirm the setting data for connecting to an IP address in Main Unit memory and connect based on that setting.}}{{ | ||
#vardefine:page|102}} | #vardefine:page|102}} | ||
|19.1d={{ | |19.1d={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|If an IP address can be set within software, the [[Sega Dreamcast/Boot ROM|boot ROM]] save must reflect the change.}}{{ |
#vardefine:fulldesc|When there is a function to set the IP Address within an application (currently only permission for settings by Dreamcast browser is given), Main Unit memory settings should be adjusted to application settings that are changed.}}{{ | #vardefine:fulldesc|When there is a function to set the IP Address within an application (currently only permission for settings by Dreamcast browser is given), Main Unit memory settings should be adjusted to application settings that are changed.}}{{ | ||
#vardefine:page|102}} | #vardefine:page|102}} | ||
|19.3a={{ | |19.3a={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|When downloading files, save to the location dictated by the save definition provided alongside the download. If a definition file does not exist, do not download.}}{{ |
| − | #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 635: | Line 600: | ||
|20.1={{ | |20.1={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|Any *.da file saved in the single-density "CD-ROM" area should be voice data.}}{{ |
#vardefine:fulldesc|In the single-density area of the Dreamcast-specific disc, DA (except for non-sound) should be input as voice data. DA sound should be made to run even if the specific-disc is put in a non-Dreamcast CD player.}}{{ | #vardefine:fulldesc|In the single-density area of the Dreamcast-specific disc, DA (except for non-sound) should be input as voice data. DA sound should be made to run even if the specific-disc is put in a non-Dreamcast CD player.}}{{ | ||
#vardefine:page|105}} | #vardefine:page|105}} | ||
|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}} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|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}} | ||
|25.2a={{ | |25.2a={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|Copyright information must conform to the same rules outlined in section 6.2 and chapter 23.}}{{ |
| − | #vardefine:fulldesc|Displaying Copyrights: Observe the rules outlined in Section 6.2, Copyright Display and Chapter 23, Trademark/Copyright Infringement, when creating copyright displays.}}{{ | + | #vardefine:fulldesc|Displaying Copyrights: Observe the rules outlined in Section 6.2, Copyright Display and Chapter 23, Trademark/Copyright Infringement, when creating copyright displays. |
| + | |||
| + | (SEGA Brand only) official material is displayed as | ||
| + | <tt>"©_SEGA_ENTERPRISES,_LTD.,_1999" | ||
| + | _= space | ||
| + | "© [Official company name][Year of release]"</tt> | ||
| + | However, when display on the visual memory is difficult due to lack of hardware display space, the following | ||
| + | can be used. | ||
| + | <tt>"©_SEGA_1999" | ||
| + | _= space</tt>}}{{ | ||
#vardefine:page|122}} | #vardefine:page|122}} | ||
|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 640: | ||
|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}} | ||
|25.4={{ | |25.4={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|An executable file should not re-write its own Visual Comment.}}{{ |
#vardefine:fulldesc|An executable file should not rewrite its own Visual Comment. Even the smallest Visual Comment requires almost 5 blocks, so having the executable file rewrite even a single block of Visual Memory would probably cause an unacceptably long delay and significant increase in power consumption, and the rewrite process could not be guaranteed to finish normally.}}{{ | #vardefine:fulldesc|An executable file should not rewrite its own Visual Comment. Even the smallest Visual Comment requires almost 5 blocks, so having the executable file rewrite even a single block of Visual Memory would probably cause an unacceptably long delay and significant increase in power consumption, and the rewrite process could not be guaranteed to finish normally.}}{{ | ||
#vardefine:page|122}} | #vardefine:page|122}} | ||
|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}} | ||
|25.6={{ | |25.6={{ | ||
| − | #vardefine:shortdesc| | + | #vardefine:shortdesc|The last three characters of a 12-character single-application file name should be "_VM".}}{{ |
#vardefine:fulldesc|The last three characters of a 12-character single-application file name should be '_VM'.}}{{ | #vardefine:fulldesc|The last three characters of a 12-character single-application file name should be '_VM'.}}{{ | ||
#vardefine:page|123}} | #vardefine:page|123}} | ||
|26={{ | |26={{ | ||
| − | #vardefine:shortdesc|Software must | + | #vardefine:shortdesc|Software must abide by the guidelines provided by the NHK and Japan Civil Broadcasting Union in regards to certain light patterns or flashing lights.}}{{ |
#vardefine:fulldesc|A very small number of individuals may experience seizures when exposed to certain light patterns or flashing lights. Exposure to certain patterns or backgrounds on a television screen or while playing videogames could induce a seizure in such individuals. Certain conditions may induce undetected seizure symptoms even in persons who have no history of prior seizures or epilepsy. | #vardefine:fulldesc|A very small number of individuals may experience seizures when exposed to certain light patterns or flashing lights. Exposure to certain patterns or backgrounds on a television screen or while playing videogames could induce a seizure in such individuals. Certain conditions may induce undetected seizure symptoms even in persons who have no history of prior seizures or epilepsy. | ||
Because of this possibility, an appropriate seizure warning should be included on videogame packaging. The following guidelines have been provided by NHK (Japan Broadcasting Co.), and should be used as a guideline for precautionary measures: | Because of this possibility, an appropriate seizure warning should be included on videogame packaging. The following guidelines have been provided by NHK (Japan Broadcasting Co.), and should be used as a guideline for precautionary measures: | ||
| Line 707: | Line 675: | ||
}}</div> | }}</div> | ||
| − | + | {{ComplianceDetails/Output|{{{1|}}}}}<noinclude> | |
| − | |||
| − | |||
| − | |||
| − | |||
{{ComplianceTable| | {{ComplianceTable| | ||
| Line 720: | Line 684: | ||
}} | }} | ||
}} | }} | ||
| − | |||
[[Category:Templates]] | [[Category:Templates]] | ||
</noinclude> | </noinclude> | ||
Latest revision as of 11:56, 10 September 2024
| : [1] |
| Compilance | Screenshot(s) | Pass/fail | Comments |
|---|---|---|---|
| Pass | dsfahukjsadgihkdgsali afsdifads iljfd sijlafds aijl |