10 Common Problems and Bugs

The following content describes common cases that result in inquiries from the Lotcheck Department or products failing Lotcheck. Knowing about these examples may avoid Lotcheck delays and increase the probability of passing Lotcheck. Use this information when preparing Lotcheck submissions.

In addition, refer to this information for handling cases where content described in these examples is reported as a Lotcheck issue. For each example, if the detailed procedure is described on a separate page, there will be a link to that page.

Contents

Note: The following sections are organized based on the conditions or type of problem.

Before Submitting to Lotcheck

OMAS Application

⇒ Related Page: 3.9 Settings for Related Systems and Networks > OMAS

The OMAS request does not advance to During Development/Lotcheck Queue. (An error occurs when clicking the Submit button for Lotcheck.)

⇒ Solution: See 11 in the 9 FAQ/NDP Errors table.

The features entered on OMAS do not match the network features that were actually implemented for the ROM.

  • Example 1: Network features are implemented, even though they were not applied for in OMAS.
    ⇒ Solution: Apply for network features in OMAS.
  • Example 2: There are OMAS entries included for features that are not implemented in the ROM submitted to Lotcheck. (These entries might include features that will be added in the future, or that were present in an earlier development phase but have subsequently been removed.)
    ⇒ Solution: If the OMAS request content is incorrect, correct it.
    If network features are not implemented in the version of the ROM that will be submitted soon, but will cause problems in development if an OMAS request is not made, include an OMAS request in the next patch. For more information, use the forums on the OMAS site.

The NEX library version for the ROM and the OMAS application do not match because the NEX library version included in the ROM was updated but not for the OMAS application.

⇒ Solution: Correct the NEX library version in the OMAS request and resubmit with the ROM.

Independent Server Settings

⇒ Related Page: 3.9 Settings for Related Systems and Networks > Independent Servers

The DNS data was not entered correctly in NDP > Release Dashboard > Features > Independent Server > Name Resolution.

⇒ Solution: Rest the mouse pointer on the ? to display the tooltips for each entry, and enter the correct information.

The request recipient FQDN for consumables and subscription service items remains in the development environment (dd1), and was not changed to the Lotcheck environment (sp1).

⇒ Solution:
Complete the steps in the following documentation.

Nintendo Switch Service Item Programming Manual > Notes When Submitting the Application to Lotcheck > Nintendo eShop Server Accessed by the Independent Server Geared Toward the Right Environment?

No account for independent services has been provided.

⇒ Solution: Provide 10 or more accounts for each supported region: Japan/Asia, North America, and Europe.

Example: The application is only released in Japan/Asia and Europe, so provide 20 or more accounts.

The IP address used by the Lotcheck Department for white-listing has not been added.

⇒ Solution: See the following documentation and add the appropriate IP address to the whitelist.

NDP > DEVELOPER SUPPORT > Nintendo Switch > Technical Information > Network Guidance > Canceling Access Control When Submitting a Title Using Independent Servers to Lotcheck

Entering Age Ratings

⇒ Related Page: 3.8 Entering Rating Settings

Rating Pending or Not Required is selected in NDP > Age Rating.

If Rating Pending or Not Required is selected for the rating value, it will be reported as a problem by the Lotcheck Department except in cases with special circumstances.

⇒ Solution:

  • Submit to Lotcheck only after obtaining an official rating, even for demo software.
  • Do not set ratings for regions where the software will not be released.
  • For applications that are exempt from game-rating evaluation, select the rating agency for the release region and specify Not Required for the rating (The value of the Age element in the NMETA file is 0).
    Consult with the NDP Licensing contact in advance for any questions or concerns. (Reference: 8 Contacts for Inquiries Before, During, and After Lotcheck Testing)

The rating obtained from IARC is used for a physical product release.

⇒ Solution: Releasing a packaged version of the game requires getting a standard rating from local rating agencies. You cannot release packaged versions with the rating obtained from IARC.
You must make a direct request to the rating agency.
In addition, upload the obtained rating certificate (the notification of the review result) in NDP by going to Age Rating and clicking Add Standard Rating.

Entering Features Page Information

The content on the Features page in Features > Play Modes > Handheld Mode is incorrect.

⇒ Solution: Enter correct information for Maximum number of players in handheld mode and Supported ways of holding Joy-Con controllers in handheld mode. For more information about entering the data, see the applicable tooltips.

Entering Test Scenarios

There is not enough information for the test scenarios for downloadable content.

⇒ Related Page: 3.6 Entering Test Scenarios > Entering Test Scenarios > Procedure for Downloadable Content

Guidelines

Does not comply with Guideline 0083: Complying With Rules in the Official Terminology Lists.

⇒ Solution: Use the terminology in the Nintendo Switch Terminology and amiibo Terminology lists in each language.

Debug

For applications that support multiple languages, text is not displayed correctly or the encoding is scrambled depending on the language.

⇒ Solution: Debug for each supported language.

Bugs occur when changing play modes or controllers.

⇒ Solution: The user may change play mode or controllers at any time on the Nintendo Switch, so assume the possibility of this type of operation when you are debugging.
Example 1: Changing play modes causes object coordinates to become misaligned.
Example 2: Changing controllers causes some buttons to become inoperable.

The Nintendo eShop jump destination is incorrect.

⇒ Solution: Specify the correct jump destination.
Example: The same title is separated into different products based on sales region, but the eShop jump destination is not specified for each product.

There is a problem when the TV resolution is set to 480p. No video is displayed. Video is scrambled.

⇒ Solution: Perform debugging at each resolution.

Accessory names or service names belonging to non-Nintendo platforms remain on a ported version of a released title.

⇒ Solution: Remove the accessory names or service names belonging to non-Nintendo platforms.

Other

Only the company name and no contact method is described in the contact information displayed in the system features.

⇒ Solution: Edit the software legal information in SLIM (https://slim.mng.nintendo.net/slim/login). Add user contact methods, such as an email address.

When Requesting Lotcheck

Downloadable Content

A release that supports the e-commerce downloadable content feature was submitted for Lotcheck, but the downloadable content was not submitted for Lotcheck, so the e-commerce feature cannot be tested.

⇒ Related Page: 3.12 Preparations for Downloadable Content > Submit Both Initial Release/Patch and Downloadable Content for Lotcheck

Downloadable content that becomes available starting with a particular release version was submitted to Lotcheck, but the patch for that release version was not submitted to Lotcheck.

⇒ Related Page: 3.12 Preparations for Downloadable Content > Submit Both Initial Release/Patch and Downloadable Content for Lotcheck

After Submitting to Lotcheck

Handling Issues Reported by the Lotcheck Department

After changing the content in Features, Test Scenarios, or Age Rating as directed by the Lotcheck Department, the Submit Edited Information button was not clicked. As a result, the Lotcheck Department has not received the changed content.

⇒ Related Page: 4 Items for the Developer to Address During Lotcheck > Handling Issues Reported by the Lotcheck Department > Second row of the table > Handling by Developer > Example

No response for issues reported by the Lotcheck Department in the Lotcheck Issues tab.

⇒ Related Page:

4 Items for the Developer to Address During Lotcheck > Lotcheck Process > Handling by Developer

7 Notification Email From NDP > List of Notification Emails > [Needs Response] A thread was created or a post was submitted to a thread by the developer, Nintendo, or NDP automatic processing (Messages tab or Lotcheck Issues Report).

 


CONFIDENTIAL