Nice. By the way I tried the raycaster in Wabbitemu and the paths I walked through seemed really narrow. Is that normal?

I think that might be beyond raycasting capabilities, but variable heights by blocks, not slopes, might be possible.

What exactly do you mean by 'curved walls' ?

Also, textures are hard

just my opinion, but will the curved wall be possible later?(Like hills)

Nope. curves cannot be supported by a raycaster due to their nature. the z-axis is locked. all walls must form a 90 degree angle with the floor.

so, no octagon style wall shapes? Or do you mean ceiling parallel to floor?

That would depend on how collision detection worked.

i'm assuming it's by the rays traced. in which case, the ray would trace through a transparent wall as if it weren't there. you'd need two maps. one indicating whether or not you can walk, and on indicating wether or not the ray should be cast for those pixels.

So I'm running into some rather unavoidable issues: the current method of all testing for collision (of both the rays and the player) is with pxl-test on the backbuffer. Yesterday I tried changing the map to bytes, and using basic array checking ({Y*96+X+Pointer}) so that I could then add support for different types of walls (like the transparent ones), and it runs really slow, even after adding Runer's assembly code. I can't think of any way to improve it

It's not unbearably slow, but I can tell that if I decided to add textures or scaled sprites, it probably wouldn't make it

Progress will continue, but at the best I think we're only going to see 4bit variation in the wall 'types' (done by or-ing two buffers over each other)

edit: Another alternative could be to reduce the screen size, like in Gemini, but I'm kind of iffy on that