What about drawing each point individually using a line algorithm? Would that be any faster than the line commands? I don't know how fast they are now.

boot2490, that's just basically how Quigibo's mode 7 axe demo works. (HappyBobJr, am I correct in assuming you used a lot of his axe code for this? )

"99.9999% if this code is Quigibo's"
Yes you are correct.
I modified it a bit for speed and optimizations though, so i don't feel too bad

I have gotten it quite fast now.


This project is going on hold (ish) for a few days.
I am now working on tiles and a map maker for the game to make it easier to test, and more fun to play.
I guess that really ising putting it on hold, but i won' be working on gameplay.

How are you storing the level?
(1 byte/tile, 1 bit/tile, etc)

Ok, so i figured out my problem.  I was  using the variable Z for two things

Also do not do Fill(L3,1,30)
It causes weirdnesses

I am using L3 just as free ram for the map maker.

Nope, i doubt that is a bug.
I was doing
Fill(loc,#,quantity)
instead of
Fill(loc,quantity,#)

Got the maker finished

source is 1600 bytes
Compiled is 1916 bytes


To do, in this order.

*Optimize and remove unneeded variables.  about 750 cycles per frame i think.
*Fix rolling ball sprite.
*organize code.
*Add more tiles.  ie Slowdown and conveyor belt tiles, anti gravity and such.
*Say hi to Frey.
* Request someone finds some more optimizations.
* Code death.
* Publish.

Edit: Best easy optimisation ever.
from
1,3
to
1,+2

That is fixable to some extent.
It costs speed though.  but it looks like i shouldn't have problems with that.
Only side effect is that it makes it go to slow with edges bolded.