This looks really good!

Indeed I really need to post a news about this soon.

Ben was working on this years ago but stopped, and now he appears to have resumed it.

@Squidgetx Two sizes sounds good for objects, although I wonder if it would look weird with large enemies.

That's an asm engine that was written by benryves that appears to be a true 3d one, (at least a bit more 3d ) since you can look up and down.

Where is that available!

I very much want this

What browser do you use Graph? I think I remember IE for Mac playing animated GIFs slowly and some sites crashing when too many images had to be displayed.

Okay, figured out generally what's wrong with the engine. It involves the necessity of scaling all my numbers by 128*8 rather than 128, so I think the engine will need to be (almost) completely rewritten. It shouldn't be too difficult though

It's getting a *little* hectic. It took me a while to figure out how to accurately compensate for the lack of a tan and cot function , and that's only the tip of the iceberg

I'm going to do some minor improvements and add sprites just for functionality testing, and call it an alpha. Then I'll work on rewiring the engine for less distortion, more accuracy, textures, and a world editor (sprites and map) which will probably be more of an on/off project depending on how things with my other projects are going.

Regarding sprites, do we think it would be better for the user to to have to make like 10 sizes of the same sprite, or only two or three and have the engine scale them by 2x and 4x? It's a question of detail versus less hassle on the user end

It's getting a *little* hectic. It took me a while to figure out how to accurately compensate for the lack of a tan and cot function , and that's only the tip of the iceberg

tan x = sin x / cos x and cot x = cos x / sin x if you didn't already know this.

Sounds great!  I can't wait for more progress.

Regarding sprites, do we think it would be better for the user to to have to make like 10 sizes of the same sprite, or only two or three and have the engine scale them by 2x and 4x? It's a question of detail versus less hassle on the user end

I think the user should have to make multiple copies.  This would be quicker and easier for your code, and also more precise than a general algorithm.