​

XR-001: Title Stability

​

FMA scenario severities

​

001-01 Title Stability

• Be aware of issues that are inconsistent between CERT and CERT.DEBUG sandboxes.
• Loading times are about setting user expectations and creating an experience that works in the game. For example, if all load times are always about 1 minute with an animated spinner, then suddenly a level takes 10 minutes, the user perceives something is wrong with the game or console.
• “Partially unresponsive state” means that the title remains unresponsive to the majority of user input, but does respond to minimal controller input (such as A button input, left or right stick input, and so on).
• Titles under 3 GB in size with an initial play marker greater than 65% can use the reduced Probability -3 for occurrence when stability issues are encountered during streaming install. Titles outside of this threshold should start with a Probability 2 and increase as needed.

​

001-02 Title Stability After Suspending

• Known system issue: Disconnect the LAN cable from the console, boot the title, reconnect the LAN cable and wait for connectivity, and then suspend the title. The title reports Package execution state: 0 (unknown).
• When returning from a suspended state, a title is expected to regain full functionality, which includes reestablishing a connection to online or partner services. If a user returns from a suspended state and can’t view an online service, such as leaderboards, but scores are still tracked and verified that they post to the leaderboards following a termination, the title reestablished the connection to online or partner services, but the feature isn’t functioning as expected (log under Title Integrity — Moderate in most cases).
• Suggested probability of 6 for core or likely areas of the title (for example, main menu). Probability of -3 for suspending during a loading screen. Increase or decrease where it’s felt appropriate to do so.