It's a "stable version" because, being not updated periodically, it doesn't risk being randomly broken by someone's mistake. It also is guaranteed to be broken in lots of (mostly known) ways, which is why when someone makes a support thread, the first advice is always "try updating to the latest version". Unless you're volunteering to backport fixes to 4.0.2, there's really only so much that can be done to support it -- if something was a known issue in 4.0.2 and has been fixed since, there's not really any way to get the fix in 4.0.2 without a backport.
Yes we should probably have a new stable release months ago, but complain to delroth about that one
(01-22-2015, 09:29 PM)Fiora Wrote: [ -> ]It's a "stable version" because, being not updated periodically, it doesn't risk being randomly broken by someone's mistake. It also is guaranteed to be broken in lots of (mostly known) ways, which is why when someone makes a support thread, the first advice is always "try updating to the latest version". Unless you're volunteering to backport fixes to 4.0.2, there's really only so much that can be done to support it -- if something was a known issue in 4.0.2 and has been fixed since, there's not really any way to get the fix in 4.0.2 without a backport.
Yes we should probably have a new stable release months ago, but complain to delroth about that one
I understand what you are saying and I agree to some extent.
However, take Metroid Prime 2 Echoes for example. If I recall correctly at one time the compatibility for the game in older releases was up to 5 stars.
With 4.0.2 it's 4 stars which is totally playable for me but with newer revisions it's listed as 3 stars and is totally unplayable because of the numerous GFX Fiio crashes with either OpenGL or Direct3d.
I have completed the game with 3.0 from start to finish, I believe I could do that again with 4.0.2 but with newer revisions, hell no.
As soon as Samus starts to rise from her ship, all hell starts to break loose.
There is absolutely no way I would recommend using newer revisions for Metroid Prime 2 Echoes to other people.
EDIT:
The wiki page for Metroid Prime 2 Echoes lists it as 4 stars compatibility but the game ini lists it as 3 stars in newer revisions.
That's strange, given how much trouble I had with this game in newer revisions it should be listed as a 3 star compatibility ranking or lower.
I agree with Duke Nukem on this, I'v been playing Metroid Prime for as long as I'v had my rig with stable release 4.0.2. One day, I decided to update to latest revisions and tried Metroid Prime with it, everytime I start up Samus on a save station the frame rate slows down significantly when the lasers all pointing at him. I don't get this under 4.0.2, that's why I always use 4.0.2 with Metroid Prime. Although latest revisions may fix bugs and be faster on some games, other games may get affected in some ways or another.
They won't be making a new stable build until they can fix all the regressions and address the other "current" issues in the
Issue tracker
(01-23-2015, 02:47 AM)cyrax33 Wrote: [ -> ]I agree with Duke Nukem on this, I'v been playing Metroid Prime for as long as I'v had my rig with stable release 4.0.2. One day, I decided to update to latest revisions and tried Metroid Prime with it, everytime I start up Samus on a save station the frame rate slows down significantly when the lasers all pointing at him. I don't get this under 4.0.2, that's why I always use 4.0.2 with Metroid Prime. Although latest revisions may fix bugs and be faster on some games, other games may get affected in some ways or another.
If the developers don't know what issue that is exactly, they can't do anything about it. Which means, 4.0.2 will stay the best build for game, forever.
Please try to post the earliest build that has this bad behavior, and the last that ran well.
(01-23-2015, 03:37 AM)mimimi Wrote: [ -> ]If the developers don't know what issue that is exactly, they can't do anything about it. Which means, 4.0.2 will stay the best build for game, forever.
Please try to post the earliest build that has this bad behavior, and the last that ran well.
You're right on that one but it's not easy to pinpoint the exact build that started to cause trouble if people ain't willing to start testing.
I remember one time when I was using Dolphin 3.0 and I wanted to try something new so I downloaded revision 3.0-830, turned out Super Mario Galaxy - Beach Bowl Galaxy gave me a bunch of GFX FIFO errors all of a sudden when I swam in the water.
It drove me mad, but after much testing and pinpointing I found out the exact revision that caused the problem and it was later solved.
However regarding 4.0.2, the only real problem I have with it is that some games tend to be slow but it's not a big deal.
Hah I just started a topic on this. I'm currently streaming both of these games and I can tell you with my rig there are no slowdowns anywhere except for the map and on entry/exit from water. The game runs brilliantly, in fact with the new dev pushes it runs even faster! The "stable" version doesn't perform well at all compared to the newer ones, but I can concur that older versions for some reason played prime more fluidly (albeit slower) specifically the map screen, it didn't lag.
Did I mention I can play this with x4 AA and AF on an upscaled resolution? If they could just fix the map lag, this game would be so EPIC to play on dolphin ^_^
The map lag is likely our line-width/point-size shader getting smashed
(01-23-2015, 11:38 PM)JMC47 Wrote: [ -> ]The map lag is likely our line-width/point-size shader getting smashed
is it something that could be addressed? I mean srsly the game is butter smooth with that exception. I mean, sometimes I get warnings saying my CPU is too fast, but it doesn't crash the game and it happens mostly in the snow areas (metroid prime) if I just click yes it goes away.
(01-24-2015, 04:10 AM)Rageypoo Wrote: [ -> ] (01-23-2015, 11:38 PM)JMC47 Wrote: [ -> ]The map lag is likely our line-width/point-size shader getting smashed
is it something that could be addressed? I mean srsly the game is butter smooth with that exception. I mean, sometimes I get warnings saying my CPU is too fast, but it doesn't crash the game and it happens mostly in the snow areas (metroid prime) if I just click yes it goes away.
Sounds to me like you are overclocking or something if you get messages like that. I use stock clock and I never get messages like that.
Maybe you should underclock?