Template talk:Problems/GC Widescreen Auto

DLP Problem
So I had been trying out the new DLP extension here to pull in a list of pages using this template. Something seems to be going wrong though as it lists things like "Ice Age 2: The Meltdown", which is just a disambig page. Though it seemed simple enough, maybe my syntax is off somehow. It's strange in any case. Kolano (talk) 22:24, 23 November 2015 (CET)


 * I was able to add some additional rules to filter out the disambig and Wii titles pulled in through disambig. Still need to work out how to prevent the tracing through disambig, since other page lists may not be able to as simply filter those pages out (i.e. any that includes both GC and Wii titles). Kolano (talk) 08:36, 28 November 2015 (CET)

Template split
Hadn't time to look into detail before but *why* this template got splitted into two? From the recent discussions it seems that for some games (like King Arthur) the built-in AR switch doesn't work, I got it, but why not edit template logic to conditionally change the text from "Auto" to "Force" if an additional parameter is given? That's waay cleaner than creating an almost identical duplicate to handle this (it's what config and testing does to handle channels, for example). I'm completely against having this template split when an super simple addition would achieve the same, I almost reverted it without asking but I think you may have a good reason to do so? - Jhonn (talk) 05:08, 24 November 2015 (CET)


 * It was split for the reason you indicated, the problem text was wrong for a series of titles that instead of "Auto" need to be set to "Force 16:9". Having two templates seemed simpler to me than adding parameters and logic. There are likely to be a few more of these sorts of Problems templates, it seemed like it could get confusing for each to have various sets of parameters. Kolano (talk) 08:05, 24 November 2015 (CET)


 * The only two options that can affect native widescreen are "Auto" and "Force 16:9" so we won't need to deal with lots of parameters and right now only two possible games needing "Force 16:9" surfaced, which makes the second template even more redundant. Also, if Dolphin changes something in its settings we would have to modify more templates to account that (not a big deal, but it's more things to keep track). If that's the only reason I'm gonna to merge them back and do something similar to config and testing, the logic is veeery simple (a simple  does the trick) and it defaults to the most used one, so in this case it would be   for the majority of the titles and   for the two exceptions currently known. - Jhonn (talk) 17:37, 24 November 2015 (CET)


 * The one other benefit is being able to get separate lists of the relevant titles. We only generate a single Native Widescreen Support category, so if we don't use different templates there seems to be no easy way to get separate lists.
 * There are only those two cases for WidescreenGCN, but there will be other non-widescreen related Problems templates. It seems like the eventual list of them would be clearer if each didn't have various custom parameters.
 * Someone still needs to review all the other titles we list under Problems/WidescreenGCNAuto‎, I have a feeling there will be other titles that are also not compatible with Auto AR.
 * Kolano (talk) 19:45, 24 November 2015 (CET)


 * Meh, I'm still not a fan of duplicated templates but you have a good point, keeping the duplicates for now but if I find a way to still get the separate listings without needing a duplicate (or more categories) expect me merging them back into a single one... - Jhonn (talk) 03:26, 25 November 2015 (CET)

Auto vs Forced Review
The titles tagged by this template need review to confirm they are compatible with Dolphin's Auto AR setting, and incompatible titles migrated to the Problems/WidescreenGCN16-9 template. Please remove titles from the list below as they are reviewed so we can track progress on this. Kolano (talk) 08:30, 28 November 2015 (CET)


 * 007: Everything or Nothing
 * 007: Nightfire
 * Batman Begins
 * Battalion Wars
 * Buffy the Vampire Slayer: Chaos Bleeds
 * Burnout
 * Burnout 2: Point of Impact
 * Call of Duty 2: Big Red One
 * Dead to Rights
 * Die Hard Vendetta
 * Disney's Extreme Skate Adventure
 * Dragon's Lair 3D: Return to the Lair
 * Drome Racers
 * Eternal Darkness: Sanity's Requiem
 * F-Zero GX
 * Freedom Fighters
 * Future Tactics: The Uprising
 * Geist
 * GoldenEye: Rogue Agent
 * Gun
 * I-Ninja
 * Ice Age 2: The Meltdown (GC)
 * Judge Dredd: Dredd vs. Death
 * Lego Star Wars II: The Original Trilogy
 * Madden NFL 07 (GC)
 * Madden NFL 08 (GC)
 * Madden NFL 2002
 * Madden NFL 2004
 * Madden NFL 2005
 * NASCAR: Dirt to Daytona
 * NASCAR 2005: Chase for the Cup
 * NASCAR Thunder 2003
 * NBA 2K3
 * NCAA Football 2003
 * NCAA Football 2005
 * NFL 2K3
 * NFL Street
 * Need for Speed: Carbon (GC)
 * Need for Speed: Most Wanted
 * Need for Speed: Underground 2
 * Pac-Man World Rally
 * R: Racing Evolution
 * Rayman 3: Hoodlum Havoc
 * Robotech: Battlecry
 * SSX 3
 * SSX Tricky
 * Soulcalibur II
 * Sphinx and the Cursed Mummy
 * Spyro: Enter the Dragonfly
 * Star Fox Adventures
 * Star Wars: The Clone Wars
 * Super Mario Strikers
 * Super Monkey Ball 2
 * Super Monkey Ball Adventure
 * Superman: Shadow of Apokolips
 * TMNT: Mutant Melee
 * The Incredible Hulk: Ultimate Destruction
 * The Legend of Spyro: A New Beginning
 * TimeSplitters: Future Perfect
 * Tom Clancy's Splinter Cell: Chaos Theory
 * Tony Hawk's Pro Skater 4
 * Tony Hawk's Underground
 * Tony Hawk's Underground 2
 * True Crime: New York City
 * True Crime: Streets of LA
 * Wallace & Gromit in Project Zoo

FOV
There might be two more possibilities in the widescreen setting we want a parameter for it. It's whether the widescreen setting impacts the field of view. But first I'd like to find a game with Problems/WidescreenGCNAuto that does that them we'll implement a such thing. Assuming there is, what's a good parameter name? Something with "|NoFoV" for example... Lucario (talk) 04:34, 28 November 2015 (CET)


 * OK, let's work through reviewing for Auto support first and see if so we can identify relevant titles. There may need to be more complex handling, as some titles might provide multiple options for this (i.e. both a FOV effecting and non-effecting setting). Kolano (talk) 08:34, 28 November 2015 (CET)