Dolphin, the GameCube and Wii emulator - Forums

Some of you may have noticed that a lot has been broken by recent revisions. But of course a lot has been fixed as well. This creates a conflict in some games where you're not sure what revision to use since newer revisions will replace some of the issues you had with older revisions with different issues. I believe that if the devs just stopped fixing issue on googlecode, made a list of every issue in newer revisions that wasn't in 2.0, and then fixed every problem on that list we would have a nearly perfect dolphin revision, all of the good and none of the bad. Obviously we would still have a lot of issues since many issues have never been fixed but I'm not talking about those, I'm just talking about the ones that have popped up recently. Obviously this is never going to happen since dolphin's development style/method is quite different from this. However we can still make it happen.

Many of these problems are well known, have been around for hundreds of revisions, and are already reported on googlecode. Why are they still not fixed then? Simply because no one has taken the time to track down the issue to the single revision that caused it. I have done this before, and I won't lie, it is a pain in the ass and very time consuming. But it must be done if we ever want to fix these problems.

So since many of you want to help dolphin grow but don't know how and can't code I hereby give you another option (besides posting issues on googlecode of course). Either:

1. Find an issue with a game that is present in the current revision but not present in 2.0 (r5350) and post it here

or

2. Pick one of the issues on this list and track it down to a particular revision. Then post the issue and which revision caused it here.

I know that what I am asking is annoying and time consuming. But I think you'll agree with me that the results will be worth it.

How do I do this? First you test both the latest revision and 2.0 and make sure that the issue is present in the latest revision but not 2.0. LOW PERFORMANCE DOES NOT COUNT AS AN ISSUE. FIFO ISSUES DO NOT COUNT EITHER (since it is being worked on). Then you test a revision halfway in between. Then keep cutting it in half. So let's say for example the issue exists in 6500 but not in 5350. I would then test 5900. If the issue exists in 5900 then you know it was a revision between 5900-6500 that broke it. So then you test halfway between them, 6200. And so on. Make a list as you do this so you don't lost track. Just number the revisions you testing and write "PROBLEM" or "NO PROBLEM" next to them until you get it down to a specific revision.

Some issues we already know about that come to mind:

AR Codes broken (broken inbetween 5350 and 6331)
Non-fifo related stuttering (likely caused by changes to the shader caching system, framerate and vps do not drop when it happens, noticable in NSMB world 2-3, happened between 6000 and 6500)

I'm incredible tired right now so I'll add some more later when I can think clearly. Unfortunately we've gotten used to a lot of these problems

Nice one! This thread has got my "official support", if that somehow motivates some end users to report issues

I'm often reading at different places (IRC, Google Code, forums, ..) that people report regressions, but it's just too many or not detailed enough reports to memorize, yet even look at all of them. Having a central place for this kind of stuff definitely is a step in the right direction.

---

Stickied

Do you really think anyone is going to read that? We can't get anyone to read a lot less when it directly helps their game issues.

So should I change the title to "ATTENTION EVERYONE! EASY WAY FOUND TO FIX ALL GAMES PERFECTLY AND ATTAIN 100% SPEED ON ANY SETUP!!!"?

I actually would have preferred it if you haden't stickied it so quickly. It's actually less noticable this way. Oh well, time to see if anyone wants to contribute.

RE4 Wii USA, using the DSP LLE (6780) the music continues stopping, just like in HLE.
Here my save: http://www.mediafire.com/download.php?pfzfnazx5b3964c
Tutorial: Right-click on the game and Open Wii save folder Put the files here
Keep on keeping on, take the key, kill the blind, disable the fire and go up there and enter the door (and the guy in red will yell kill him) and the music here stop play for a few minutes later.

The problem does not exist in 2.0? And are you using jit dynarec?

Well, I' ve read this
And man, this thread is one of NaturalViolence's great ideas :p
You have my colaboration :p

I don't think the idea is to post game issues here, but to read the first post and learn how to find the problem yourself. There are thousands of threads to just post a problem in.

No the idea is to post issues that are in the latest revision that weren't in 2.0 and/or track down which revision caused them.

Isnt it what Hyperspeed did?
He tracked the issue down to rev 6780, I think.