r/proceduralgeneration • • 1h ago

Rate my procedural animals in my space exploration game

Thumbnail
gallery
26 Upvotes

made these for my space game, all generated from genes. how do they look? still a work in progress


r/proceduralgeneration • • 8h ago

Procedurally generated galaxies

31 Upvotes

r/proceduralgeneration • • 9h ago

Wednesday update: Three.js Crashing waves

18 Upvotes

Added transparent water and procedural wave sounds. Next up will be foam particles.


r/proceduralgeneration • • 6h ago

I built a procedural generator that rolls an alien and two attacks with one click

Post image
6 Upvotes

Each panel in the GIF is me hitting Randomize in TerraForge, the engine I built for my game, TerraHeist. Each roll generates a creature and two attacks.

The part I’ve had the most fun with is making the attacks play differently, not just look different. Two rolls can pull from the same attack family, but the projectiles can move differently or fire at different times, and have different effects/visuals. The creatures and attacks in the GIF are generated using code and math rules, not generative AI.

When you find a creature in TerraHeist, you can recruit it as a companion or steal one of its attacks and socket it into your own weapons.


r/proceduralgeneration • • 7h ago

How do you make procedurally generated areas feel natural rather than random?

4 Upvotes

How do you make procedurally generated areas feel natural rather than random?

I'm working on Ars, a 2D roguelike set in alien ecosystems, focused on survival and exploration. Each biome has its own vegetation, creatures and points of interest.

The world is divided into small procedurally generated areas. I'm trying to find a good way to arrange their contents so that each area feels like a natural-looking environment, rather than just a random collection of objects.

I'd like to have a mix of open and dense spaces, clearings, irregular vegetation clusters and natural passages. The layouts should make sense for the environment, while still being varied from one area to another.

This also affects gameplay: the arrangement of elements influences movement, visibility, exploration and encounters with creatures.

For those of you who have worked on procedural environments, how have you approached this? Do you rely on algorithms, placement rules, or a combination of both?


r/proceduralgeneration • • 2h ago

Polishing sound generator for my graphics engine

1 Upvotes

r/proceduralgeneration • • 20h ago

Thoughts on UPDATED procedural generated maps for card battler : Zoomalia

17 Upvotes

Genuinely looking for any criticisms people may have. This is an overhaul based from the criticisms from my last post a while back (check on page). This is for a creature collecting auto battler as well, the other main part of the game is rts style take over.

  • Would this be something you would expect in a shipped game?
  • Are there things that look like they should be removed, added, etc?
  • What do you like/don't like?

Thank you everyone for any feedback, it means a lot and helps devs like me out a ton.
If your interested game link (Zoomalia) : https://store.steampowered.com/app/4153900/Zoomalia/


r/proceduralgeneration • • 1d ago

Procedurally generating details for real map data

37 Upvotes

I'm using Claude Haiku to automatically extract structured descriptions of building facades from street-level 360 panorama photos, to be painted as procedural textures and decals on extruded OpenStreetMap buildings. They certainly don't look perfect, but seem recognizable, render fast and take less space than equally sharp-looking photo-based textures.

There's also bridge, tunnel and fence meshes generated on the fly from OSM data. Street furniture, vehicles and hundreds of plant species were modeled in code using GPT Astra. It runs in the browser using WebGL 2, also on my old iPhone 11 (though with short draw distance).

Still a work in progress, so for now the map only covers Scandinavia and Baltic countries, with facades only in one city (Porvoo). I'm working on global coverage for the map and more varied test areas for the procedural facades.


r/proceduralgeneration • • 50m ago

(AI) A game with a galaxy of 150 million star systems in a 299 kB HTML file

0 Upvotes

PLAY THE GAME - GitHub

I vibe-coded Voidstruck over 4 days. It's a procedural space exploration game with 150 million star systems, fitting into one 299 kB HTML file that runs in your browser.

Every planet can be landed on (except for gas giants). You can fly low over and step out to explore on foot and by jetpack.

Every star, planet, moon and name is generated from a seed as the player progresses. There are no images, models, audio files or libraries.

The story: A jump drive test goes wrong and throws you 2,500 light years from home. You make your way back one jump at a time, but every jump costs years on Earth. Messages from home reach you along the way, and what you find when you land depends on your actions.

On the way you can refuel in a star’s glow, pass pulsars, white dwarfs and black holes, each with its own look and music. There are eight kinds of worlds, from ocean and lava to crystal and living ones, with plants, animals, weather, and day and night. You can also mine, build bases that earn credits while you travel, upgrade your ship at stations, and fight or flee raiders. The galaxy also features our own solar system. There are four ships to choose from and a one-life hardcore mode, and the ten music pieces are synthesised live in the browser.

The inspiration came from my obvious passion for space exploration games like No Man’s Sky and Elite Dangerous. But recently, Abyssal Garden, made by a fellow redditor, opened my eyes and gave me a huge push to actually create it.

I made the taste calls, Claude (Fable 5.2) wrote the code. Music was one of the challenges, since Claude can’t "hear" what it writes, so I described tracks I love and chose by ear.

It works best in Chrome or Edge on a desktop, full screen, with sound on. It needs WebGPU, so it won’t run on phones, and I haven’t tested Firefox or Safari.

It’s free, with no ads and no account, and you can play it offline. If something breaks or feels off, please tell me.


r/proceduralgeneration • • 23h ago

huh, what might have hatched there? :-S

23 Upvotes

r/proceduralgeneration • • 1d ago

[OC] Magna Urbis V2 alpha is out! (region/city procedural generator)

Thumbnail
gallery
43 Upvotes

For those who don't want to read:

For the others:

I've been rushing development like a madman, and even if I ended up spending about 70% of my time only on generation and rendering optimization,

Magna Urbis V2 alpha is officially out!

Before starting, alpha version means:

  • Updates anytime. No backward compatibility on updates: formats, codes, etc. may loose compatibility and break. Anytime !
  • Things can crash, freeze, run at 3 FPS, or produce complete nonsense.
  • Some features are barely tested, some are known to be totally unstable (but overrall it should run).

Features in this version

Cities & buildings

  • 115 architectural cultures, covering medieval, fantasy and even some modern, and sci-fi cities. Modern and sci-fi styles generally need larger cities or change in parameters to look a bit recognizable :) .
  • Isolated buildings, landmarks, and monuments.
  • Configurable land-use distributions with quantified models (ressources, etc.)

Terrain generation

  • Procedural, neural, or imported heightmaps, with 12 terrain configurations.
  • A quick note about neural generation: it's based on the awesome InfiniteDiffusion models (https://xandergos.github.io/terrain-diffusion/), but I worked to make it run in a browser. Homemade Rust/WebGPU inference that execute directly in the brower with custom-distilled models and weights to reach 150Mo instead of more than 1Go. I've speed up the neural inference as much as I could on browsers but don't expect a miracle.
  • If you don't have a decent GPU, I'd recommend sticking to procedural generation. It's not quite as good, but it still gets the job done.
  • With a good GPU, neural terrain generation can comfortably handle regions up to 200 × 200 km on desktop app, 40km x 40km in the browser with webgpu inference is also fast.
  • Desktop app is more advanced on this one problem but ... see below.

Rendering

  • 6-8 rendering styles. I've implemented what I judged interesting, but this is definitely an area where I'd love your feedback.
  • In particular, if you have suggestions for improving the realism of the Satellite renderer, I'm all ears. My original goal with my other projects like Neural Earth, was to eventually get something approaching a Google Earth-style experience on a procedural world. Still a loooong way to go, though. :D

Editing

  • Basic editing: you can reroll individual components of the generation.

Exports & saving

  • Basic exports: PNG, SVG, internal formats, heightmap.
  • Basic save/load support... which, to be perfectly honest, I haven't actually tested yet. :D Don't think it works well
  • For unedited generations, share codes should work reasonably well. Proper saving and compatibility handling are on the roadmap.

Desktop version

I haven't even properly tested the desktop build. I basically reused my old local v1 build and hoped for the best.

So, use it at your own risk. :D But Sol worked well so I'm pretty sure it will do its job.

If it runs, it should be significantly faster than the web version, thanks to multithreading, native Rust engine, Vulkan and if you have a pytorch environment installed, Python backend for neural nets (works a bit faster than Rust engine).

There is no proper update mechanism yet (or is there? I genuinely haven't checked), and almost zero testing.

macOS support is deferred for now. It requires me spending time making my gpu code compatible with Metal, and to be honest, as I have no macos around me, it involves working through loops with github actions and it's tedious.

A few words about WebGPU and performance

A little technical story here.

Originally, I had a massive shader (several MB of code) that Vulkan could compile in about 4 seconds.

Direct3D? Eigth to twenty minutes depending on the day and the mood...

That was super fun times...

I eventually broke the whole thing into a bunch of smaller shaders, which brought Direct3D compilation times much closer to Vulkan. Not quite there yet, though, and Vulkan still seems to perform better on my setup.

So, if you're using Chrome or Edge on Windows, you might get better performance by switching WebGPU to the Vulkan backend instead of the default Direct3D 12 backend.

If none of that means anything to you and the webapp feels slow, just Google "Chrome enable Vulkan". If your hardware and drivers support it, it might help.

No guarantees, though. And I wouldn't be surprised if the results vary wildly between GPUs.

If you want to be sure, go Desktop version, if it runs, it will be faster for sure.

But if your browser doesn't support WebGPU (which should be very rare), well, grab a coffee and pray it stays responsive.

What's planned for future versions and iterations ?

The following features are already on my roadmap, so there's no need to request them again (unless you have particularly interesting suggestions about how they should work).

Bug reports, on the other hand, are very welcome! Especially reproducible ones. I already know about quite a few issues, but I'm sure you'll find plenty more creative ways to break things (please report issues on the github page).

Features:

  • Documentation: actual explanations of what all those parameters do. I know document is sooo 2025 but I'm old school.
  • Integration with Azgaar's Fantasy Map Generator.: Azgaar is doing an incredible job, Magna Urbis could work as an alternative of the Watabou City generator (which was actually what inspired me to create Magna Urbis ! Hats off, Watabou!)
  • Real desktop release: multithreading, native Rust backend for generation, native Python backend, native terrain model. And all with a nice auto-installer.
  • Advanced exports: OBJ, SVG, GIS (maybe?), and more (don't know yet what may be interesting).
  • Advanced heightmap and coasts editing.: for now it's shitty but I can do a little better.
  • Advanced city geometry and growth behavior editing: I may include a city growth timeline which produce pretty good results in the prototypes but change a little the overrall city shapes and ofc is compute-expensive
  • Advanced toponym generation and editing.: I have a project dedicated to that (namebench), I may include parts of it in Magna Urbis
  • Building interiors / floor plans.: I have the basics done but I'm not sure if something really interesting is achievable without heavy workload though.
  • Fill the descriptions and metadata of magna urbis objects: activities, floor area, inhabitants, etc. Bsically to convert numerical parameters of generation into something human readable (already half-done), and a region with lot of minerals will have more mines and carries for instance.
  • Illustration-style rendering: brush-based renderers. I've removed the current one because it's honestly a joke but I have old projects with really nice looking maps so I'll try to fit that in Magna Urbis.
  • Lots of polishing: both generation and rendering engines still need plenty of love. Many roads anomalies or inconsistencies, same for city plans, rivers, etc. It could be better overrall but now I'm walking on eggs when changing the logic of generation because any small change has to be validated against the thousand of possible generation combination (culture x region x size).

When will it be "really" released? Don't ask, I have absolutely no idea.

But as I don't know what to do next, you're welcome to post a message if you want one of these features implemented first.

Last things, Magna Urbis is completely free and open source and will stay free and OS. This is just one of my hobby project that got a little out of hand. It also means that collaborators and Pull Requests are greatly appreciated.

Feature suggestions are welcome too, particularly for things that aren't already on the roadmap.

enjoy !


r/proceduralgeneration • • 19h ago

[PAID] Built a procedural Douglas fir generator in Houdini: growth presets, 4 LODs, USD proxy export, and sim-ready skeletons

Post image
4 Upvotes

r/proceduralgeneration • • 23h ago

Clouds Rendering in NervLand - Second Stage

8 Upvotes

r/proceduralgeneration • • 14h ago

Teskooano: Terra Firma - Infinite N-Body systems where you can visit any body, even drive on them - all in the browser

Thumbnail
gallery
1 Upvotes

I've been working on this project for a couple of years now and it's finally getting to a point I'm happy with it - Teskooano has both hand-crafted system - Sol, and many from Sci-Fi like Trisolaris or The Twelve Colonies with procedural generation across all the bodies, and random systems generated from any seed - you can visit it to day https://teskooano.space/ and play in your browser.

For stars, each stellar type has it's own renderer, you can fly into gas giants and rings, and any solid body you can drive on with the buggy. Everything is web-based so you can also use URL bookmarks to revisit any scene.


r/proceduralgeneration • • 1d ago

Infinite Gen 3 Pokemon Inspired World Map

47 Upvotes

This is a project I've been working on on and off again since 2019. The world here can be generated consistently in any direction and any order -- everything is uniquely determined by the world seed in advance.

I'm standing on shoulders of giants here -- I started this project when I came across Porygion and wanted to understand how it worked, and then find a way to improve on it and make it my own. I also was heavily inspired by this video on using layers/tiles to create infinite, graph based worlds.

I know a lot of games do something similar when generating infinite worlds, but I'm proud of how my approach lets me compose graph, pathfinding, and clustering algorithms during world generation. The particular way I'm generating cities and routes involved running a K-Means-like clustering algorithm to space cities, flood fills to identify features like mountains and lakes, Delaunay Triangulation and a Kruskal's like algorithm to pick which cities should be connected by routes, and A* to find the specific route layouts that cleanly overlap and interact with each other. Each of them was a challenge to adapt so they could run on a local neighborhood in a way guaranteed to produce globally consistent results no matter what order tiles were generated in. However, now that I have them, I can operate on these infinite, embedded graphs during the whole process, which lets me bring a lot of richness to the constraints.

I plan to keep working on this, and maybe put it online somewhere eventually. I have so many ideas and improvements I'd love to make, but its been more than 7 years, and this is the first time I've felt like it's in a sharable state, so I wanted to post a WIP.


r/proceduralgeneration • • 1d ago

Need help building a Survival Horror Level Generator in UE5

Thumbnail gallery
4 Upvotes

r/proceduralgeneration • • 1d ago

Everyone making their own planet/environment/engine I wish you would all pool your resources into one giant planet project.

31 Upvotes

I see a lot of people making similar projects. And of course everyone has their own personal preferences and styles they want to build for themselves. But I can’t help wonder what awesome group project you would all be able to make if you combined all the things you’ve learnt and made.

Imagine an open source planet where devs could all help build and add complexity. I’m sure there probably are some projects like this? Can’t be worse than what meta tried to put together 😂


r/proceduralgeneration • • 1d ago

Full size procedurally generated planets in my survival sandbox game

Thumbnail
gallery
44 Upvotes

Steadfall's world is a cube sphere the full size of Earth, a 6,371 km radius, all derived from one seed, so nothing exists until someone goes there. Every noise is sampled at the true point on the sphere, so the ground runs continuous across face seams and over the poles with no border and nothing that repeats.

A few parts I had the most fun with:

Rivers are a priority flood over a 20 km grid of regions. A single search over the whole planet would be about five billion zones at this size. I definitely have some tuning to do 🙃

The Moon's maria are biased to the near side. Over three seeds they cover 21 to 39% of the near side and under 3% of the far, close to the real Moon's 31% and 2%.

Craters come from a lattice at seven scales, from 11 m cells up to 7 km. The big ones get flat floors, terraces and a central peak, and each lattice cell belongs to exactly one cube face so no crater gets doubled or cut at a seam.

It's Rust and Bevy. Happy to go deeper on any of it.


r/proceduralgeneration • • 1d ago

First-principles 3D geological terrain simulator

Post image
10 Upvotes

I’ve been building and testing a 3D terrain simulator using first principles instead of standard procedural noise, and I was wondering if anyone would be interested in using it and giving me feedback.

It runs on Windows and requires an NVIDIA GPU, as CuPy made development way easier on me (sits around ~2 GB VRAM on a 512×512 grid). It models coupled erosion, subsurface rivers/caves, fault uplift, and atmospheric chemistry, and exports .ply / .gltf meshes into Blender.

Would anyone want to test it out or check out some simulation runs? Happy to share screenshots or answer questions about how it works.


r/proceduralgeneration • • 22h ago

It's been a month since I released my little procedural creature-collecting experiment, and today it reached 100 players!

0 Upvotes

I'm really happy with the current path of this little web game, in which you simply connect 2 or 3 times a day to compete for the Blobi of that day and do some chores with them that revolve around collecting items and interacting with other users. What started as a little experiment ended up turning into a little community!

I would like to hear your opinions about the first impressions of the trailer and if you would like to try it out: blobvarium.com


r/proceduralgeneration • • 1d ago

My Spore-like Evolution Game

24 Upvotes

The game concept is almost identical to Spore. You start as a single cell, design your creature, crawl out of the sea (or don’t), and end up leading a tribe.

What I’m trying to do is the parts I always missed: a real underwater stage, the choice to stay in the sea or go on land, and tribes that remember how you treated them. Every stage will be deep and complex enough. Full mod support.

How procedural is it? There are no hand-made creature models or animations. Every body is built in code from its DNA: spine, limbs, parts and skin pattern become a mesh at runtime, for cells, sea creatures and land creatures alike. Movement is procedural too. The walk cycle comes from the body you built, with feet that plant and don’t slide, extra steps on turns, and a lizard-style climb on steep slopes; swimmers get a body wave from their spine. 

The cell stage is a free demo and runs in the browser: https://akinjigames.itch.io/primordium

If you want to follow it, the Kickstarter pre-launch page is here. Hitting “Notify me on launch” helps a lot:
https://www.kickstarter.com/projects/primordium/primordium-evolve-your-own-creature-from-a-single-cell

It’s still rough in places. If you try it, tell me where you got stuck or bored. That’s how most of this week’s fixes happened.


r/proceduralgeneration • • 1d ago

Carving procedural terraces and dungeons into a height map (C++/OpenGL/GLSL)

3 Upvotes

A short preview / demo of carving procedural terraces into terrain. Free demo here: https://store.steampowered.com/app/2223480/Infinicity/


r/proceduralgeneration • • 22h ago

Check out VOID.TD on my github.

0 Upvotes

https://haykohanyans.github.io/void-td/

66 free procedural systems ready for your projects. GLSL, raymarching, and simulations at your fingertips. Explore everything from black holes to complex fractals—all free to use.

Thank you for your support 🫂


r/proceduralgeneration • • 1d ago

Idea for Topological Kinematics and Chiral Flow

1 Upvotes

I’m not a professional software engineer or graphics programmer, just someone who went down a deep mathematical rabbit hole this morning thinking about how skeletal and procedural animation systems handle continuous twisting, helical winding, and topological constraints.

I ended up turning the idea into a complete, MIT-licensed open-source specification and reference repository: TKMH (Topological Kinematics and Chiral Flow).

Repository: https://github.com/thomwblair/tkmh-framework

What’s inside:

  • Normative Specification (tkmh_normative_spec.md): Defines the mathematical foundations, 3.5-turn chiral spinal winding invariants, and curvature (kappa) bounds.
  • Binary Container Format (.chiral): A tightly packed binary layout starting with a 44-byte little-endian header (CHRL magic signature) and explicit byte offsets for tensor, wave, and weight payloads.
  • Reference Implementations:

    • tkmh_parser.cpp: A C++17 parser enforcing strict bounds checking and memory alignment.
    • validate_chiral.py: A standalone Python validator and sample container generator (samples/sample.chiral).
  • OpenUSD Integration (tkmh_schema.usda): An applied API schema (TKMHSpineAPI) designed to expose these chiral properties inside DCC tools and game engines like Houdini, Maya, or Unreal Engine.

Since this started as a spontaneous personal project rather than an active production pipeline, I’d love any feedback, critiques, or thoughts from folks who actually work with custom binary formats, skeletal rigs, or OpenUSD schemas.

Thanks for taking a look!

Edit: At a glance, this looks like a simple glowing helix—but it’s a visual testbed for a deterministic parametric framework (TKMH) designed to replace destructive, manual 3D modeling workflows with rule-based topological kinematics.

Why this matters for production and engineering pipelines:

  • Zero-Rework Iteration: In traditional modeling or CAD, altering the pitch, twist angle, or chirality of a complex helical structure breaks downstream UVs, rigs, and simulation meshes. Driving the geometry through pure parametric rules means structural variations update instantaneously without manual redrafting.
  • Data Economy: Instead of storing and version-controlling heavy, multi-megabyte mesh caches (.fbx/.obj), the entire geometry is defined by lightweight mathematical parameters—keeping pipeline footprints minimal until final render evaluation.
  • Deterministic Scalability: The same ruleset can instantiate interlocking multi-strand structures or variable-density topologies on the fly without bloating memory budgets.

Render Details: Generated the base topology parametrically and rendered the turntable in Blender 4.x (Cycles with OptiX on an RTX 4070 Ti), using a high-strength emission shader interacting with a matte studio floor plane to isolate the silhouette and bounce light.

Curious how others here handle parametric vs. destructive workflows when dealing with complex, repeating topological curves—do you stick to Geometry Nodes/scripts, or manually keyframe/deform?