Readme-TitleCheckTool-1_1-en.html
Menu Display Check Tool for Nintendo 3DS Networked RIDs
Contents
- Introduction
- Package Content
- Notes
- Advance Preparations
- How to Update Title Information
- How to Run the Tool
- Verification Methods
- Errors
- Checking Videos (North America Only)
- Known Bugs
- Revision History
This package contains a tool for checking whether or not the content recorded in the RID demo's ROM information file will display correctly on the Nintendo 3DS networked RID Menu.
Using it, you can change the name of the triMeta.xml file output by the macros in the RID demo ROM information file to TR_000000.xml, and check the screen display in a development environment.
- TitleCheckMenu_JP.cci => Japanese ROM.
- TitleCheckMenu_US.cci => North American ROM.
- /SDImagesCIS => Images written onto an SD card.
Only use this tool to check how title information is displayed on the RID Menu of Nintendo 3DS networked RIDs.
This tool is not for debugging behavior.
If there are any abnormalities in the SD Card data, the program may hang.
Currently there is no way to fix this. If a hang occurs, redo the checks from the beginning.
The following preparations are required before using this tool.
- Prepare an SD Card.
- Place a folder entitled SDImagesCIS directly beneath the SD Card's root folder.
- Replace the applicable files with the development title's .xml files, refer to 5 How to Update Title Information.
If you are using banner files (.ban) or package images (.pac1), rename and replace those as well.
- Insert the SD Card into a development system.
Warning: Since a log will be output, you must ensure the SD Card is not write-protected.
- Write the ROM (.cci file) for the corresponding market to a FLASH card.
The following sample files are contained within the SDImageCIS folder.
Replace with each development title file as necessary. Rename them and perform the necessary executions and checks.
TR_000000.xml |
Title Meta-information (xml) |
TR_000000.ban |
Banner File (bnr) |
TR_000000.cd |
Content Descriptor Image (jpeg) (Only used for North American version) |
TR_000000.mof1 |
Movie File (moflex) (Only Used for North American version) |
TR_000000.pac1 |
Package Image (jpeg) |
TR_000000.rel |
Related Software Image (jpeg) |
Warning: Do not alter the following files:
- tri3DSIntro.xml
- triBestSeller.xml
- triList.xml
- triNewRelease.xml
- triRecomList.xml
- triStandbyMovieList.xml
- Launch the ROM (from either the HOME Menu or testmenu).
- After running the ROM, copy the content files written onto the SD Card to extended save data.
Verify that the files have been copied correctly (the state of the copy process is displayed on the lower screen of the Nintendo 3DS).
"Press any button" will be displayed upon successful completion of the copy process; do so and the RID Menu will launch.
If the copy fails, an error will appear in the center of the Nintendo 3DS system's lower screen; determine the cause of the error by checking the log file written in the SD card's root folder (cis_log.txt, recorded in UTF-16 format).
When you launch the RID Menu, the following menu will be displayed.
- Japanese Version: "おすすめソフト"、"ニンテンドー3DSの紹介"
- North American Version: "About the Nintendo 3DS", "New Releases", "Nintendo Recommended"
In order to check whether or not the title information and images are displaying correctly, select Nintendo Recommended (おすすめソフト for the Japanese version). Then, from the title list screen, select your title.
If there are problems with the XML file, an error will be displayed on the lower screen of the Nintendo 3DS during boot-up. Example: ERROR_PACKAGEMANAGER_XML
In this case, a log file (cis_log.txt) is output to the SD Card's root folder.
Below are common errors.
- 3DSXML illigal element : 'xxxxxx',TR_yyyyyy.xml
There is a problem with the content of the xxxxx element in TR_yyyyyy.xml. This could be caused by an error in numerical values or an excess of characters.
- 3DSXML parse error : xxxxxx.xml
Failed to parse xxxxxx.xml. Check the format of the XML file.
- 3DSXML parse xml buffer over(xxxxxx.xml)
A buffer overflow occurred while parsing xxxxxx.xml. This occurs when the value of an element is too large as a single character string.
Character counts that are too high will cause this.
- SPI spi error[file_info],XXXXXXXX,yyyyyy
- SPI spi error[file_info2],XXXXXXXX,yyyyyy
- SPI spi error[file_read],XXXXXXXX,yyyyyy
Output when the file in question does not exist. Verify whether or not the yyyyyy file exists.
With this tool, you can play back video files as though they were playing on an RID, and check for any issues with playback (such as sound skipping).
If any problems with playback occur while using this tool, you must make fixes to the video files appropriately to remove them.
- The documentation for ctr_BannerModelConverter states that placing textures with names like COMMON1.ctex in the Textures folder, located within each language's language-specific data, allows you to replace and display a texture that shares a name with one in the COMMON folder. However, there is a bug unique to RIDs where this tool will seek out a texture from other languages if a compatible one does not exist in the corresponding language.
Consequently, if you wish to revise and display textures for each language, set the textures for each language separately.
- It is possible to use a billboard for networked RIDs, but it is implemented differently from the HOME Menu. As a result, there are some some slight differences. As written in the Data Restrictions section of the ctr_BannerModelConverter manual, since the Number-0 Camera is reserved by the HOME Menu, it generally cannot be used. However, if it is used, the billboard will no longer function on the networked RID Menu. For this reason, do not use the Number-0 Camera.
- 2015/02/19
- Revised wording about bug information for section 10 Known Bugs.
- Changed "CTR" to "Nintendo 3DS."
- 2012/08/06
- Added bug information to section 10 Known Bugs.
- 2011/11/04
- Added section 10 Known Bugs.