• Login
  • Register
  • Dolphin Forums
  • Home
  • FAQ
  • Download
  • Wiki
  • Code


Dolphin, the GameCube and Wii emulator - Forums › Dolphin Emulator Discussion and Support › General Discussion v
« Previous 1 … 164 165 166 167 168 … 370 Next »

Should I use the stable or development build?
View New Posts | View Today's Posts

Pages (2): 1 2 Next »
Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Threaded Mode
Should I use the stable or development build?
04-11-2013, 11:43 PM
#1
Scootaloo Offline
I'm liking this idea!
***
Posts: 101
Threads: 7
Joined: Apr 2013
I know that it is a double edged sword for each.

The pros and cons (from what little I know):

Stable build: it is [supposed to be] less buggy and be more reliable. However it does not get updates nearly as fast as the dev. builds (because obviously its not a dev. build :p).

Development build: has hot fixes (I think that's the right term) and is updated much faster. However things can break much more easily.
__________
So should I use the stable or dev. build? keep in mind I am some what of a noob, but I am willing to learn. Cheers!
Find
Reply
04-12-2013, 12:01 AM
#2
LordVador Offline
Christmas Vader
*******
Posts: 8,851
Threads: 1,908
Joined: Mar 2011
Use both.

Try your games with the stable release first. If they work fine you have no reason to use something else. If they don't work then try latest builds (or older ones Tongue ).

Also you can try latest builds to see what improvements/changes have just been done. Not necessarily to play but to keep up-to-date.

This is what I usually do
[color=#ff0000][color=#006600]i5 3570K @ 4.5GHz/GTX 660 Ti/RAM 4GB/Win7 x64[/color][/color]
Find
Reply
04-12-2013, 12:05 AM (This post was last modified: 04-12-2013, 12:08 AM by Scootaloo.)
#3
Scootaloo Offline
I'm liking this idea!
***
Posts: 101
Threads: 7
Joined: Apr 2013
(04-12-2013, 12:01 AM)LordVador Wrote: Use both.

Try your games with the stable release first. If they work fine you have no reason to use something else. If they don't work then try latest builds (or older ones Tongue ).

Also you can try latest builds to see what improvements/changes have just been done. Not necessarily to play but to keep up-to-date.

This is what I usually do
Thanks for the advice. I think I'll try the stable build and see how it runs first. First I need to rip my games and hope that they work...
Find
Reply
04-12-2013, 01:45 AM (This post was last modified: 04-12-2013, 01:46 AM by Zee530.)
#4
Zee530 Offline
Above and Beyond
*******
Posts: 1,747
Threads: 12
Joined: Jan 2011
This is a subjective decision, just do what floats your boat.
......?????
Find
Reply
04-12-2013, 09:43 AM
#5
nintendo_nerd Offline
Fox Admirer
****
Posts: 327
Threads: 26
Joined: Aug 2009
If you want to have the latest features (such as the reworked HLE audio), the development builds are your best bet, for the most part they're fairly stable, but they might crash every now and then.
Custom Desktop -
CPU: Intel Core i5 3570 3.4 GHz to 3.8 GHz (Turbo Boost)
GPU: MSI nVidia GTX 660 2 GB GDDR5
RAM: 8192MB DDR3 SDRAM PC2 10600 1333MHz
OS: Windows 7 Professional 64-bit
HDD: 1 TB Western Digital 7200RPM HDD

Find
Reply
04-12-2013, 09:53 AM
#6
RachelB Offline
Developer
*******
Moderators
Posts: 1,003
Threads: 1
Joined: Dec 2011
(04-12-2013, 09:43 AM)nintendo_nerd Wrote: but they might crash every now and then.
Not that the same isn't true of the "stable releases".
Find
Reply
04-12-2013, 10:08 AM (This post was last modified: 04-12-2013, 10:09 AM by Scootaloo.)
#7
Scootaloo Offline
I'm liking this idea!
***
Posts: 101
Threads: 7
Joined: Apr 2013
(04-12-2013, 09:53 AM)RachelB Wrote:
(04-12-2013, 09:43 AM)nintendo_nerd Wrote: but they might crash every now and then.
Not that the same isn't true of the "stable releases".
Cool a developer! Heart
____
Yep no release is truly "stable". I think that a "stable release" is a release that is just less likely to crash and have problems.
Find
Reply
04-12-2013, 01:52 PM
#8
RachelB Offline
Developer
*******
Moderators
Posts: 1,003
Threads: 1
Joined: Dec 2011
Really, the point of using a stable release is that it stays the same, and it's easier to find information on what works and what doesn't (since more people use it). In general, the newest revision will be the best. Sometimes though, there's regressions, and things stop working. The benefit of using a stable release is that you can easily find out what works, and what doesn't, and that will always be the case. If you stay up to date with the newest changes, you can't easily be sure something that worked last week will still work today.

The stable release is NOT less likely to have problems. Do you think we've just been making things worse in the over 1200 commits to master since 3.5? Some things have gotten worse, but overall, it's pretty safe to say the latest revision has way fewer problems than 3.5.
Find
Reply
04-12-2013, 03:48 PM
#9
Scootaloo Offline
I'm liking this idea!
***
Posts: 101
Threads: 7
Joined: Apr 2013
(04-12-2013, 01:52 PM)RachelB Wrote: Really, the point of using a stable release is that it stays the same, and it's easier to find information on what works and what doesn't (since more people use it). In general, the newest revision will be the best. Sometimes though, there's regressions, and things stop working. The benefit of using a stable release is that you can easily find out what works, and what doesn't, and that will always be the case. If you stay up to date with the newest changes, you can't easily be sure something that worked last week will still work today.

The stable release is NOT less likely to have problems. Do you think we've just been making things worse in the over 1200 commits to master since 3.5? Some things have gotten worse, but overall, it's pretty safe to say the latest revision has way fewer problems than 3.5.
I was wrong. I guess it does make sense to have one version to be able to easily get information for.

Commit? I'm assuming that's a change? sorry I don't know the terminology. I'm just going off what Google says about programming and "commits".

To answer your rhetorical question: "Do you think we've just been making things worse in the over 1200 commits to master since 3.5?" Well I'd hope not. I just like to stay with the stable version, because why would I want to upgrade 2 times every day? granted I'm sure some users (not devs. who have to do it) do, but as for me it is just a hassle. Since my games for the most part run fine I don't see the need to use the SVN/Nightly Build (whatever you call it). Unless I need to upgrade for some reason I'll just wait until the next stable release is picked.

Sorry for apparently ticking you off. Thanks for your work on the emulator though.
Find
Reply
04-12-2013, 04:03 PM
#10
RachelB Offline
Developer
*******
Moderators
Posts: 1,003
Threads: 1
Joined: Dec 2011
Quote:Commit? I'm assuming that's a change?
That's right.

Quote:I just like to stay with the stable version, because why would I want to upgrade 2 times every day?
Well, you wouldn't. It might be wise to update every few weeks, or months though.

Quote:Sorry for apparently ticking you off.
You didn't. Sorry if it came across that way.
Find
Reply
« Next Oldest | Next Newest »
Pages (2): 1 2 Next »


  • View a Printable Version
Forum Jump:


Users browsing this thread: 1 Guest(s)



Powered By MyBB | Theme by Fragma