RWAP wrote:Another really good start - although I find it rather difficult to spot the gaps in the walls sometimes - maybe you need an upright line to define the ends of the wall?
It's all pretty work-in-progress at the moment. The texturing is now better than it was in that video, but there is obviously room for improvement, which I'll come back to once other sections of the engine are in place, such as...
yerzmyey wrote:I presume there will be some full version with monsters (even if levels would be multiloaded on 16K, I'd go for it).
I'm currently working on the logic for enemies/monsters. Like all of this engine, how to do it isn't the problem, but rather how to do it quickly on a ZX81. It's possible that the calculations for monsters might mean that other features might be dropped, such as...
BrunoFlorindo wrote:The fact that this is possible on a ZX81 is impressive indeed. If the walls didn't had any bricks and were just defined by their outline, how much faster would it be? I understand you need some texture in order to show movement, but maybe you don't need full brick walls.
The first video on the page is of the engine in wireframe, and if I went the full way to an optimised wireframe solution it would be faster than the current textured version (although not hugely faster as a lot of the time is taking with the ray casting, and the logic behind a proper bitmap display) but require a completely different code base for the wall rendering. I wanted to try for the texturing if I could, just to see if it could be done...
yerzmyey wrote:Bricks, bricks, bricks!!
Hehehehe.
Of course I mean any nice low-res textures. I think it's not slow at all.
At the moment anyway (without monsters
).
Indeed. The current code base is slightly faster than the video, and I'm working on the monsters at the moment.
Indeed potentially better!
