A New Era Arrives
Dolphin has had its first release in eight years! Read more about it on our blog: Dolphin Releases Announcement. |
The Dolphin Emulator Wiki needs your help! Dolphin can play thousands of games, and changes are happening all the time. Help us keep up! Join in and help us make this the best resource for Dolphin. |
Template talk:Problems
Bug
There seems to be a bug with the new Problems template when an problem has an "=" character it causes all indicated problems to be ignored and the "no problems" statement be displayed. This is most frequently seen with External links that use parameters, refer Homebrew Channel. Kolano (talk) 19:18, 3 December 2016 (CET)
- I added an equals template {{=}} to work around the problem, unclear if there is any better way of handling it. Kolano (talk) 01:16, 4 December 2016 (CET)
- Also unclear if there is any current way to search for/flag problems effected by this. Problems with external links, and some settings references (i.e. XFB=Real), are likely candidates to cause problems. The old search-n-replace had allowed for regex searches, but I think we lost that with the newly implemented one (I've forgotten the details). Kolano (talk) 03:31, 4 December 2016 (CET)
- Okay, the issue is trickier than I though. I double checked all RegExp queries and they all are working as intended, the issue here is the parameter's parsing. Basically, by having a = in those cases is making the problems "text" being passed as an argument different than {{{1}}}, so, the problems never get into the template logic (since it checks for {{{1}}}, and when the bug is triggered, {{{1}}} is empty). The strange part is that the various === from the headings doesn't trigger this bug, yet a forum link like the one from Homebrew Channel does. I'll see if I can do something to somehow prevent that, but at the moment there's no fix other than the workaround you provided... - mbc07 (talk) 05:06, 4 December 2016 (CET)
- Sure, I'll see what can I do - mbc07 (talk) 17:27, 4 December 2016 (CET)
- Take a look at the recent edit I made in Homebrew Channel. It avoids the issue completely, although it also makes template usage a bit more "messy". What do you think? - mbc07 (talk) 17:46, 4 December 2016 (CET)
- Not sure. I guess it's not too bad once we'd use the search-n-replace to populate it everywhere so users wouldn't have to remember, but it is a bit ugly. I guess that logic has to exist outside the template itself? It's certainly preferable to having users needing to remember to escape any equals characters though, so I'm supportive either way. Kolano (talk) 20:43, 4 December 2016 (CET)
- Yes, it must be outside of the template. It's basically assigning a variable with the text before passing it to the template, and it avoids the issue because = has no special meaning when defining a variable. The content of the variable is then "echoed" into the template parameter {{{1}}}, avoiding it wrongly recognizing = as a definition of a specific parameter. Another possible approach is using {{#vardefine:problems| <problems text here> }}{{Problems}} then refactoring {{Problems}} to work directly on that variable instead of the {{{1}}} parameter, but it still looks a bit messy. What do you think, does it look better? - mbc07 (talk) 01:55, 5 December 2016 (CET)
- Not sure. I guess it's not too bad once we'd use the search-n-replace to populate it everywhere so users wouldn't have to remember, but it is a bit ugly. I guess that logic has to exist outside the template itself? It's certainly preferable to having users needing to remember to escape any equals characters though, so I'm supportive either way. Kolano (talk) 20:43, 4 December 2016 (CET)
Template Request
- WiiConnect24 / RiiConnect24
- Online service retirement
- EFB Poke: Nintendo Puzzle Collection, BlowOut, Okami
- GBA link working / broken info:
- The_Legend_of_Zelda:_Four_Swords_Adventures#Game_Boy_Player
- Pokémon XD: Gale of Darkness
- Category:Game Boy Advance (Input supported)
- Per JMC: I was looking for MayImilae earlier, and she told me she was busy, but, I think it's about time the GBA <-> GCN notes got updated to the new behavior? Namely, it's missing on a bunch of games, and on Four Swords it is so incorrect that it makes me barf. Here are a few pointers: There are possible audio issues when using HLE; it bugs out on ucode swapping. Only one GBA will connect on HLE audio. Pokemon games don't work afaict, but others have gotten them to work. I can't.
- Device Connectivity: Skylanders and etc, refer issue 5153
- Mii Faces: It seems there may be multiple issues here, most titles corrected with EFB2RAM, but some needing Dual Core disabled.
- 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.
- In-game screenshots requiring EFB to RAM
- 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)
I have all games from the main series and some spin offs and from personal experience we can safely split them between first gen (Just Dance 1/2/3/4, ABBA You Can Dance, Michael Jackson The Experience) and second gen (Just Dance 2014/2015/2016 and onwards). All first gen titles have video corruption issues due to filtering enhancements. Second gen titles doesn't suffer from filtering issues but works only with wiispeak branch (or Ishiiruka) and requires EFB2RAM to properly display characters in many songs. Just Dance Wii and Just Dance Wii 2 are also first gen titles (based on Just Dance 2/Just Dance 3, respectively), can't say anything about Just Dance Kids or other spin offs like Dance on Broadway...- After 5.0 stable and recent builds, everything is fixed on the newer Just Dance games. The only common problem is probably worth creating a template is for the Filtering issue on Just Dance 1/2/3/4 (but I suspect it might be already fixed in a PR opened recently which improves EFB2RAM Copy downscaling filter -- haven't tested it, though) - mbc07 (talk) 19:33, 7 September 2016 (CEST)
- Remove 4:3 Borders
- {{Problems}} should focus on problems not enhancements. I doubt we'd want the enhancement counterpart either. Lucario (talk) 02:59, 26 December 2015 (CET)
- I'm pretty sure we would, titles with Filtering scrambling videos would be a good example case. At the same time I'm not very supportive of covering this particular issue the way we do. It's about distorting titles not intended to run at 4:3, not via an AR code or other means that would do so properly, but by stretching/skewing the rendered image or cutting off portions of the display, which I don't consider an "enhancement" at all. Kolano (talk) 08:02, 26 December 2015 (CET)
- 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
- Sonic Adventure 2: Battle
- Baroque
- Baten Kaitos: Eternal Wings and the Lost Ocean
- Boom Blox Bash Party
- Castlevania: The Adventure ReBirth
- Contra ReBirth
- Diner Dash
- F-Zero GX
- Harry Potter and The Half-Blood Prince
- Hasbro Family Game Night
- Hasbro Family Game Night 2
- Paper Mario
- Peach's Castle
- Rapala's Fishing Frenzy
- SSX Tricky
- Skies of Arcadia Legends
- Super Monkey Ball 2
- WTA Tour Tennis
- Zatch Bell! Mamodo Fury
- {{Problems/Emulated Wii Remote Position Toggle}}
- Sonic and the Secret Rings
- Pretty confident that this also applies to Mario Party 8 and 9
- May merge games with "Sideways Remote required for Emulated Wii Remote" into this list also?
- Wii Speaker Data off
- For all Wii Balance Board titles, as it causes BB disconnects. May need clarity if titles don't use speaker data (or if the disconnects occur when playing audio over an emulated Wii Remote).
- {{Problems/Analog Stick Range}}
- Unlimited VPS
- Need for Speed: ProStreet
- Excite Truck
- Excitebike
- other NFS titles
- TMEM Emulation FMV Failures
- Refer issue 11164
- Aspect Ratio (Dolphin's AR detection bugs out in some titles)
- Blue Box
- Sims Censor Effect
- Phantasy Star Online titles shared problems
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! - MayImilae (talk) 10:02, 13 December 2015 (CET)
- Mario Galaxy 1/2 shared problems
- Paper Mario shared problems
- Shadow Z-fighting
- Distorted/Missing Shadows (LogicOps support)
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 way (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 ideas. Kolano (talk) 22:14, 17 December 2015 (CET)
Just a thought, it'd not be ideal to create {{Problems}} for very specific things. Using a comment tag like <!-- possible shared problem: [[game title]] --> into each article source will do a better job telling editors that there is game with shared problem and should be updated accordingly, or not. Shared problem with different culprit is always a possibility. And thus using {{Problems}} templates will be more of a burden.
Using commented tags instead will also preserve unique sentences. We won't have to worry trying to merge different sentences across games with shared problems.
This will finally purge out "Mario Galaxy 1/2 shared problems", "Paper Mario shared problems", etc. and other shared problems with unsure culprit ("Heat Effect/Blur: F-Zero GX and Rocket Power: Beach Bandits" where MayImilae suggested not to merge) from above. Lucario (talk) 20:45, 31 October 2016 (CET)
Template for Upscaled Bloom Problems
Given the number of games with upscaled Bloom problems, it would make sense to have a template for ease of tracking. If agreeable I could create one and start applying them to games I know have the issue and from the Dolphin bug tracker. Gordonfreeman01 (talk) 14:08, 11 January 2022 (CET)
- This would be great. Please keep in mind there is likely some variability needed for indicated solutions, and it's preferable to not have multiple templates if it can be avoided. So some care will be needed with phrasing, and room left to provide per title specifics. Kolano (talk) 04:39, 12 January 2022 (CET)
Purging Fixed Problems
Now that Dolphin 2407 has been released, quite a few problem templates can be purged. But since that is more invasive than a normal edit, I was wondering how purging would impact edit history since I can image it is nice to keep that accessible. Otherwise, the problems can be removed game side and the game templates can be marked with a strikethrough to mark them as fixed. Thoughts? - Miksel12 (talk) 16:39, 2 July 2024 (CET)
- The purge isn't finished yet, the first pass I did yesterday specifically didn't touch any of the shared problems templates. The plan is to keep the templates (maybe move them somewhere else and add a category to flag pages still including them) and purge only the call from the game pages. There's also some templates that aren't fully updated yet for the new releases numbering (e.g. {{VersionRevision}} and others including it), which I plan finishing in the next days. Releases will be more frequent from now on, so I'm also taking some time to ensure everything works and to document the release process, so it can be done more quickly when future releases arrive... - mbc07 (talk) 01:33, 3 July 2024 (CEST)
- Yeah, generally agreed with mbc07. Will be good to shuffle way prior resolved issues.
- But given the more frequent releases we may need to revise the rules around how we update things since preserving some history across more than just the prior release will likely be important. We'll probably need a better feel for the release cadence to work that out though. Thanks for taking a stab at handling this mdc07, definitely appreciated. And thanks for taking interest to help Mikse112, here's the list of pages with "fixed" problems that likely still need clean up: https://wiki.dolphin-emu.org/index.php?title=Category:Pages_with_fixed_problems
- @mbc07, I think some of your recent version revisions have made this category go wild, so probably some revision needed for that: https://wiki.dolphin-emu.org/index.php?title=Category:Pages_calling_VersionRevision_template_with_SVN_build_numbers_without_a_leading_R
- Everything being flagged in Category:Pages calling VersionRevision template with SVN build numbers without a leading R right now is expected, I'll delete this category once everything is ready. I temporarily added it so I could easily flag pages which still had SVN era revisions, and used that to mass edit them with a leading r (to not conflict with the new release format, which is NNNN for releases, NNNN-NNN for dev versions and NNNNL for hotfixes). That part was done a little before the announcement, however, I haven't updated {{VersionRevision}} to understand the new release format yet (current plan is to finish it by the weekend), so right now it thinks anything following the new release format is SVN, and since {{CurrentGitRevision}} is now using the new format too (which is included in the {{VersionCompatibility}} template, present in every game page), basically everything got tagged in that category... - mbc07 (talk) 10:21, 4 July 2024 (CEST)