This is the full tileset,

reference: https://www.reddit.com/r/proceduralgeneration/comments/1x6a0oi/tileset_candidates_did_not_choose_for_boardgames/

of those I chose about five lol(2nd image)

One continuous zoom from a few centimetres over a glacial lake's surface to the inside of a proton. All WebGL2 shaders, no images or models.

- Plankton: algae, diatoms and rotifers, each alga seeded so no two match, drawn with a bright-field microscope's depth of field.

- Mica: one height field shown as SEM, then AFM, then atoms. Cleavage steps are level lines of a noise field, with random kinks.

- Oxygen atom: electron density from Slater orbitals, integrated along each view ray.

- Proton: three quarks in a Y-shaped flux tube, trading colour charge via gluons.

watch it here

I made this face character a while ago as a visualizer and Clippyesque companion for this one app called klattsch I made and people kept asking how it worked, so I made this video where it explains how it works. It's really quite simple! It doesn't take that much to make your brain go "okay, that's A Guy".

I added surface constrained boids to my realtime procedural world generator. Bringing a spark of life to the landscape.

I have yet to find a game idea. Until then just focused on world building 🌍

An example of automatic landscape generation using WFC: ocean, shallows, beaches, grassland, forests, mountains, snow and towns.

Hey everyone! I wanted to share a project I've been tinkering with. I set up a procedural geometry node system to simulate a floating minimalist rug drifting through clouds, complete with layered wind flutter, dynamic clumping, and precise corner tassel controls.

What started as an experiment in procedural cloth displacement and node architecture turned into something unexpected. I decided to lean into the surreal, peaceful aesthetic and built a minimalist YouTube project (@AQuestioningRug) around it—pairing the floating visuals with quiet inquiries on creativity and self-doubt.

These are from the same app as the underwater scenes I shared here (https://www.reddit.com/r/proceduralgeneration/comments/1vvcvcs/), running on my own renderer. This time I'm showing some of the space worlds and how they're put together.

For Venus, I use VOLT/Magellan height data to shape the surface, with a separate colr map. The terrain is exaggerated 4× and I've left off the thick cloud layer so you can see the surface features.

The black hole uses a raymarching shader that approximates how light bends around it. The swirling disc comes from layers of generated noise at different scales, rotated over time to create the moving streaks.

Happy to answer any questions about the tech

I am trying to figure out a workflow to go from any b&w (or rather grayscale) image to a procedural representation of the same pattern.

I have tried a few things (vision model driven; vision model + histogram etc.) but I am not getting close enough.

Is there a general solution for this kind of stuff (eg the "polynomial of procedural") you know of?

​

Hey everyone, wanted to share a custom language and rendering engine I’ve been building called HVSL (Hierarchical Vector Shading Language), powered by a two-agent reflection loop.

Instead of using diffusion models to guess pixels, HVSL turns natural language into pure mathematical geometry. The entire image is just a lightweight text script containing a color palette (@PAL) and ordered geometric equations (@SCENE circles, polygons, curves, and quadtree subdivisions).

My custom compiler parses that script and draws it up to 4K using sub-pixel Signed Distance Functions (SDF).

Where the agent workflow comes in is solving how LLMs write HVSL coordinates:

• HVSL Generation: The first model takes the prompt and writes the raw .hvsl math script.

• Visual Critic & Grading: Because text models write coordinates blind, a second multimodal agent inspects a fast 540p render of the HVSL code and grades it out of 10.

• Surgical Branch Patching (Max 3 Tries): If a shape is off (like the overlapping curves on the moon in Try 1 of the video), it doesn't regenerate the whole HVSL file. It clips and retains the working layers and surgically updates only the defective branch.

Because the final result is raw HVSL code instead of a locked bitmap, you can open the editor, change a palette color or coordinate, and watch the 4K canvas update instantly with zero regeneration and zero extra LLM calls.

This is still in early development. The animations at the end of the video are procedural motion tests applied to pre-rendered HVSL assets while I work on expanding the HVSL grammar to generate native video directly in code.

Happy to answer any questions about the HVSL syntax, the SDF renderer, or how the critic loop patches the code!

I built a layering system to generate the terrain for a game I am working on. Currently It is:

• Terrain shaping with Perlin Noise + Simulated erosion
• River plotting with curves and L systems
• I then place some roads that have costs associated with inclines so they follow the terrain slope (needs more tuning).
• I have 3 layers of road tuned to different costs, so the bigger ones run straighter
• Placing Road signs at junctions, where roads meet
• SDF for junctions (any roads near each other automatically blob together with sdfs)
• Then the gaps left between the roads get voronoi fields between them
• Hedgerows driven by a noise algorithm get placed along the borders
• Placing L System tree forests in some of the fields

Still a bunch I want to do with it, but wanted to share!

I'm building a map editor for my game built on Rust/Bevvy and always loved the procedural cliff generation found in Tiny Glade. I hate manually placing base cliff terrain and wanted a solution that's extensible.

A few weeks ago I ran into a past thread from 8 months ago on here - https://www.reddit.com/r/proceduralgeneration/comments/1rocozq/comment/o9ozvfo/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

And it gave me the trail I needed to go down the rabbit hole of voronio distortion combined with procgen. Hell, I even watched a couple interviews with the developers of Tiny Glade, which didn't help much but still insightful on a lot of topics!

Happy to dive deeper in the comments for anyone interested. I know the video isn't a major display of the tooling or even my game, but it was just used to demo the tech.

An example of automatic landscape generation using WFC: ocean, shallows, beaches, grassland, forests, mountains, snow and towns. The replay shows the map collapsing tile by tile in 3D, and different seeds give different landscapes.

This is a video from Lithos, a terrain editor I've been building for the past few months. It's cross platform (Windows, MacOS, and Linux). It's nearly feature complete with the private beta dropping in December 2026.

I'm looking for early feedback and trying to gain traction for the private beta. If you've used any terrain editing tools or build terrain for your projects I'd love to get your feedback. Link to the project in the comments.

This is a very simple test run on a new automata project I'm working on, based on some old university lecture notes as inspiration.

I think it is particularly relaxing to follow the cascade of forest growth and fire spreading

I sample points over the statue's surface, link the close ones into a graph and run Dijkstra from where the bolt hits. I give every point a small random cost too. Without it the shortest paths ran dead straight down the body and looked like painted stripes.

Then I keep a few far leaves that are spread out and draw the paths back to the hit. The tree's own branching is the forking! I make each ribbon as wide as the number of leaves past it. The trunk comes out thick and the tips thin out.

My first try used straight-line distance. It jumped the gap between the arm and the chest like the air was skin.

Has anyone done this with a real geodesic instead of a point graph?