puǝ
puǝ
(ɐ)sןǝxıdʍɐɹp
(ʇuǝɯbǝs ɟo ʇɥbıǝɥ)ɹoɟ
ɐ>-ɹoןoɔɔןɐɔ
(13 oʇ 0)ɹoɟ

:buıʞuıɥʇ ɯ,ı ʇɐɥʍ ɹoɟ ǝpoɔopns ǝɯos ǝʞıן

o˙o sןǝxıd ǝɹoɯ oʇ buıʍɐɹp ǝɹɐ noʎ ǝsnɐɔǝq ʎןǝɹǝɯ ssoן pǝǝds ǝɥʇ sı ɹo   ¿ǝɹnʇxǝʇ ǝɥʇ ɟo uoıʇɔǝs ɥɔɐǝ ɹoɟ ǝuo  ¿sǝɯıʇ 23 ʎןuo uɯnןoɔ ɥɔɐǝ ɹoɟ ǝɹnʇxǝʇ ǝɥʇ pǝʇɐןnɔןɐɔ noʎ ɟı dןǝɥ ʇı pןnoʍ

Mmm could you multiply the height of the section by .03125?  Would that be faster than dividing by 32?  This way there wouldnt be any extra calculations for taller columns, only the overhead of drawing the pixels.

Wow the new 32x32 bit textures look great. I would highly suggest studying the code from the FAT engine, it was able to render 64x64 bit textures on a 10mhz calc (although it was only rendering to a 96x96 pixel screen), you've got a lot more processor speed to work with, despite the fact that your engine uses the whole screen, I think you could use some of the optimization concepts from that engine in your code.

Also do you  have a maximum distance for rendering coded in yet? if not you could glean a few FPS's of speed from not even bothering with tiles that are outside of that distance. You probably have, but that's just a thought. At a certain distance and beyond, the walls would all render as a single pixel in each column, so there's no real need to calculate anything at that distance and beyond. It would make more sense to just render a pixel.

Also after a certain distance, you could just abandon textures, and just render the wall as a solid color, like black would be good, because it would appear that you just couldn't see that texture, and it would probably speed things up a bit.

Just a couple of thoughts. I tried writing a raycasting engine for the HP50g once, and only managed to make a really fish-eyed representation of the walls, and only in one color, so I think your expertise in these matters severely outweighs mine

Good work! Keep it up! It won't be long and I might be working on a Wolfenstein port for the nSpire.

Good idea, I'll add the maximum distance code.
calc84: how do you change the CPU clock speed in C?

Just out of curiosity, what do the bits in 0x00000002 and 0x00141002 do?

(on a offtopic note I wonder where SuperKoolkid went..., his engine would have been amazing. Only Calc84maniac did that besides SKK and he didn't release a demo yet, not to mention it's dormant

Is it a calc-only feature or will it work on emulator too?

Very very impressive project thus far.

Question I have is will it support being able to look up and down? A user on my forums (SuperKoolKid) was going to make an engine for the 68k that allowed that, but he has seemingly stopped the project due to not having the time or motivation to work on it.

If you did, we could have some really epic games made.

I fairly sure no matter what epic games are in the near future