Whew, finished! I'm gonna go take a break now. Enjoy! 

Those sprites look so good, they look even better when they flow together. With these newest additions, all I can say is wow.

On another note, I'm going to have to start, clipping all these sprites. I left in all the white space just to make it easier, but now they take up 3,969 bytes in the program, and 9,261 bytes unpacked on calc. I've used up 14kb of the extra ram page. So that's next on my agenda.

Here's the latest if anyone wants to give it a go.

Edit:
    Jk, I use 15kb of extra ram.

wow those arwing sprites look awesome! 
btw tp77 do you think that you will be able to fit it into a program or you will make it into an app?
also here's a sprite for falco

Very nice Falco.

I am going to try as hard as I can to keep this in mirage. I use a lot of self modifying code so it would get ugly if I tried to go with an app. Plus, apps aren't as convenient as programs to the average user.

I have a few tricks to make space when I run out. The first is to compress all of the pictures, the only downside to this is that when I uncompress them, I'm going to have to put them somewhere. So when I run out of my 16k of extra ram, I'm going to figure out how to archive 8000h-9D95h. It'll be tough, but that's an extra 7.5kb. Plus I can make a temporary appVar for another ~6kb. If things get really out of hand, I may even try to archive the VAT, but there are so many things you have to watch for when you do that.

Bosses will be scary and hacky, but I'll definitely have them.

Levels are as many as I can make. They really don't take much space. The little demo I've been showing is only like 100 bytes. If all else fails, I can make a separate file that is all data. Then I would just import the current level, run it, and when it's done, grab the next one.

For boosting / breaking I only need one sprite. I don't see any reason to waste the resources for sprites that would only be used 1/1000th of the time. Like, what are the chances that a person would be pressing up and right while breaking. Besides, for boosting, it is going so fast that realistically it would level out anyways. I guess it's ok if the braking sprite is bigger than 21. I don't really see any other way of doing it.

I'll probably eventually do first person, but I think that would be easier to do with polygons rather than sprites. Or I could skip the whole animation part.

I've never really played starfox so I'm not sure. I'm pretty much going by the SNES version, and I think most of those bosses are just random things. But if the character is in the SNES one, go for it. For instance, I definitely could not do the battles where you have to shoot down another ship, that would require an entirely different engine.

^^i'll do the same as yunhua

quick question- in star fox 64 there is a robot named "rob64," who helps you in training mode and gives you items throughout the game. what do you think of a rob-ti character for this game?