Emulator Issues #5101
closedGames run with top half distorted when progressive scan is enabled, workaround known
0%
Description
- Game Name and ID (as it appears in right click > properties: "GZ2P01",
"RSBE01", etc): GFEE01, RFEE01, probably more, not tested
2) What is the expected output? What do you see instead?
Expected:
Launch game with progressive scan enabled, play game.
Instead:
Launch game with progressive scan enabled, see top half of screen look like attached file, set internal resolution to 1.5x or higher, game returns to normal, set internal resolution back to window size, play game.
3) Did the game ever work correctly (i.e. not have this problem) on an
earlier version of dolphin? Please specify the exact revision when the
problem began.
Not sure when this started
4) What steps will reproduce the problem?
- Enable progressive scan
- Try to play a game (tested with two above, I think it probably happens with just any game, though)
- While the emulation is running, set the internal resolution to 1.5x or higher. This returns the game to normal.
5) What version of dolphin are you using (32bit/64bit along with the
version as it appears in the title bar, etc)?
On what operating system, drivers, and hardware? Be sure to list OS,
graphics driver information, and video card model if you are having
graphics problems, for example.
OSX 10.7, Dolphin x64 3.0-235, MacBook aluminum unibody 13", 4GB RAM
6) Please provide any additional information below.
Doesn't happen every time. Every once in a while, it'll start up fine without the workaround; I don't know of a particular trigger for it.
7) Attachments. IMPORTANT! We have a limited storage quota on
GoogleCode, so please use a 3rd party host for screenshots or any other
files (http://min.us/ for example).
http://imgur.com/DzmPW
Updated by vlakipn almost 13 years ago
That happens to me too , sometimes, even without progressive scan.
Updated by Billiard26 almost 12 years ago
- Issue type set to Bug
- Category set to gfx
Updated by skidau over 11 years ago
- Status changed from New to Fixed
This seems to be fixed as I cannot reproduce the problem anymore. Tested on 3.5-600.