Closed GoogleCodeExporter closed 9 years ago
Indeed, it originally cames from here (Issue8), we assumed component cable
presence was enough to say progressive mode is supported but it is obviously
not always the case. I will add an option to let users configure menu video
mode if component cable is found, rather than relying on a key press (lot of
users don't bother reading user manual).
For the record, on PAL gamecube, we can't output 480p and B button is generally
used to switch from 576i (50hz) to 480i (60hz).
Original comment by ekeeke31@gmail.com
on 11 Mar 2012 at 9:06
Well, after re-reading the original issue (Issue8), this won't work with
monitors that only support progressive mode so we are stuck to non-visible key
press solution. I guess it would be more practical to save the default mode in
config file and have it switched between 480p and 480i anytime B is held on
startup...
Original comment by ekeeke31@gmail.com
on 11 Mar 2012 at 9:12
Sorry I should have specified, this is on an NTSC gamecube.
My brute force workaround has been to re-compile with the 'force 480p' section
commented out. Looking forward to a more elegant solution, thanks!
Original comment by dustin...@gmail.com
on 11 Mar 2012 at 11:07
added in r670
since i cannot test on my gamecube anymore (seems like my sdgecko adapter got
trashed), please tell me if it works as expected
Original comment by ekeeke31@gmail.com
on 7 Apr 2012 at 5:19
I have compiled the latest code (r673) and tested on my gamecube. The program
now loads in 480i mode by default. If I hold the B button at startup, it plays
the Sonic ring sound at the legal screen and switches to 480p mode, then goes
to the menu. From here I can (semi-blindly) exit the program like normal and
re-load, and it once again defaults to 480i mode.
It does not seem to be storing the setting like you expected. Instead the B
button has to be held each time you want 480p enabled, rather than acting as a
toggle. This actually makes more sense to me as this is how commercial games
behave.
Interestingly, if you hold the B button at startup without a component cable
plugged in it will still play the ring sound, but stays in 480i mode.
Thanks for the fix!
Original comment by dustin...@gmail.com
on 9 Apr 2012 at 4:16
Thanks for the report.
The setting was not restored properly, it should be fixed in r675. 480p should
also now the default when component is detected, as before.
You can still switch the setting when no component cable is connected, hence
why you can still hear the ring sound, though video mode won't be changed.
Original comment by ekeeke31@gmail.com
on 9 Apr 2012 at 9:36
I've compiled and tested r676, I can confirm that the setting is now being
retained and 480p is the default on first run.
Some notes:
- Holding B at startup doesn't toggle the video mode, instead you have to press
B while the legal screen is displayed.
- Upon switching from 480p to 480i at startup the main menu seems to have the
flicker filter disabled. After loading a game and exiting back to the menu,
the flicker filter is back to normal.
Original comment by dustin...@gmail.com
on 10 Apr 2012 at 2:33
I revamped stuff a little bit, key registration is now done just after
configuration load, then video mode is eventually switched to 480p at the same
time, before anything, including disclaimer, has been displayed.
This is still blind coding so tell me how it works for you...
Original comment by ekeeke31@gmail.com
on 10 Apr 2012 at 7:07
The latest r677 is working near perfect. Holding B at startup makes the video
mode switch before showing the legal screen, and the setting is retained next
time.
The only bug is with the ring sound. When switching from 480p to 480i the
sound does not play at first, but then plays when you press the A button at the
legal screen. When switching from 480i to 480p the ring sound starts to play,
cuts off as the legal screen comes up, then finishes playing when you press the
A button to continue. In either case, the regular sound when you press A never
plays.
Original comment by dustin...@gmail.com
on 11 Apr 2012 at 9:00
Original comment by ekeeke31@gmail.com
on 16 Jun 2013 at 11:34
Original issue reported on code.google.com by
dustin...@gmail.com
on 11 Mar 2012 at 2:26