I finally got around to writing some code for my Nspire raycaster project. Right now it is shamefully featureless, as it basically draws untextured walls from a scene defined by a hard-coded array in the source:

The big problem I'm having right now is getting the animation not to flicker (the above screenshot was not animated). Does anyone here (maybe calc84maniac?) know how to do flickerless animation on the Nspire?
Once I get the animation working, I'll add other things, like texture mapping and sprites. Also, does anyine know how to pause execution for a specified amount of time (so I can limit the frame rate)? Right now, from my preliminary flickery code, it seems like I have plenty of speed to work with.

Nice, glad to see you got this working.  Did you end up using the small step or the vertical/horizontile method?  Judging from the side shading on the walls I'm guessig it's the latter?  Looks good

Seems you might have a case value for the column directly in front of the camera maybe offset all of the columns by .5 degrees?

Great!

I've got one little additional remark: most of the screen is left unused. I've never written raycasting/raytracing code, but is there a reason?

As for flickering, calc84 should know, he wrote the GBC emulator and such.

Keep in mind, though, that the Nspire is 90 MHz (or more?) while the 83+ is 6 MHz.

I think I can implement variable wall heights. The emptyness of the screen is because my walls are not very high, which is easily fixed. Right now, my biggest priority is figuring out how to get smooth motion.

From what I have right now, I think I have plenty of speed left, especially since I haven't started optimizing yet.

Once I get texture mapping done, it will support 16 shades. Right now, there are only two shades.

A question: in src/arm/headers/common.h in the Ndless package, there are several keycodes. Does anyone know where I can find more of these codes? Also, are the direction keys also considered keys, or is it some sort of analog device with infinitely many directions?

aaah ok, I was unsure. 4 levels of gray would be ok, though. Even monochrome, altough it wouldn't be pushing the Nspire to its limits as much . But we have to start small when coding anyway, IMHO. It's good to be ambitious, sometimes, but we have to make sure to not be way too ambitious either. ^^

Some people who are totally new at something will sometimes go with the largest possible RPG project, then realize it was too much for them . I usually start with something small, see if I can do it, then expand.

16-level gray is pretty easy to do, considering the Nspire has hardware grayscale support.
I don't feel this project is terribly ambitious yet. Notice I have absolutely nothing planned for gameplay--right now, I'm just experimenting with raycasting.