Emulator Issues #12254
Widescreen Heuristic Mega-Issue
Metal Arms: Glitch in the System
Yugioh Falsebound Kingdom
Need for Speed Most Wanted
Metroid Prime 2
Likely Others to be added.
What's the problem? Describe what went wrong.
While playing these games, either they will get stuck in the wrong aspect ratio when using "auto" or they will jump between aspect ratios erratically.
What steps will reproduce the problem?
I will link the individual issues, but most of them will happen right away while a few others are specific to various actions. For instance, Metroid Prime 2's issues only occur when certain effects are on screen, like dust from a enemy coming out of the ground.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
The issue is present in 5.0-12581
Is the issue present in the latest stable version?
Some are, some aren't as the heuristic has changed many times since 5.0.
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
We'll probably be moving/attaching fifologs/screenshots as games are added to this issue.
#7 Updated by JosJuice over 1 year ago
You can get Dolphin to incorrectly think Pokémon XD is 16:9 by moving around in the first overworld room. I've attached a FIFO log which contains both a segment detected as 16:9 and a segment detected as 4:3. Tested in 5.0-12579.
#8 Updated by ryanebola16 over 1 year ago
Copying this here in case it's related. Originally posted in #7143:
Super Monkey Ball (GMBE8P) Advanced Stage 10 seems to randomly stretch the screen then quickly return it to the proper size (widescreen mode detection issue?) on 5.0-12369. Dual core only, single core does not have this problem. Let me know if I should file a separate issue for this.
#10 Updated by Billiard26 over 1 year ago
Copying my comment from #12090:
I believe the widescreen heuristic is not fixable without adding per-game settings.
Metal Arms NON-widescreen aspect ratio is 1.25.
F-Zero's widescreen aspect ratio is 1.244.
Certain games have an unusual idea of what "widescreen" is so we can't fix them all with one magic number.
Killer 7 is also affected, during one of the first cutscenes the game will switch to widescreen and stay like this (haven't tested long enough to see if it switches back to 4:3 at some point).
To reproduce: start a new game, skip cutscene, say "No" for the controls tutorial, when in-game hold A until you trigger the next cutscene and skip it, another cutscene will follow directly, don't skip this one, that's the one that triggers the widescreen.
Wave Race too, it can flicker like crazy, it seems to be only on specific parts of the course, easiest way to reproduce (warning if you're sensitive to quick flashes, the flickering is pretty bad!): select "Free Roam" then the 3rd track (Southen Island) and just start driving, the flicker should happen very quickly.
#24 Updated by THAWwidebug 6 months ago
Tony Hawk's American Wasteland (GWJE52) is also affected. I am using the latest Platpak build avaible, 5.0-15445, and the hash of the game is OK.
No configuration settings were altered before starting the game.
A video showing the error can be found here:
By starting the game with the aspect ratio set to "Force 4:3" there will be no errors whatsoever. However, if the game is started with it set to "Automatic" and then changed to "Force 4:3" once the memory card starts being read, there will be a flickering glitch effect on the screen:
The same also happens if "Force 16:9" is chosen:
I could not determine whether this error is exclusive to Dolphin installed through Platpak or not as the wiki page for the game doesn't mention anything about this glitch, but F-Zero GX runs fine and the widescreen toggle works perfectly.
I could not save the FIFOlog I recorded, it gave me an error when saving for some reason.
I could not determine whether this error is exclusive to Dolphin installed through Platpak or not
Hey! The random flickering in "Auto" happens to me on Windows 10 as well. I wasn't able to reproduce when a "Force" mode is used however.
Just like Wave Race, the random flickering is impossible to capture, as soon as you press "Record" it stops doing it. However widescreen also triggers when changing menus, I was able to capture this one. I've recorded 30 frames tho, as I had to press "Record", then switch to the game window and press a button to trigger the glitch...
2 FIFO records from Pokemon Colosseum:
-pokemon_colosseum_10f.dff: recorded 10 frames, when I play it I can only see the 4:3 -> 16:9 on the first loop, then it stays in widescreen.
-pokemon_colosseum_60f.dff: recorded 60 frames, this one is much bigger but you can clearly see the AR switch on every loop at least.