Closed GoogleCodeExporter closed 9 years ago
Doesn't the same thing happen in the main menu (when the currently played game
is displayed in background ?). This should be quite easily fixable though I'm
wondering why people are using the 16:9 correction option. Isn't your 16:9 TV
able to display 4:32 video signal ? Because the result is WAY BETTER this way
than messing with the original genesis aspect ratio to take 16:9 upscale in
account.
Original comment by ekeeke31@gmail.com
on 13 Jun 2010 at 5:03
This doesn't happen when you switch into the emulator menu. However, the
screen cap shifts/bounces a few pixels when switching to the from the emulator
menu which is kind of distracting but a pretty minor issue. I wonder if it has
to do with the new menu how being animated when it appears and disappears. Try
just taping the Home button on the wiimote to switch the menu on and off.
Maybe it only does when the video option is set to 16:9. I'll have to
experiment with the 4:3 option some more.
Original comment by achan...@gmail.com
on 14 Jun 2010 at 10:53
No, it has to do with the fact the Wii video width is changing (when Menu &
In-game emulation does not use same video modes), similar happen when playing a
PAL games (which switch the Wii video to 50hz) and returning to menu (60hz),
nothing much I really can do against that and I don't think it's that much
distracting the way it's actually done (it used to be worst).
About your issue, if your TV can handle it (most TV I know can switch to 4:3
and automatically center the image with black bars), I definitively encourage
you to stay with 4:3 original aspect ratio because:
1/ it's the original aspect of the rendered (genesis) display (i.e if you
hooked the real console on your 16:9 TV it would look just as stretched)
2/ it does not require additional stretching/filtering that usually deteriores
the original image, giving you the best raw image as possible.
Will look at this issue though since it's supposed to be handled like when you
switch into the emulator menu...
Original comment by ekeeke31@gmail.com
on 14 Jun 2010 at 11:26
Fixed in r462
Original comment by ekeeke31@gmail.com
on 15 Jun 2010 at 6:52
Original issue reported on code.google.com by
achan...@gmail.com
on 13 Jun 2010 at 2:57