I had a crazy idea. Builder boy wrote portal X to run at 9fps on a z80 running at 15mhz and with 24kB of ram.  Well the N-spire has 90mhz processor, 32MB of ram and an OS that is a million times more intelligent than the TI 84's. (nucleus itself not the TI front end) to put things in perspective the N-spires processor it clocked 18 times faster then the 84 and is a better architecture plus its 32 bit as opposed to 8 bit we are talking around 50 times the computational power of the 84 and over 1186 times the memory. with this kind of memory it should be possible to write a full 3d portal running at 30 fps interlaced. (because the screen is fine enough that it can be gotten away with)
To give a comparison the Nintendo DS has about the same if not less processor power, spread across to processors so there is extra overhead of coordination, then the N-spire and one 4mb of ram + 656k of video ram to the N-spires 32MB (including OS space). 3d rendering a physics are completely possible on the N-spire and portal is only a tiny bit of a strech

the only thing the ds has on the nspire is the video ram and plus bwag's already got a raycaster

I'm not sure my raycaster can handle scenes of that complexity and still run at reasonable speed
The DS has more that just video RAM; it also has an entire GPU doing the 3D transformations and texture mapping.

portal plus raycasting might be a bit hectic to make, especially when shooting portals on the floor. I think you wouldnt even be able to see through portals until you get through it (you would then be warped on the other side).

As for the FPS, it would also need to be dropped to like 15 FPS because the Nspire LCD is too blurry to have anything of higher FPS look good. When turning around in Bwang's raycaster, we have trouble seeing stuff if we're viewing an area that renders very fast

I actually thought about interlacing the other day. It could maybe work, actually, and speed things up a lot.

What do you mean by interlacing? Do you mean draw different sets of columns every other frame (so this frame I'd draw columns 0, 2, 4, ... and next frame I'd draw columns 1, 3, 5, 7, ...)?

Exactly.

kinda like old TVs

It would still need to use something else than raycasting, though. I am uncertain raycasting can be vertically wire-frame. Just see in old versions of Bwang raycaster how distorted things can get when looking up/down very high/low.

Basically real 3D could be used. real 3D would be possible, too. With several polygons, Calc84maniac got about 70 FPS on his 3D wireframe engine. That was without textures and polygon sorting, though, and I think the engine is discontinued.

I would like to see more Nspire 3D dev in the future, even if Ndless 2.0 was to be discontinued or end up unavailable forever, because there's lot of potential