79,227
edits
 |
Progress Continues
We've already had 21555 updates since Dolphin 5.0. Keep up with Dolphin's continuing progress through the Dolphin Blog: February, March, and April 2024 Dolphin Progress Report. |
 |
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:Gecko: Difference between revisions
Jump to navigation
Jump to search
→Regions
No edit summary |
|||
| Line 29: | Line 29: | ||
::Well, I'm not used to GameID as header of the code table. Maybe I'm just too used to the likes of "NTSC" and "PAL". I think those disc revision could be merged into NTSC column as part of title of the code. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 00:09, 4 January 2018 (CET) | ::Well, I'm not used to GameID as header of the code table. Maybe I'm just too used to the likes of "NTSC" and "PAL". I think those disc revision could be merged into NTSC column as part of title of the code. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 00:09, 4 January 2018 (CET) | ||
::: OK, how about the Korean releases then? Should we presume the can merge under NTSC-J? [[Pokémon Snap]] is probably a good example. It has 7 different releases /w 3 PAL ones and requires a 16:9 Aspect Ratio Fix. There is currently only one code for the NAKE01 GameID. | |||
:: Something else positive that can likely come out of using the GameIDs would be the ability to tell when additional investigation / codes are needed (i.e. there are 6 missing codes for [[Pokémon Snap]]. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 02:10, 4 January 2018 (CET) | |||
== Quality Categories == | == Quality Categories == | ||
If you want to turn gecko codes into a template (not a bad idea), it might be good if you're going to try and integrate quality checks to hook it into [[Template:Problems/GC Widescreen Auto]] and [[Template:Problems/GC Widescreen 16-9]]. If the game supports 16:9 already but also has widescreen codes for whatever reason, then the template should generate flags to show that the widescreen gecko codes aren't needed. That would give the template tangible benefits rather than just style compared to the current way of doing it. I don't know how to handle that with Wii though, but I don't really know how widespread the creation/desire for widescreen Wii codes is when most games already support it (I think?). - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 04:17, 30 December 2017 (CET) | If you want to turn gecko codes into a template (not a bad idea), it might be good if you're going to try and integrate quality checks to hook it into [[Template:Problems/GC Widescreen Auto]] and [[Template:Problems/GC Widescreen 16-9]]. If the game supports 16:9 already but also has widescreen codes for whatever reason, then the template should generate flags to show that the widescreen gecko codes aren't needed. That would give the template tangible benefits rather than just style compared to the current way of doing it. I don't know how to handle that with Wii though, but I don't really know how widespread the creation/desire for widescreen Wii codes is when most games already support it (I think?). - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 04:17, 30 December 2017 (CET) | ||
:Good idea, if this new template is going to make it to game pages then we can add additional qualility checks regarding games that already support widescreen. We may like another category for whether it's used in Wii game pages. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 03:29, 31 December 2017 (CET) | :Good idea, if this new template is going to make it to game pages then we can add additional qualility checks regarding games that already support widescreen. We may like another category for whether it's used in Wii game pages. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 03:29, 31 December 2017 (CET) | ||