Tell me "how to code and contribute", and how "to put up some raw numbers and measurements derived from their 'tests' " and I will, gladly.Let's make this thing perfectly clear - I don't need 'testers' so much, I need people who know how to code and contribute, and people who are willing to put up some raw numbers and measurements derived from their 'tests' instead of just saying 'I feel input lag' (that's as close to useless to me as somebody saying 'I can feel the force').. Nobody can have any influence on me (Squarepusher) because I don't take (monetary) donations and so I am under no obligations to get anything done for you or anyone else. If something gets done, it's entirely out of my own accord and because I feel like doing it.
For the record, my own take on this issue is - I have a Classic Controller myself and I never experienced much of a problem. That being said, I will look into trying to improve the input driver but I honestly don't see how it's going to greatly matter.
Only way you can expect a clear improvement to happen straight away is for some libogc dev to step forward and tell us what we're doing wrong (that is, IF we're doing anything wrong).
[quote='"Dogway"]
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 (won't fix), but don't assume 4 people bother themselves to come around and report without doing their homework (tests, etc).
You expect me to take everyone at his word that it's the fault of my/our pogram when it's almost certain that your particular brand of HDTV / wireless controller has a 90/80% impact on the severity of 'input lag'? This is why the modern HDTV era sucks - the TV manufacturers don't care the slightest about this issue, the public is so infatuated and in love with these TVs that they keep buying it, and then developers will have to deal with a lot of bitching about 'input lag', blablabla.
How many more people I need to care about it?
People who can do an ABX test. Look it up on Wikipedia.
https://en.wikipedia.org/wiki/ABX_test
Time to do something that resembles some 'real' science instead of gut feelings - 'oh I feel something is wrong'. I need measurements.
I'm sorry but your hostile response just rubs me the wrong way and it annoys me even more because all of those 'reports' you linked to are all just of the type 'oh I feel input lag' - just saying 'there is input lag' is not helpful in any way or shape at all - I need something quantifiable, not 'gut feelings'.
If you're expecting people to give you "numbers" maybe you should upload some kind of tool to measure the response time.
I'm not trying to be a pain in the ass and I'm MOST DEFINITELY not expecting you to fix it or anything. Cause I know it's not your job and/or you're not obligated to do so. I was just trying to find out if this is, in fact, a known issue (which apparently, it is).
You're free to tell me or anyone else having this problem "f*ck off, I don't give 2 sh*ts about it" and that's it. Trust me, we're not trying to bring you guys "down" or anything. And we're obviously not forced by anyone to keep using your emulator. I guess if I were to develop an emulator or any other app I'd like to get as much feedback as possible. Guess that's just me.
Please, excuse me if I "bothered" you with my posts. From now on I'll either wait for a fix (if there is ever one) or just refrain from using an emulator on the WII.











