Thanks.  I'm going to take a look at the wall/floor collision as part of the other stuff that needs fixing.  Also, I probably will use text on the graph screen, but it shouldn't cause much of a slow down because it won't update the screen until I tell it to.

Update

Sigh... this has not been a fun update.
*Updated to Axe 2.0, meaning I changed the contrast code from hex to Axe, and exported the pic.
*I have visited 4 seperate physics teachers for help in working out the collisions with no luck.  I am working on it though, its just very stressful and hard.

Ouch sorry to hear about the issues you got :S, I hope you can get them fixed

Well, for collisions I do not use pixel test because of how limited it is.  Objects can interact with the enviornment, meaning the map, just fine.  However, they do not interact with each other very well.  As you can see in this screenshot:

The collisions work fine.  That is, until they hit a wall, in which case you can go through objects.  It is not easy, but I feel like I can make something work here soon.

I thought about that, but it would require another byte per object to store mass.  That would reduce the maximum number of objects.  Thoughts?

26 objects at once.

Yeah, thats a good idea.  I also store the width and height of each object in a single byte, because who really needs a 255 pixel wide object?

Nice!
A full physics engine with 64-bit precision however, is a little more complex.  I will do my best to compress it.