Emulator Issues #3915
closed
Progressive scan on GC games
0%
Description
What's the problem?
When launching a gamecube game that supports progressive scan (like fzero, mario golf, etc), holding [B] during boot doesn't prompt the "enable progressive scan?" dialog anymore. And sometimes when doing this, I'll get a green screen and if I keep holding it, the screen will changes colors but never display the game until I release it.
Dolphin version with the problem (as it appears in the title bar, Ex.: "R
4779" or "R 6403M"):
r6837
(optional) Dolphin version that does not have the problem:
Not sure. This used to work on previous revisions.
Operating system and version:
Win 7 x64
32-bit or 64-bit:
x64
Note:
This occurs whether the "enable progressive scan" option is on/off in the dolphin display config.
Updated by wespipes69 over 14 years ago
It works perfect in r6005 - this is definetely broke and leading to some gfx issues. I get blue grass in Mario Golf now and it's 100% because of the progressive scan setting in my save file - which I can't turn off currently. Maybe I'll load it in a old revision and turn it off...that should work. On or off, I shouldn't be getting blue grass which makes me think the game is in some pseudo progressive scan state or simply progressive scan just causes gfx issues on new revisions.
Anyway, I know r6005 was a while ago. Let me know if you REALLY need me to track this down. :)
Updated by skidau over 14 years ago
- Status changed from New to New
Seems to work for Mario Kart: Double Dash and Eternal Darkness. Are you sure Mario Golf and F-Zero GX have those screens? Do you have a screen-shot of the progressive scan question screen from Mario Golf in r6005?
Updated by hatarumoroboshi over 14 years ago
It works with Star Fox Adventures PAL (r6854 - Jit 32-bit)...pressing B-button at start shows the usual 50-60hz configuration screen.
Updated by wespipes69 over 14 years ago
Alright after 2 frustrating hours I figured out what is going on here. Sorry Skid, but you broke this with r6297 (as I suspected).
Before that commit:
All GC games can have progressive scan enabled properly - the "progressive scan" option has no effect.
After that commit:
To enable progressive scan, the option MUST be enabled AND not all games can enable it. Games like Fzero, Mario Kart, Eternal Darkness, Star Fox can enable it fine. BUT Mario Golf, Mario Tennis (which always have the same issues) and probably other games cannot enable it at all - no workaround.
Here's the pic for proof Skid:
http://img543.imageshack.us/i/17731050.png/
Updated by skidau over 14 years ago
Are you sure it was r6297? The code for this area looks the same before and after (as long as the option has been ticked). I think the above screenshot was taken using the NTSC-U version? Is it possible to test r6296 and r6297 with the PAL version?
Updated by wespipes69 over 14 years ago
Weird. Well I can garauntee it was one of 3 builds. It could be I guess r6296 or maybe r6298 (but that's just an extention from what you did on r6297).
All I know for certain is downloading r6295, unpacking, using 100% defaults,launching Mario Golf/Tennis while holding B, causes the Progressive Scan option to appear. Doing the same in r6298 never shows the screen, it just acts like I'm not holding B and continue through the legal screens. So it was either r6296, r6297, r6298 - Mamario doesn't have builds in between.
And again, the "Progressive scan" option also became required in one of those builds for progressive scan to even work in some games - before that it did not matter at all (for GC games at least).
My game is the NTSC-U version, so someone else will have to check out the Pal thing.
Let me know if there's anything more I can do on this one.
Updated by wespipes69 over 14 years ago
Alright, well in r6892 it seems to be working fine now. If the option is enabled, Mario Golf/Tennis automatically pop up the progressive scan confirmation. Not sure if code changes or setting changes fixed this...but something is different now and it works as you would expect.
I'd say go ahead and close this and if I discover anything else about this, I'll open a new bug.