thanks, well actually I'm going to make all my tiles that are not solid objects, because I can have any tile I want, it will just pxl-test() for pixels only not whole tiles.

well yes, but he doesn't fall at 2 pixels per frame, but if he was too, I would do the check twice in a row, which is how I do the running
I'm using the pixel test method in my tutorial.

no it wont, my screenshot is slow because it's running at 6MHz, it runs way too fast at 15MHz. and so far on a 83+ it runs fast enough to be very playable it does seem a tad bit slow, but that is ok, because I will aim for 15MHz calc's and it will still be fast enough to play. and actually for the running, it does run faster, because it's only testing the X-axis stuff twice, so it's a little bit of slow down, but the speed increase is enough to make that slowdown null.

Don't forget, you can move 1 pixel at a time but update the screen every other time, so it appears you are still moving at 2 pixels per frame, but with the accuracy of 1 pixel per frame and nearly the same speed.  That's what I did for starship.

I actually use both of the previous suggestions in Portal right now It moves at a maximum of 1 pixel per frame, but updates only every other frame.  And the coordinates are stored x64 for more precision, for the acceleration and stuff

cool, can't wait to try ^^

wow nice ^^, just tried it and it's quite fast in SE mode, altough mario looked funny when you held down 2nd, left and right at once