Performance Enhancing Bug

Jump to navigation Jump to search

Yeah, the first hypothesis was only applicable to greater-than-1 weight for most kinds of smoothing, which I had thought to be likely.

The second hypothesis still isn't ruled out by that however. "Any GF other than the visited GF would get rounded down to 0" is in fact the most extreme version of what I describe in the second hypothesis.

Now that I know you are using a weight of 1 however... and thinkning about your decay... I'm now quite certain that the real cause is not anything about the smoothing, but the decay. Specifically, applying the operation "foo *= 0.995" where "foo" is an integer in the range 1 to 199, is equilivant to a decrement-by-one operation. When your weight is 1 and your array is an integer one... this means that your decay might as well be "foo *= 0.0" because you're immediately completely erasing the last data point when the next arrives.

Rednaxela (talk)00:11, 9 May 2013

That makes a lot of sense. Thank you for your help. I guess I'll have to try out decay rates until I find one that matches the performance of the bug.

Has anyone ever made an AS gun that only took one wave into account at any given time?

Sheldor (talk)01:10, 9 May 2013