Dolphin 3.5?

[delroth]

Maybe try to have a logarithmic scale on that bar? After all, changes in recent revisions are imho more important than changes in older revs.

[Zee530]

I also would prefer a standard 4.0 release instead of a 3.5 or 3.9, i would prefer they go into 3.0-1xxx if they run out of space.

[Duke Nukem]

It's not Dolphin 3.9 bug tracker any longer it's Dolphin 3.5 bug tracker

I guess 3.5 is gonna be the version that's gonna be released soon.

[DefenderX]

I hope, Dolphin 3.5 will emulate F-Zero GX better And yeah, I'm able to play this game @ 40-50FPS on my Macbook Pro (Win 7). Only the crashes and freezes are annoying, the rest is fine ^^

[Duke Nukem]

The majority of the games I use in Dolphin works to near 100% satisfaction as of today.
Super Mario Galaxy however gives me GFX FIFO errors on Beach Bowl Galaxy on the levels that requires you to swim.
My hopes for Dolphin 3.5 is that it's cured somehow, I don't really know what's causing it to freak out on that Galaxy. Never had any problems with it on 3.0 before.

[neobrain]

It's not going to be fixed without an issue report and some regression testing... :|

[Duke Nukem]

(12-01-2012, 10:53 PM)neobrain Wrote: It's not going to be fixed without an issue report and some regression testing... :|

You're right about that neobrain, but I'm not even sure anyone else have my problem since no one else have reported it in the Super Mario Galaxy thread where I have posted many many times about the problem.
I have pledged to people to try it out but no one has reported or answered back with any feedback.
Given that it was a couple of weeks since I first posted my problem, maybe it's just me that have this specific issue after all.

[neobrain]

It's likely not, people are just terrible at regression testing this stuff. No offense, but that's just the way it is :/

Issues like this get unnoticed for hundreds of revisions and even more obvious ones are reported half a year after the regression gets introduced. Makes me wonder if people test new stuff at all or if they just cannot be bothered to report bugs anymore...

[Duke Nukem]

(12-02-2012, 01:01 AM)neobrain Wrote: It's likely not, people are just terrible at regression testing this stuff. No offense, but that's just the way it is :/

Issues like this get unnoticed for hundreds of revisions and even more obvious ones are reported half a year after the regression gets introduced. Makes me wonder if people test new stuff at all or if they just cannot be bothered to report bugs anymore...

I would be more surprised if a GFX FIFO error would have gone unnoticed for Star Wars Jedi Knight II: Jedi Outcast for GC which not even a 1% of the forum members play here then Super Mario Galaxy one of the most popular games for the Wii ever.
But maybe it's like you said, people don't test new stuff at all and just cannot be bothered to report bugs anymore. A shame really, it doesn't take more then a couple of minutes to test something out.

[NaturalViolence]

Quote:Issues like this get unnoticed for hundreds of revisions and even more obvious ones are reported half a year after the regression gets introduced. Makes me wonder if people test new stuff at all or if they just cannot be bothered to report bugs anymore..

Regression testing involves a lot of work. Most dolphin users just want to play their games and don't bother with this. A significant portion of the ones who would be willing to test aren't active in the community and aren't aware of the changes that currently need testing or how to properly test them (what to look for). Not to mention that there are so many different games and settings that you're bound to miss something no matter how rigorously you test new changes.

Recently the devs (including you) have started posting testing threads to raise forum awareness of changes being made. This is a step in the right direction but didn't happen until recently and is only done for what are perceived as the most important changes. In an ideal world all devs would do this with their changes. Making forum posts, blog posts on the main site, and alerts on googlecode to make their changes noticed by as many parts of the community as possible. Let's face it most users don't constantly check googlecode for new branches. It would be amazing if we could integrate this into the application somehow. It would make it stupid easy and extremely accessible. Perhaps have a button that opens a pop up window that lists branches that are currently flagged as needing testing, has a description from the author of the branch about what it does and what to look for when testing, and allows the user to auto-download that build and integrate their current config files, gameconfig files, savestates, GC memory cards, and Wii NAND by clicking on it in the menu.

I'll test some of this stuff if someone is willing to make a thread describing the issue and posting a save that allows me to access the area in question.