- Blue Box
- EFB Poke: Nintendo Puzzle Collection, BlowOut, Okami
- Sims Censor Effect
- Various issues shared by Phantasy Star Online titles
Heat Effect/Blur: F-Zero GX and Rocket Power: Beach Bandits
- Let's be careful not to go *too* merge happy with problems! For issues that only have two or three entries, I don't really see the need for it. Also, we need to be careful about association! The heat blur issues aren't really related, and I would be opposed to those. But the banding problems are related, since they use the same engine. Let's be careful! - MaJoR (talk) 10:02, 13 December 2015 (CET)
- GBA link working / broken info The_Legend_of_Zelda:_Four_Swords_Adventures#Game_Boy_Player
- Device Connectivity: Skylanders and etc, refer issue 5153
- Mario Galaxy 1/2 shared problems
- Paper Mario shared problems
- Hybrid XFB titles (i.e. need XFB Real for video), and a note regarding why these titles render in low resolution today
- Save-state (i.e. Dolphin save states) break: Resident Evil Archives: Resident Evil, but others as well. This seems like may be more an "ignorable" global problem.
- Region lock details
- In-game screenshots
- Mat Controller
- Banding/Pixelated Shading
- Wii Remote Disconnects
- Video corruption due to Filtering enhancements
- Marvel Super Hero Squad
- Goblin Commander: Unleash the Horde
- The Simpsons Game
- Just Dance (series?, ug, this series needs further review common problems don't seem spread around properly)
- All the VP6 titles
- MySims SkyHeroes
- Manhunt 2
- Epic Mickey (and 2?)
- Remove 4:3 Borders
- Dual Core Crashes/Issues
- These really need closer investigation generally. There are now additional GameINI settings that may improve some Dual Core issues.
- issue 7143
Naming Convention
I think I was in programming mode when I set this up initially without spaces in the titles. I'm guessing there is no good reason to handle them that way. Should these be revised to include spaces, and otherwise extend them, to make them them easier to identify?
Noting Additional Data
Various shared problems have additional data tacked on to the end of statements (screenshots, particulars of the issue for that title). I think we may want to handle that differently so we can be aware of such content when these issues need to be cleaned up. Some strategies:
- Just ignore it, always remember to postfix something like ".*?(?=== )" to the ends of search 'n replaces used to clean these up (i.e. followed by "== "). (My regex syntax may be off there). Though something a bit more complicated would be needed to account for shared problems following one another.
- Add notes regarding the post-fixed content on each shared problems documentation page, and be careful cleaning shared problems with such text. We probably should have some standard documentation of it in any case.
- Pull the content into the shared problem in some pay (i.e. provide additional parameters). Though this probably makes the clean-up steps equally hard as with the "ignore it bullet", so perhaps not a good solution.
Please chime in with opinions/other ides.