2010-03-29, 05:08 AM
Almost there.
Something in either the buffer bit, or the erase bit is putting data where it shouldn't.
But a quick test shows:
Original fourspriter, 4 sprites running, 250 "bufferAndDraw" cycles: 62 frames.
Upcoming version, 4 sprites active, 250 "bufferAndDraw" cycles: 5 frames.
If this makes, it's going to be scary fast. I have no idea if it's going to be fast enough to do four sprites flicker free at 50 FPS beating the ray-trace, but it's making a shot at goal.
Something in either the buffer bit, or the erase bit is putting data where it shouldn't.
But a quick test shows:
Original fourspriter, 4 sprites running, 250 "bufferAndDraw" cycles: 62 frames.
Upcoming version, 4 sprites active, 250 "bufferAndDraw" cycles: 5 frames.
If this makes, it's going to be scary fast. I have no idea if it's going to be fast enough to do four sprites flicker free at 50 FPS beating the ray-trace, but it's making a shot at goal.