Hyrule Field Slowdown Observation

[StripTheSoul]

@ NaturalViolence: I think he rather refers to the google code pages...here is nothing like a +1

Well, in the end I guess no one can say what the devs should do and what not...it's their free time they sacrifice for this.
But I agree there are quite some issues which I would even say also started around 47xx-49xx and which are still blocking the feeling that the emulator has come much further (though it has, actually).

[Xtreme2damax]

Yeah Omega is right, too many idiots who spam +1 without testing the changes just because the change might sound good. This is one of the reasons why commenting and ratings should have been left to a certain group of informed individuals who actually test these commits and can immediately spot when a commit breaks things. The +1 spam seems more constant than those who just spam -1 without an explanation or testing anything just because it doesn't fix a game they wanted fixed.

[naoan]

Notice any revision with a word "speed up" will get MANY +1 regardless if it break something. I agree with xtreme, is there any way to limit comment or +1 to a select group of proven individual in google code?

[darkshadw]

Yeah , just try to fix an issue and say that it will decrease speed... You will see that a lot of people will spam -1...

[Starscream]

Who would pick this "select few" of "proven individuals"? I'm sure many decent people would be left out since no one really knows who actually tests the revisions. How are we to tell an idiot from a good member? It's not as easy as you may think.

[naoan]

afaik pcsx2 pulled it off with a reliable team of beta testers, it wouldn't be easy but it is feasible.

[omegadox]

(05-12-2010, 02:42 AM)NaturalViolence Wrote: I have no idea what you were trying to say there, I'm assuming it was an insult saying I'm not helping by posting a "lame comment" and that I'm just spamming instead of thoroughly testing the new builds like I should be?

I have great faith in the developers though. This is all just part of the process and completely normal. Every once and awhile they introduce a bunch of really big changes/features that cause a lot of other things to break, then they spend a month or two fixing everything and it ends up creating amazing progress. It's like the normal commercial software cycle of beta code then stable code then back to beta code, right now we're on the beta side. But soon everything will be stable again and they should release an unofficial build when that happens like Xtreme said.

I am referring to google code: http://code.google.com/p/dolphin-emu/source/list

[jakeslogan]

I still remember when i was in a forum with a rule that users have to type at least 20char before posting. People then started to post things like this "+1. Stupid 20char rule is @#$@%!!!." or "+1, miley:miley:miley:". When they don't want to spit their comment out, it's really annoying.

[NaturalViolence]

Quote:Yeah Omega is right, too many idiots who spam +1 without testing the changes just because the change might sound good. This is one of the reasons why commenting and ratings should have been left to a certain group of informed individuals who actually test these commits and can immediately spot when a commit breaks things. The +1 spam seems more constant than those who just spam -1 without an explanation or testing anything just because it doesn't fix a game they wanted fixed.

Thanks for explaining. I never read the commits and comments on google code so I had no idea what omega meant by +1 spam. That makes perfect sense though, but honestly I don't think the devs should pay any attention to those and if they don't then they won't make a difference anyways.

[Starscream]

They have to pay attention to them to some extent. That is one of the ways that the devs know that the change either works, works for more than just the dev who added it and that others are seeing the same results that are or should be expected.