Closed GoogleCodeExporter closed 9 years ago
Original comment by dborth@gmail.com
on 25 Jul 2009 at 5:29
That's really weird, I updated my WII system menu to 4.1, updated to FCEUGC
3.0.7 and
was impressed that the turbo didn't crap out a few minutes into it like it
usually
does. I played through bubble man, metal man and flash man before quitting. One
thing that I have noticed about turbo is that the speed may be set a little
fast. It
works for a few seconds in Double Dragon III and then it's like turbo is off.
This
has always happened for me, and happens in every nes emu on PC as far as I have
tested. I should note that today I was using a WiiMote with turbo B mapped to
1. It
worked fine for me, input in general is flat out awesome now!
Original comment by aroun...@adelphia.net
on 26 Jul 2009 at 4:33
Heh, must be the gamecube controller only then?
Original comment by RiSho...@gmail.com
on 26 Jul 2009 at 6:17
No turbo doesn't work for me either :(
It's something introduced by the new core that I still have to track down.
Original comment by dborth@gmail.com
on 26 Jul 2009 at 6:20
Issue 157 has been merged into this issue.
Original comment by dborth@gmail.com
on 26 Jul 2009 at 5:04
with classic controller the turbo works fine, must happen only with nukchuc
Original comment by albaques...@gmail.com
on 27 Jul 2009 at 2:30
No, it was crashing for me with the classic controller. I guess it only crashes
under certain circumstances. The good news is that I'm able to duplicate those
circumstances.
Original comment by dborth@gmail.com
on 27 Jul 2009 at 3:02
Original comment by dborth@gmail.com
on 28 Jul 2009 at 5:09
With Classic Controller the game will crash, when I using the turbo button.
Videomode is PAL.
Original comment by markus.f...@online.de
on 30 Jul 2009 at 9:59
I have the same issue, Issue appeared in multiple games, although in my case the
screen goes all green and I have to hard reset my wii...
Original comment by Brainy...@gmail.com
on 30 Jul 2009 at 5:23
What part of "Fixed" don't you understand? That means I've already fixed this,
you'll see the fix in the next version.
Original comment by dborth@gmail.com
on 30 Jul 2009 at 5:32
Original comment by dborth@gmail.com
on 31 Jul 2009 at 5:12
Original issue reported on code.google.com by
RiSho...@gmail.com
on 25 Jul 2009 at 12:18