Well, I dont know whether or not the FAT engine was written in pure ASM or not but C should do just fine if I do it right.

NEWS:

New menu system is done. Now when you are in-game, the menu floats on top of the viewing plane in the original font. Ranman helped me with the font system. It looks pretty sweet.  

It might, I think I hotlinked it from UTI. It really doesnt matter much to me. I'll think of something.

Anywho, I looked into the advanced raycasting and I understand it to a point. If anyone here can help me find some tutorials on drawing a raycasted scene to a flat screen, please post the links here.

I'm going to go on Amazon and see if I can't find some books on the subject also. I think I may actually be crazy enough to attempt this.

I need to get my head examined.

EDIT:

Okay, I found Doom's Original source code. I'm going to study their methods, and see if I can learn a thing or two.  

The Zombies show up a little later, around level 3. The exposion thing applies to all the characters because of the amount of space required to store all the death scenes for all the enemies. Four frames per death animation and 4 normal enemies, means 16 frames, at 64*64 pixels each times two planes.

That would equal around 32768 bytes, and then add on to that another 32768 bytes for the normal animations. Now we're up to 65536 bytes , plus two extra frames for the attacks times 4 would equal another 65536 bytes, so now we're up to 131072 bytes. Thats just for the enemies, now the tiles. There are about 72 or so of them. That equals 147456 bytes and add that to the 131072 bytes, which equals 278528 bytes, then add the fat engine which is ~55kb.

Now we're up to ~333528 bytes. Now add the 47982 bytes for the doom game engine. Now we're up to 381510 bytes, now add the 17kb map file, the 7kb text file, and the 8332 byte save file and we're up to 413842 bytes, plus the 1002 byte run game program.

414844 bytes all together.

that figure is without all the add ons and optimizations I have so far.

the actual figure of space is 452341 bytes.

So, if i were to add all the normal death animations, it'd be;

485109 bytes.

Also, the fireballs thing may be in the future, but right now I'm not sure really what I'm going to do about that. It'd require a good bit of RAM to keep up with the location and status of the fireballs. Plus the way the imps are set up right now, they come kind of close to you and start scratching, so it looks more normal.

I'll give it some thought, see what I can come up with and then get back to you on that one. It'd also require around 8 sprites or so, so that the fireballs are multidirectional like in the real game.

I am working around a lot of restrictions because of the small platform. While the 68k series is certainly a powerful platform, its still small.

Yes there are, there's a bunch of them, in fact I have one that converts Doom2 to a raytracer version of goldeneye.

NEWS:

I will be releasing a 28 level public beta soon, It has entered testing today and I expect that it should be ready for release in a couple of weeks at the most.

Yeah, that sounds right, it says it should run about 20 - 40 MHz
thats fast! 89 HW2 == ~12 MHz o.o

I dont know but from the graphing speed I'd say yes.  

Yea, go figure, and I program for calculators.

HAHA! Voyage 400. I remember that Ticalc joke. That would be majorly cool though.

Hey, I've been trying to find a good HP emulator and ROM for the 50g or 49 series. The ROMs are freely distributable according to HP's license but I can't seem to find any. Can anyone help me out? I want to see what the HP calcs offer.