I think the only way to make it faster is to have the map stored in a string and a second copy in a pic (where solid tiles are all white), then do pxl-test collision detection. I think Builderboy did that in Trapped.

Almost right.  I had the strings stored in my program, and then instead of Output()ing them onto the homescreen, i Text()ed them onto the graph screen.  It took longer to display maps, but i was able to use pxl-test() for collision, which made movement faster

It might be tricky if the wheels are already at the bottom of the sprite though

Also, an idea.  Since the calc screen is somewhat limited, would it be possible to have the camera not focus on the player itself, but the area in front of the player?

Yep, that should work That is, are you able to write the compression routine in itself?  or do you need some pointers?

Alright, first, can't quite figure out what sub GN is suposed to do..  what does variable D mean?  It isn't used anywhere else in the code you posted.

Second, why are you looping from 0 to your velocity? For(r3,0,{Θ*4+GDB0→r5+3}) I think you want to move your character forward 1 space and check for collision each time?  Problems are going to arise when your velocity becomes negative.  I recommend switching to x256 format, since you are working with physics, and I recommend just incrementing your characters position by their velocity.  If they collide with an object, move them back to where they were before, and reverse the velocity.


EDIT: WOW thats an amazing application of cellular automata!  Outstanding! 

Nice catch, can't wait for the new version

I imagine you are storing the string directly in your program, displaying it with output, and then using sub() for collision?