03-06-2010, 04:28 AM
apenao, I think you might be using it inorrectly - have you noticed how flickery it is at the top of the screen?
It's because there's a long time between erase and redraw. Each sprite has two locations - next and previous. You only need to update the next one, erase and redraw.
I've got a version that's much tighter there, but it still is flickery for the top 26 pixels. I'm trying to tighten (and perhaps shorten?) the code to make it faster to cover the shortfall, as well as look at their demo and find out why it doesn't have this issue at all.
If I can get the bugs out and make it even faster and smaller (one subroutine I got 30% faster!) then I'll post it up here.
The docopy routine is also duplicated, so I deleted one to save quite a few bytes.
It's because there's a long time between erase and redraw. Each sprite has two locations - next and previous. You only need to update the next one, erase and redraw.
I've got a version that's much tighter there, but it still is flickery for the top 26 pixels. I'm trying to tighten (and perhaps shorten?) the code to make it faster to cover the shortfall, as well as look at their demo and find out why it doesn't have this issue at all.
If I can get the bugs out and make it even faster and smaller (one subroutine I got 30% faster!) then I'll post it up here.
The docopy routine is also duplicated, so I deleted one to save quite a few bytes.