Well yeah I've done enough, I even exerted more effort that is typically beyond my capabilities to help track down this issue and provide enough "important" information that I thought would be useful to developers.
There's not much more that I can do, it's up to developers to decide whether or not to use this information in order to fix the issue. From what I've observed, there doesn't seem to be much interest on the developer forefront to fix the issue as can be perceived by the lack of comments from other developers both in this thread and on the issue tracker.
Keisel has done a tremendous job with the information and contributions he has provided in this thread. Hopefully he has narrowed this the source of this issue down a bit further than I previously did. I guess there is nothing else to do but sit back and wait and hope this issue will finally get fixed someday.
Your mean? and what enough? I know he has contributed a lot in the fixing of the problem. But his responsibility is not over yet. He must stay here and keep this topic fresh. If not i can assure that it will sink like a stone and people will soon forget about it.
Hey Xtreme, many of us are following this thread. I'm doing my own research on this issue also as I think many games can benefit from this (smg?). Hopefully I can contribute on this thread, however we really need the devs to get more involved in this issue, not because it's more important but because there's a lot of testing to work with.
I agree with kernel64. If you need me or JADS to do anything to help (especially testing since we're doing that anyways) just say so.
Wow seems the developers ran out of things to fix, no commits in two days..
Either that or they lost enthusiasm and are tired, wouldn't blame them though.
I think they want some days off
maybe the problem is too tough so they have quit.
Usually people try before they quit.... I honestly don't care if he developers take a break as long as they start fixing some of the stuff that they've broken over the last 200 revisions at some point. This is starting to feel like 4700-4900 all over again. Although after they fixed everything that got broken in those revisions dolphin ended up being far better because all of the features they introduced were still there.
Many don't know if they broke something and no help from lame comments with a spam of +1 without really testing the change.
I have no idea what you were trying to say there, I'm assuming it was an insult saying I'm not helping by posting a "lame comment" and that I'm just spamming instead of thoroughly testing the new builds like I should be?
I have great faith in the developers though. This is all just part of the process and completely normal. Every once and awhile they introduce a bunch of really big changes/features that cause a lot of other things to break, then they spend a month or two fixing everything and it ends up creating amazing progress. It's like the normal commercial software cycle of beta code then stable code then back to beta code, right now we're on the beta side. But soon everything will be stable again and they should release an unofficial build when that happens like Xtreme said.