r/proceduralgeneration

Basically it’s a wireframe toroid drawn in a vector program I created , but it has a limiter that hard stops the edges I discovered if I gave the limiter a negative value it indebted the outer regions to get this cool pinched look. Plotted light green for two reasons 1: wife said use light green lol 2: CRT aesthetic ;)

My game is fully procedurally generated, with each cell having a genome that drives the expression of organelles and phenotypic traits. Everything you see is generated and simulated at run time, all the way down to the cell's organelles. The playtest is open to anyone who wants to try it out, you can find it here

I finally finished my big project! You can watch my workflow with this asset here!

Here is my Gumroad

and Instagram

thank you for watching!

The game is called fish lab , and it has basically no bitmap assets , Besides some icons and title screen

There will be a steam demo may 18th

Back in January, I shared a prototype of my procedural mountain generation here. Over the past few months, I added side faces to the hexes and implemented water. Water hex cuts turned out to be trickier than expected, but I think it works now.

Water hexes are actually less procedural than the mountains. I split the generation pipeline into several stages:

1. First, I generate the coastline (essentially a set of 2D points within the hex).

2. Then I compute depth values for each vertex inside the coastline.

3. Finally, I generate side faces where needed.

On top of that, I generate the water mesh itself, plus side faces for water if required.

I struggled quite a bit with coastline generation. Conceptually it's just a set of points on a plane, but getting good results wasn't easy. I went through ~5 iterations trying different approaches. The main issues were either visible seams between adjacent hexes or unnatural-looking shapes.

In the end, I switched to a hybrid approach: I defined fixed connection points on hex borders and manually authored a set of coastline templates that snap to those points. This gave me much more control. Variation comes from randomly selecting a template from the pool.

This decision was partly inspired by how water seems to be handled in Dorfromantik - with the difference that they appear to pre-author full 3D variations, while I only define 2D curves and generate meshes from them.

As a next step, I'm considering loosening the constraints a bit - e.g., allowing slight random offsets for connection points and interpolating segments of the coastline to get smoother transitions.

I realize this post is quite technical - if anyone wants more details, feel free to ask in the comments. I can share more breakdowns and screenshots (always easier to explain visually).

Also, I recently put together a small team and we're going to try turning this into a full game. We're working on it in our spare time, but trying to make steady progress.

The project is called Hexscapes - let's see where it goes :)

Eulerian grid-based smoke sim running real-time on the GPU.

What's under the hood:

- Semi-Lagrangian advection

- Gauss-Seidel pressure solve with SOR

- Vorticity confinement + buoyancy

- CUDA/OpenGL interop (zero-copy rendering)

Every kernel handwritten in CUDA. Every equation derived from scratch.

Source: https://github.com/NobodyBuilds/smoke\_simulation

I'm working on a procedural city generation for my roguelike game. Early stage but pretty proud of how it's turning out.

was experimenting with mold growth for my fruits

I’m working on my own role-playing game inspired by Wizardry 8 and Might & Magic 6. Since I chose the desert as the first biome, I’ve focused on optimizing procedural generation specifically for it. You can see the result in the video.

I experimented with various generation techniques, including vertex shader–based terrain generation - using a mesh that covered the required area, with a shader applying vertex transformations. In practice, the mesh itself stayed in place as the camera moved; only the vertices changed, creating the illusion of movement. However, this turned out to be slightly more expensive than generating the terrain dynamically on the CPU, since the vertex shader processes every vertex each frame. With CPU-based mesh generation, no recomputation happens for the entire lifetime of a chunk.

Chunks themselves are stored in a pool and reused: as the camera moves forward by one chunk's size, a new line of chunks is created ahead, while a line of chunks behind the camera is released and returned to the pool. New chunk generation is spread across several frames to keep the framerate perfectly stable. Generating everything in a single frame is possible, but can cause occasional drops.

At 800p (16:10), my modest MacBook Air M3 with 8 GB of memory pushes over 1,100 FPS - even with real-time terrain generation on a single CPU thread. The dunes come with collision meshes, so you can walk on them. 520k+ primitives drawn, ~65 draw calls. Draw distance is ~1,800 meters, flight speed is 500 m/s, and altitude is 60 meters.

This is an actual 3D procedural volumetric shader of NGC 6302-like nebula.

https://chilly-chili.itch.io/wayfarer

Made a pixelated planet generator (inspired by that one really great post from ages ago) as a late submission for Procjam and might have slightly missed the deadline. Proud of how it came out, but I think it still needs tweaking, too many planets come out as uninteresting "blobs" due to a mix of low frequency + 1 octave + a dull palette.

Works on shader magic and otherwise totally standard noise-based map generation on a sphere.

Blender Guru said a traffic cone costs $3,600. So I built an Infinite Money Glitch (Procedural Cone Generator). Free download in comments.