Kyo_JP
Today is a Diamond
- Joined
- Jul 28, 2018
- Location
- Madrid, Spain
- Favourite title
- Shenmue
- Currently playing
- Virtua Fighter 5 Ultimate Showdown
- PSN
- ElBidimensional
This is the 2nd thread for reporting bugs and issues found by the community. You can find the original one here.
There is one critical point when reporting issues in the QA business, you have to give concrete explanations and be as clear as possible, just think that the people reading the issue does not nothing about and how to find it and determine what is causing it and how to fix it.
Critical information present when reporting bugs:
Current Version:
PS4: 1.03 /1.04 for Shenmue 2(Previous 1.02) / 1.0.1 Japanese SKU
Xbox One: 1.6.0 (1.5.0)
Steam: 1.0.6 (previous 1.05)
Title: What is happening. Short clear description
Platform: In which platform does it happens. Cross information between platforms to determine is a hardware specific issue or it happens in all of them (when possible)
Title Version: The game version where the issue were found. Read updated info above. This is one of the most important points for the team to check if they know it already or if it is a new one.
Category: What feature is affected by the issue. Functionality, settings, audio, video, gameplay, cutscene, save data, control.
Status: Is the issue occurring in the latest build of the game? If it is not fixed mark as Not Fixed (and version of the title if possible). When it is fixed update to Fixed (and version when it was fixed). UPDATE NEW STATUS ADDED: WNF for Will Not Fix when the reported behaviour is also present in the original Dreamcast or Xbox Version of the title. Also implementing Claim Fixed when the studio report a know behaviour as fixed, it will be in this status for two weeks and if nobody reports that is still present it will be closed as Fixed. If a Fixed behaviour is broken with a new update it will be classified as Reopen.
Priority: How severe is the impact of the bug in the user experience? Please understand that the final priority to fix or not a bug is up to SEGA/D3T, but in this case is a measure of how the user perceive it.
Reproduction Steps: How to get to reproduce the issue, this is critical for the game team to replicate it and determine what is causing it and how to fix it.
Observed Result: What is happening (similar to title)
Expected Result: What was suppose to happen instead of the bug.
BUG TEMPLATE EXAMPLE
Title: Bloom is automatically activated when the notebook is opened (What happen)
Platform: PS4/Xbox1/PC
Title Version: 1.X.X
Reproduction rate: X out of X tries (for example 5/10)
Category: Settings
Status: Not Fixed (update with future patch results)
Priority: Severe
Reproduction Steps:
1- Boot the title > Go to settings > Turn Bloom Effect off
2- Start a new game > Observe that the Bloom Effect is off
3- Open the notebook > Pause the Game > Go to Settings
Observed Result: Observe that the Bloom effect is turned on automatically
Expected Result: The settings selected by the user should no be changed by the title without asking.
There is one critical point when reporting issues in the QA business, you have to give concrete explanations and be as clear as possible, just think that the people reading the issue does not nothing about and how to find it and determine what is causing it and how to fix it.
Critical information present when reporting bugs:
Current Version:
PS4: 1.03 /1.04 for Shenmue 2(Previous 1.02) / 1.0.1 Japanese SKU
Xbox One: 1.6.0 (1.5.0)
Steam: 1.0.6 (previous 1.05)
Title: What is happening. Short clear description
Platform: In which platform does it happens. Cross information between platforms to determine is a hardware specific issue or it happens in all of them (when possible)
Title Version: The game version where the issue were found. Read updated info above. This is one of the most important points for the team to check if they know it already or if it is a new one.
Category: What feature is affected by the issue. Functionality, settings, audio, video, gameplay, cutscene, save data, control.
Status: Is the issue occurring in the latest build of the game? If it is not fixed mark as Not Fixed (and version of the title if possible). When it is fixed update to Fixed (and version when it was fixed). UPDATE NEW STATUS ADDED: WNF for Will Not Fix when the reported behaviour is also present in the original Dreamcast or Xbox Version of the title. Also implementing Claim Fixed when the studio report a know behaviour as fixed, it will be in this status for two weeks and if nobody reports that is still present it will be closed as Fixed. If a Fixed behaviour is broken with a new update it will be classified as Reopen.
Priority: How severe is the impact of the bug in the user experience? Please understand that the final priority to fix or not a bug is up to SEGA/D3T, but in this case is a measure of how the user perceive it.
Reproduction Steps: How to get to reproduce the issue, this is critical for the game team to replicate it and determine what is causing it and how to fix it.
Observed Result: What is happening (similar to title)
Expected Result: What was suppose to happen instead of the bug.
BUG TEMPLATE EXAMPLE
Title: Bloom is automatically activated when the notebook is opened (What happen)
Platform: PS4/Xbox1/PC
Title Version: 1.X.X
Reproduction rate: X out of X tries (for example 5/10)
Category: Settings
Status: Not Fixed (update with future patch results)
Priority: Severe
Reproduction Steps:
1- Boot the title > Go to settings > Turn Bloom Effect off
2- Start a new game > Observe that the Bloom Effect is off
3- Open the notebook > Pause the Game > Go to Settings
Observed Result: Observe that the Bloom effect is turned on automatically
Expected Result: The settings selected by the user should no be changed by the title without asking.
Last edited: