Yeah that's what I mean NIck. The SNES processor isn't even as fast as the TI-83+, let alone the 84+. Collision detection checks are even scrapped sometimes to gain speed, such as when Mario jumps backwards in a corner just below ceiling blocks when crouching, which, as a result, can let you go through walls.

And in most RPGs on the NES/SNES, if you see a tree or bush, you can't even walk right next to it sometimes if the tree doesn't take the entire tile size. Add to that the games where you can't walk behind walls such as Final Fantasy IV. Of course on a Nspire he has more processing power for a game like F-Zero but doing collision detection by tile as complex as it should be would be a shitload of work, with about 128+ if/then/else blocks.

What I suggest is pixel-test for walls, but tile collision for dashes, finish line and jumps.

I'll just go with pixel testing, I want to have a respectable accurance with collisions.

I'm not sure if that's a good idea, as pixel operations are never (on any platform) very fast; it could give quite a blow to performance. But what do I know, doing mode7 already involves a lot of per-pixel stuff and it doesn't seem to be that slow.

Quote from: Matrefeytontias on January 09, 2013, 05:04:41 pm

I'll just go with pixel testing, I want to have a respectable accurance with collisions.

I'm not sure if that's a good idea, as pixel operations are never (on any platform) very fast

Except in some cases on the 83+ (in Axe and TI-BASIC). In TI-BASIC there isn't much difference over using matrices, but in Axe if you need accuracy it's the fastest way.

Why not have a separate collision texture? The Nspire has the RAM to do it. With that you could even have multiple types of surfaces, for example normal track, off-track but still traversable regions that slow you down, and speed boosting surfaces.

Update !

Thanks to hoffa for his help with the nSDL and the port of SDL_image to Nspire, now I can use the original tracks from the first F-Zero as gif files (so 800KB instead of 42MB !!!) !



As ever, new screenshot in the first post but this time I didn't attached the tns since it's so little progress.

Now I'll work on collision detection, I have enough of going through the walls

Also, do you think I should lower the camera a bit or is it ok like it is ?

Do you know the time it takes to shoot a 4MB-large screenshot, convert it from avi to gif and then upload it ?

Anyway, you can see it now

Will you get rid of the huge black area on the left side of the road when the race starts?