Oh... Now we're all disappointed. Well, holes are still somewhat useful...

Bwang, I figured it might effect the speed of the engine if you had to use overdraw (the only way I know of to make transparent wall textures) because of the need to continue looping after a wall intersection. But thanks for trying anyways, it's cool that you're listening to my suggestions, as off base as they might be sometimes.

Bwang, I figured it might effect the speed of the engine if you had to use overdraw (the only way I know of to make transparent wall textures) because of the need to continue looping after a wall intersection. But thanks for trying anyways, it's cool that you're listening to my suggestions, as off base as they might be sometimes.

I need to continue looping after a wall intersection anyway, because of the variable-height columns (so a slice of wall may be partially hidden). Right now the problem is if a cube has holes, the engine will try to draw all four faces of the block, which looks terrible. The only way I can think of to remedy this is to make the rendering unit a face of a cube instead of a whole cube, at the expense of making the level format harder to comprehend.
Does anyone have optimizations for the code? Or should I add more comments to make the source more readable?
I might try writing an external level loader next, so textures and maps would no longer be hard-coded.

I can do an animated screenshot, but it will be split in several screenshots. I think ticalc limits each files to 1 MB. An animated screenshot for such thing will hit 1 MB in about 10 seconds.

Do I need to wait for a new version btw? Or do I use latest one?

Ok I'll try to do some screenshots as soon as possible.

They'll run at 10 fps

EDIT: Here are some. Pick your favorites. The two first run at 5 fps, though. The rest are all at 10

Btw you oughta include a readme in the next release with controls so people know what keys does what.

IN later releases, are you planning maybe to have some sort of example mini game, for example, just a small map where you need to find a gun, avoding enemy shots, then reach the end, killing the boss? Just something simple so people see what kind of games could be done

It is so good to start seeing Nspire graphics.
Can you optimize the engine to get some more FPS? (without reducing resolution)

I think a FAT engine (see the FAT engine for 68k calcs, it is the engine that DOA uses) for Nspire will be a great project to open game oriented programming to it.
But from all doubts that bwang has about available C functions, Nspire is not yet an easy calculator to program.