too bad, I would be fine with the fast old version instead.

but great job anyways so far, I could never do most of this.

good luck!

Here it is: Doom 83, French version.

However, I really suck in the emulator.

Wow this is ancient. . There's a much up to date version called zDoom on ticalc.org. It still has some glitches, though. Cool game nonetheless. I wish it was finished. I remember reading the site regularly back in 2001 and 2002. http://doom83.free.fr/

A website for a calculator game? Wow, that's epic

96 isn't on the auto optimization list, try doing *32*3 instead and it should be much faster Technically speaking, pixel testing is usually slower than byte reading, since with pixel testing you are doing bit shifts and bit testing.  also, if your map was like 64x64, it would be even faster since you could then do *64 which is extremely fast

On a related note, check out this FPS that BenRyves Made

Right here http://www.benryves.com/

Holy crap.

btw, I'm going to clarify in case this wasn't clear from the beginning, this project is intended to allow other people to make 3d games with Axe, it's an engine. Of course, I might end up making something with it myself, but it is open source and anyone can use the code to make their own game as long as you credit me appropriately

Couldn't you just reduce the resolution, but not the screen size? That might double the speed. However, textures aren't really necessary I think. Do you think adding sprites would be hard, btw? (If they are scaled, I would recommend that each possible zoom is pre-rendered and stored into memory prior starting a level to speed rendering up.

That's an interesting idea, and wouldn't be hard to implement. Sprites I think wouldn't be too hard as long as they are prerendered to a specific set of sizes. I think it should support a couple sizes: probably two sizes, large and small. (as in a small object like the barrels in Doom and the big enemies along with their respective zoom levels) What do you guys think?

Also I will try that optimization, and probably will change the map to 64x64. I was surprised that the byte checking was so much slower as well. However all these changes will mean that I'm going to have to create a map editor/sprite editor, which might take a little while.

EDIT: However, first I want to tighten up the raycasting process as described on the 1st page by Runer112, and get rid of the fishbowl effect. Also I think I get how to do textures now, but I have to do the above stuff first

This looks really good!