Hey All,
After spending a lot of time looking at the bug reporting forums I see a lot of topics getting made that, while they may seem helpful at first, really don’t contribute much other than a single line saying ‘there is a problem with this’.
With the release of 3.5 this forum has exploded with new bug reports.
Solving bugs is not an easy process. A lot of time needs to be put in to isolate the issue. If we could help the PMDT by doing this, it would be better for everyone involved.
This is a list of things to do in order to keep bug reporting streamlined:
RESEARCH
REINSTALL and REPRODUCE
REPORT
First up, RESEARCH
1. Read the Pinned Topics. Carefully. Make sure what you're reporting is not a known issue already.
2. Search the forums to be sure what you've found has not already been reported.
Do this thoroughly. Helping by submitting an unknown bug is awesome.
Submitting something already known is unhelpful.
If you find that your bug is reported already, have a read of the topic. If you can contribute more by 'confirming' it's existence, do so.
3. Make sure what you're reporting is not:
- An intended PM feature
- An intended game-play feature from either Brawl or Melee
- An issue left over from Brawl that can't be fixed yet.
- A workaround resulting from another bug.
- Known
- In turbo mode
- User Error
If you have custom Content: Make sure what you're submitting IS NOT related to the custom content. Do this by trying to reproduce the bug with a default build.
(If you would like help with customised content. Post in the Help forums or the Custom Content forums. This forum is for reporting and logging bugs in the official build.)
REINSTALL and REPRODUCE
Reinstall the default build and try to recreate the bug again. Problems may occur on your SD card and a fresh install may fix a bug you think you’ve found.
It is important to do this because ANY custom content can inadvertently affect the default build.
THE PMDT only want to spend time fixing their bugs, not bugs caused with custom content.
Even without custom content, SD cards can wear out, things can go wrong. The simple process of reinstalling can potentially fix your problem and avoid unnecessary bug reports.
REPORT
Then if you still need to file a bug report, fill out these Details when you make your post:
Topic Title: PM3.6 | <Text about the bug, use good key words>
In the post:
Title of the bug:
Version found in:
Hardware you are running:
Loading Method:
Details:
Attachments:
Custom Content:
For Example:
Title of the bug: [Something Descriptive about the bug, that if other users find your bug they will find your topic upon searching.]
Version found in: [e.g. 3.5: Homebrew: Full set]
Hardware you are running: [wii, or dolphin version number]
Loading Method: [e.g. USB Loader name and ocarina hook-type , Pm ISO, StageBuilder (hackless will be using this)]
Details: A step By step detailed description on how to reproduce the bug.
If you are unable to reproduce the bug. Please provide as many details as possible so others may try to. If this is the case include ‘INTERMITTENT’ in the topic title until it can be refined.
Attachments: Reproduce the bug using the Wi-Fi/replay build if you can. And attach the replay of the match to your post.
Otherwise try to get some screenshots or record a video with your phone (prop it up with something instead of holding it in your hands to avoid shaking).
Make sure the problem is clearly visible.
Custom Content: This should be 'no'. Not even a little. Not even 'a few songs'. Nothing.
Extra Notes:
If we do this we can help the Dev Team solve issues by providing a thorough analysis of the bugs we find.
They've done so much for us, let’s return the favour and make things easier for them.
Regards,
A Software Tester.
After spending a lot of time looking at the bug reporting forums I see a lot of topics getting made that, while they may seem helpful at first, really don’t contribute much other than a single line saying ‘there is a problem with this’.
With the release of 3.5 this forum has exploded with new bug reports.
Solving bugs is not an easy process. A lot of time needs to be put in to isolate the issue. If we could help the PMDT by doing this, it would be better for everyone involved.
This is a list of things to do in order to keep bug reporting streamlined:
RESEARCH
REINSTALL and REPRODUCE
REPORT
First up, RESEARCH
1. Read the Pinned Topics. Carefully. Make sure what you're reporting is not a known issue already.
2. Search the forums to be sure what you've found has not already been reported.
Do this thoroughly. Helping by submitting an unknown bug is awesome.
Submitting something already known is unhelpful.
If you find that your bug is reported already, have a read of the topic. If you can contribute more by 'confirming' it's existence, do so.
3. Make sure what you're reporting is not:
- An intended PM feature
- An intended game-play feature from either Brawl or Melee
- An issue left over from Brawl that can't be fixed yet.
- A workaround resulting from another bug.
- Known
- In turbo mode
- User Error
If you have custom Content: Make sure what you're submitting IS NOT related to the custom content. Do this by trying to reproduce the bug with a default build.
(If you would like help with customised content. Post in the Help forums or the Custom Content forums. This forum is for reporting and logging bugs in the official build.)
REINSTALL and REPRODUCE
Reinstall the default build and try to recreate the bug again. Problems may occur on your SD card and a fresh install may fix a bug you think you’ve found.
It is important to do this because ANY custom content can inadvertently affect the default build.
THE PMDT only want to spend time fixing their bugs, not bugs caused with custom content.
Even without custom content, SD cards can wear out, things can go wrong. The simple process of reinstalling can potentially fix your problem and avoid unnecessary bug reports.
REPORT
Then if you still need to file a bug report, fill out these Details when you make your post:
Topic Title: PM3.6 | <Text about the bug, use good key words>
In the post:
Title of the bug:
Version found in:
Hardware you are running:
Loading Method:
Details:
Attachments:
Custom Content:
For Example:
Title of the bug: [Something Descriptive about the bug, that if other users find your bug they will find your topic upon searching.]
Version found in: [e.g. 3.5: Homebrew: Full set]
Hardware you are running: [wii, or dolphin version number]
Loading Method: [e.g. USB Loader name and ocarina hook-type , Pm ISO, StageBuilder (hackless will be using this)]
Details: A step By step detailed description on how to reproduce the bug.
If you are unable to reproduce the bug. Please provide as many details as possible so others may try to. If this is the case include ‘INTERMITTENT’ in the topic title until it can be refined.
Attachments: Reproduce the bug using the Wi-Fi/replay build if you can. And attach the replay of the match to your post.
Otherwise try to get some screenshots or record a video with your phone (prop it up with something instead of holding it in your hands to avoid shaking).
Make sure the problem is clearly visible.
Custom Content: This should be 'no'. Not even a little. Not even 'a few songs'. Nothing.
Extra Notes:
- If you are reporting a bug, be committed to help resolve it. At least until it can be pinpointed and reproduced. Please do not post up and wash your hands of the matter. It’s likely that questions will be asked in order to help refine the bug. As the reporter, you will have the most experience in seeing the bug, we need you to help.
- The PMDT are focused on the Wii version of the game. This is not to say that dolphin bugs shouldn’t be reported, but keep in mind that if they’re dolphin only they will likely be assigned a lower priority. Dolphin bugs may still be used to pinpoint bugs in the wii build.
- Keep in mind when using Dolphin that the ‘netplay’ build (which most people use when using dolphin) is actually a custom build and the custom content rules apply to it. That said, still report it if you feel it's a problem as netplay has a big audience. and since it's one custom pack everyone uses, it would be good to find errors. Make sure your report mentions it is on dolphin and the other steps apply (restart pc, reproduce etc)
- Keep bug reports separated into different topics. Otherwise it can be hard to keep track of what's happening in the topic.
- Replays not working is not a bug. DO NOT REPORT THAT YOUR REPLAYS DON'T WORK. The replay function saves button inputs, due to how light presses on shoulder buttons are used and recorded, they de-synch replays. This is known. In order to use the replay function, you need to be saving and viewing replays using the 'wifi safe' build. This is found in the addons menu.
- If your Music is bugging out (Changing tracks, making undesirable noises) you need to delete project m from the Sd card (format it is fine) then reinstall.
If we do this we can help the Dev Team solve issues by providing a thorough analysis of the bugs we find.
They've done so much for us, let’s return the favour and make things easier for them.
Regards,
A Software Tester.
Last edited: