So I can't seem to run newer versions. 4.0.2 runs great, but if I try a dev release I get maybe 5 FPS. I've tried going to OpenGL, that did nothing. I removed all graphical enhancements, tried running at it's native resolution, just about anything. It's driving me crazy. I have a fairly beefy computer(i7-4770 3.4 GHz, 32 gigs of RAM, Nvidia GTX 660), and like I said, the last stable release runs fantastically. I read that some amazing progress has been made on Dolphin and wanted to use a newer version, but I can't for the life of me figure out what's going on. I've tried going backwards, and got all the way to build released this past January, and have the same problems.
Thanks to all who take the time to read this. Sorry if this is a common problem and I'm just being dumb.
EDIT: Updated drivers, restarted, now I'm good. Sorry again for junking up the forum.
hint: "framelimit=audio" on 4.0.2 is "framelimit=5fps" on dev builds
(09-24-2015, 04:20 PM)evolvedmessiah Wrote: [ -> ]So I can't seem to run newer versions. 4.0.2 runs great, but if I try a dev release I get maybe 5 FPS. I've tried going to OpenGL, that did nothing. I removed all graphical enhancements, tried running at it's native resolution, just about anything. It's driving me crazy. I have a fairly beefy computer(i7-4770 3.4 GHz, 32 gigs of RAM, Nvidia GTX 660), and like I said, the last stable release runs fantastically. I read that some amazing progress has been made on Dolphin and wanted to use a newer version, but I can't for the life of me figure out what's going on. I've tried going backwards, and got all the way to build released this past January, and have the same problems.
Thanks to all who take the time to read this. Sorry if this is a common problem and I'm just being dumb.
EDIT: Updated drivers, restarted, now I'm good. Sorry again for junking up the forum.
I totally agree with you, even the release candidate versions are not working as good as the stable version that was released for almost 2 years ago.
Read what desgaus said, its a lot more common than you think. Make sure your framelimit is set to "auto"
(09-25-2015, 04:40 AM)KHg8m3r Wrote: [ -> ]Read what desgaus said, its a lot more common than you think. Make sure your framelimit is set to "auto"
Framelimit is on auto as default. I don't mean to be mean but new builds are disastrous compared to the old stable version. It's as if they were made by two different teams and the second team tries to "re-invent" rather than to keep what's working.
Also when the devs only give support or rather want us to use the new versions that got many bugs makes me to think that they did not made the old stable version. I guess one reason is that they want us to be testers.
But anyway, I apologizes for being a douchebag but I'm hoping the next stable version is as stable as the old one, but with new improved features.
Just because your experience was "disastrous", doesn't mean the overall experience for others is the same. I have had no problems with the development builds, and I was able to complete SMG2 at 1080p60 on a relatively recent build.
*ahem* Moving on, do you have the same problem as the OP? It isn't exactly clear from your posts.
Keoma is probably trying to play a demanding game that suffers a speed decrease as a result of all the accuracy improvements in the development builds. Most games have gotten both faster and more accurate since 4.0.2, but regressions do happen, which is why they're called
development builds.
He's also using a Sandy Bridge CPU, which certainly isn't ideal for playing the most demanding games.
(09-25-2015, 07:09 AM)OatmealDome Wrote: [ -> ]Just because your experience was "disastrous", doesn't mean the overall experience for others is the same. I have had no problems with the development builds, and I was able to complete SMG2 at 1080p60 on a relatively recent build.
*ahem* Moving on, do you have the same problem as the OP? It isn't exactly clear from your posts.
One can only talk on his behalf. Yes, I have same problem as him.
The OP solved his problem by updating his drivers. Perhaps it would work for you, too.
(09-25-2015, 07:24 AM)Aleron Ives Wrote: [ -> ]The OP solved his problem by updating his drivers. Perhaps it would work for you, too.
I always got the latest drivers. The OP doesn't say what windows version he got. I got win 10 x64, maybe thats giving me problem.