Read my post. If thecause is, in fact having an LCD display, then why on earth is the problem only noticeable with the classic controller? Neither the GC or the wiimote by itself present that behaviour.
Oh sorry, didnt read that part.
Read my post. If thecause is, in fact having an LCD display, then why on earth is the problem only noticeable with the classic controller? Neither the GC or the wiimote by itself present that behaviour.
Yes, and with UNGODLY HIGH input delay I mean sometimes it doesn't even register the pads being pressed. (mind you, this also happens as soon as I launch HBC. Even the wiimote becomes jerky and kinda non responsive as long as the CC is connected.)So you're getting 'absurdly high' input delay with a Classic Controller (non-Pro)? I definitely am not experiencing that. I do all my Wii testing on a Sony CRT TV from 1998 or so - so dunno if it's down to the display device or not.
I'd like to hear from more people first whether they're experiencing problems of this nature. It might be that we're not covering some specific quirk to do with input in libogc.
For the record - about 'Tantric's emus' - if this is the 'fix' you're referring to -
https://code.google.com/p/snes9x-gx/source/detail?r=718
then it's of absolutely no use to us since we never checked the return value of PAD_ScanPads to begin with - every frame input is sampled for all pads regardless of what it returns.
Yes, and with UNGODLY HIGH input delay I mean sometimes it doesn't even register the pads being pressed. (mind you, this also happens as soon as I launch HBC. Even the wiimote becomes jerky and kinda non responsive as long as the CC is connected.)
About the CRT Vs. LCD/PLASMA display argument, if it was the case wouldn't it make sense that ALL controllers were non responsive? maybe, MAYBE it has something to with the specific combination CC+HDTV.
At first I thought it had something to do with the fact that my CC is a third party one (madkatz, if it makes any difference) so then I tried using an original one with the same results.
I'm working now on a SNES>wii/GC adapter. It SHOULD work flawlessly (cause it's using the GC ports after all) At least I hope it does cause if not then its money down the drain.
Thank you.I'm going to take another look at the input driver together with ToadKing.
Thank you.
And like I said, that behavior isn't even your emulators fault. Cause the problems begin as soon as I launch the Homebrew Channel, but maybe with that in my mind you could find an explanation for that. (and then we could troll the devs at HBC for a fix) or at least a "fix" for that behavior while using the emulator.
One more question, is there a way to play with 2 GC controllers? So far I haven't been able to do it, and even if I manage to make the GC controller the 1st player, the wiimote/CC second player can't move. Is it necessary for the CC controlled player to be 1st player? Also, is there a way to launch the HBC with a GC controller? I can navigate through the emus and homebrew apps with it, but can't for the life of me figure a way to launch the channel without a wiimote. (probably its just the way it is...)
I did that, but the wiimote/CC keeps syncing as 1st player.You have to go to the individual controller settings in RetroArch and set which controller you're using. Second player is probably set to use a CC. Also if you have Bootmii installed through MINI you can run the Homebrew channel directly and skip the Wii menu every time you start up.
I did that, but the wiimote/CC keeps syncing as 1st player.
I think we're not in the same page. I´m trying to have the wiimote as second player. Whenever I set itlike that the only controller that works is the GC (1st player) one.It does but the controller settings themselves don't change. If player one and player two are set to use the gamecube controller that's how they're going to work regardless of what actual controllers are present. I noticed this because I frequently switch around controllers and have to change the settings manually each time I do this.
I think we're not in the same page. I´m trying to have the wiimote as second player. Whenever I set itlike that the only controller that works is the GC (1st player) one.

How many more people do you need to care about it? If all that happens is that you don't own a CC, then that's ok, just tell
I don't have a Classic Controller Pro so I'm not in an ability to test and/or do experiments with it. Perhaps ToadKing does.
That's how I see it, until someone (with influence on LibreRetroArch) committed to it cares to test the thing out on a game that is known to show clearer this input lag.
I'm going to take another look at the input driver together with ToadKing.

So you're getting 'absurdly high' input delay with a Classic Controller (non-Pro)? I definitely am not experiencing that. I do all my Wii testing on a Sony CRT TV from 1998 or so - so dunno if it's down to the display device or not.
I'd like to hear from more people first whether they're experiencing problems of this nature. It might be that we're not covering some specific quirk to do with input in libogc.
And hence the reason I included those statements... :SThose two posts being on the previous page and the one you posted on...
I'd like to hear from more people first whether they're experiencing problems of this nature. It might be that we're not covering some specific quirk to do with input in libogc.
as far as I understand both show input lag, so you are not going to find discrepancies between those too, compare to a GC controller for that matter.using both a CC and a CC Pro - no discernible input delay here, certainly no 'absurdly high' one.....

That's how I see it, until someone (with influence on LibreRetroArch) committed to it cares to test the thing out on a game that is known to show clearer this input lag.
That's not what you said in my quoted post, you are just adding that for the sake of excusing."How many more people I need to care about it?
People who can do an ABX test"
My concern is not on fixing the issue, but addressing the issue, being aware of it. Because many people is experiencing it, maybe you haven't because you don't play high pacing games where one frame time matters. I couldn't really tell until I compared against a GC controller.
rest of your post - something about me bullshitting and me contradicting myself...

as far as I understand both show input lag, so you are not going to find discrepancies between those too, compare to a GC controller for that matter.
