Dolphin, the GameCube and Wii emulator - Forums

I gave a look at the goals they have set themselves the developers for the 3.0 release:

Quote:Tasks:
a) fix all feature regressions
b) get the user experience into the most polished state as possible
c) try to fix as much other issues as possible
d) try to get any added features as stable as possible

As far as point a) we users can help a lot the devs to identify from which build, there were certain problems (for example, I noticed that from release 6416 onwards fps on my laptop for Mario Kart Wii dropped from 50fps to 30-35fps).

Point b) is unclear and somewhat variable from user to user (at least from what I understand it).

The most challenging are the c) and d) that are very connected. The release of version 3.0 depends on how far they want to go in fixing the issues and what how long it will take to make new features stable.

It may take a lot of time before you get to version 3.0 but in my opinion it's not so important, being able to download the sources and compile them means that in practice every day we have a "version 3.0", we as users can help the developers by going to this page and try to better identify the bugs and versions from which they arise in order to speed up their work by showing them directly the sources of the problem and help them to focus their work where it's needed.

Mario drugged?????

Quote:As far as point a) we users can help a lot the devs to identify from which build, there were certain problems (for example, I noticed that from release 6416 onwards fps on my laptop for Mario Kart Wii dropped from 50fps to 30-35fps).

FPS/gamespeed reduction is not a regression.

The point of release 3.0 is supposed to be a sudden shift towards stability. Developers have been told to hold off on commiting new features/major changes that they are working on and are instead fixing regressions of features from 2.0 while trying to make dolphin as stable and usable as possible.

(04-01-2011, 01:28 PM)NaturalViolence Wrote: [ -> ]FPS/gamespeed reduction is not a regression.

...opinable...fps/gamespeed reduction is the result of regrssions in some parts of the code, but it's my opinion...

(04-01-2011, 01:28 PM)NaturalViolence Wrote: [ -> ]The point of release 3.0 is supposed to be a sudden shift towards stability. Developers have been told to hold off on commiting new features/major changes that they are working on and are instead fixing regressions of features from 2.0 while trying to make dolphin as stable and usable as possible.

which is the meaning of points c) and d) no?

(04-02-2011, 12:18 AM)newneo85 Wrote: [ -> ]

(04-01-2011, 01:28 PM)NaturalViolence Wrote: [ -> ]FPS/gamespeed reduction is not a regression.

...opinable...

Actually, it's not.
But this has been explained often enough now...

direct3D performance is a regression.

Quote:which is the meaning of points c) and d) no?

They should be changed to:

c) Fix other issues as long as you don't introduce new features or compromise stability. However you must get approval from the other devs first, some fixes are just too tempting.

d) If a developer is stupid enough to commit a feature and neobrain doesn't kill him/her then that developer should make sure the feature is stable before release

c) is referring to any issues in general (anything which isn't a regression or feature wish), even issues which existed before 2.0.
d) is referring to features introduced since 2.0 until now, which might have been committed in a semi-working state and still would need some polishing. Not sure if that really covers anything, but it's self explanatory that new features should actually be working when we're doing a release.

FPS lowering is not a regression seeing as it has lowered because other more important game breaking bugs have been fixed

(04-02-2011, 01:15 PM)Vegerunks Wrote: [ -> ]FPS lowering is not a regression seeing as it has lowered because other more important game breaking bugs have been fixed

its a regression when it only occurs in direct3d.