DIYDoom VS VoxelSpace

Don't sell yourself short, I imagine you could achieve a lot more than you think! It's just a case of breaking the problem down, simplifying accordingly and (probably the most difficult bit) finding the time to sit down and work on it. There are some DIY courses that could even be followed and mashed up to approximate a scriptable "3D" engine with a bit of creativity. You could familiarise yourself with building a simple compiler + VM for a little language by following "Crafting Interpreters" (https://craftinginterpreters.com). For the engine side of things someone recently posted this "DIY Doom" over @ https://github.com/amroibrahim/DIYDoom which looks like a bit of fun.

I mean it's a bit tougher to do it all completely from scratch, but I reckon most HNers could get quite a lot of the way there :)

see also a tutorial on writing a doom-compatible engine from scratch:

https://github.com/amroibrahim/DIYDoom

they also have a community forum, diyidtech, at https://discord.gg/a8n4Y2z

For reference, I want to convert this C++ code (https://github.com/amroibrahim/DIYDoom/tree/master/DIYDOOM/Notes001/notes)

see also: a series of posts (with accompanying code) on rewriting the doom engine from scratch:

https://github.com/amroibrahim/DIYDoom

This uses the "Voxel Space algorithm" used in 1992s Comanche to get a faux 3d terrain. Based on the code from here with some optimizations to get a reasonable FPS.

Reminds me of this: https://github.com/s-macke/VoxelSpace

Another implementation to play around with here; this one's not DOS but web based though.

I'm reminded of the render algorithm in Comanche, the 1992 video game [0]. I find it remarkably ingenious, and it certainly felt incredible at the time.

[0] https://github.com/s-macke/VoxelSpace

The heightmap I've been manipulating may also be familiar to you, but not for the same reason, because it's terrain data of Mt. Fuji. I'm thinking of heightmap files instead of infinite noise, mixing the perks of ray-based rendering insights with a manageable early-'90s-style aesthetic and conventional level design. An erosion simulation could be preprocessed with a seamless OOB margin in that context too.

I wrote a voxel space implementation in Rust some time ago using SFML, and now am trying to move it to WGPU in order to learn how GPUs work better and perhaps solve a horizontal lines glitch I've got.

Recently, I’ve been getting into voxel rendering, and I’ve been thinking of a way of extending the voxel space algorithm. https://github.com/s-macke/VoxelSpace