r/procedural • u/TheSapphireDragon • Apr 14 '25
Game Some floating islands made with layered marching squares and fractal simplex noise
This is going to be the primary terrain system in a little exploration game im making for a college project
r/procedural • u/TheSapphireDragon • Apr 14 '25
This is going to be the primary terrain system in a little exploration game im making for a college project
r/procedural • u/SingerLuch • Jan 02 '25
r/procedural • u/DV-Gen • Apr 15 '22
r/procedural • u/Slackluster • Feb 12 '22
r/procedural • u/[deleted] • Jan 17 '23
r/procedural • u/JerryGreenest • May 14 '21
r/procedural • u/obesefamily • Dec 01 '20
r/procedural • u/SweetEasy5457 • Jul 02 '26
r/procedural • u/LABYRAINTH • Sep 25 '25
Hi everyone, I wanted to share with you the development process of our game LabyrAInth, which we have been working on for two years.
We developed this game in such a way that...
TL;DR
Labyrinths are actually data matrices. We associate a value with each piece of data and reconstruct it in real time in Unreal in the game.
We start with algorithms that generate mazes. There are tons of them, and we customized one similar to graph exploration using DFS. The script runs in Python and generates a data matrix.
This matrix is then loaded into the game and parsed by another algorithm that dynamically builds the maze in the game.
All this in a matter of tenths of a second!
But we don't stop there. The game textures are also procedural and scale with the length and type of maze wall.
And finally, the actors that populate the maze.
While the algorithm parses the matrix to build the walls of the corridors, another decides where to place the actors according to certain criteria. Enemies, traps, power-ups, weapons, decorations... they all have ad hoc procedural algorithms that scale with the shape and size of the maze.
The most important thing, however, is the assignment of a level given the maze matrix. Here we studied various university research papers and ultimately formulated a metric that establishes the level of the maze based on its size but above all on its complexity, i.e., how many paths there are to the solution and how long the latter is.
I am attaching some screenshots of the game from above.
What do you think?
r/procedural • u/svaswani93 • Jul 15 '24
r/procedural • u/svaswani93 • Jul 10 '24
r/procedural • u/svaswani93 • Sep 19 '25
Supercharge your Houdini workflow with 7 powerful HDA Toolsets — all in one bundle!
From perfect deformation blur to streamlined AOVs, lightweight camera-aware scenes, and art-directable instances, this collection is built for speed, stability, and production.
📦 What’s Inside
Particles Deformation Blur for Houdini
- Stable point counts for cached particles → perfect deformation blur
- Eliminate jittery, inconsistent blur and velocity hacks
- Works for rain, sparks, embers, sand, and custom FX
- Example HIP file included
2. IPOPs Standard Library
- Core operator set for shaders & AOVs
- Utility nodes (Fresnel, falloff masks, shading presets)
- Supports Mantra, Karma VEX, Karma Materials & MaterialX
- Constantly updated with new nodes
3. IPOPs Geometry AOVs
- Generate quick mattes and passes for comp & shading
- Compatible with Karma Materials & VEX Shaders
- Step-by-step guide available on the blog
4. IPOPs Particles AOVs
- Specialized AOV generators for particle FX
- Create passes for compositing & lookdev flexibility
- Works in Karma and Mantra
5. IPOPs Volumes AOVs
- Fast generation of volume AOVs (smoke, pyro, fog, etc.)
- Plug-and-play for Karma CPU/XPU & Mantra
6. Camera Proximity Toolkit
Three black-boxed HDAs to keep your shots light & render-ready:
Calibrator → Camera-driven particle & volume control
Set Culling → Remove out-of-frustum geo + auto VDB proxies
Ocean Plane Generator → Camera-sized ocean grids adaptive to shot scale
7. Art Direct Your Instances! (Explosion Setup)
- Populate shots with multiple explosions/caches
- Switch between proxy & render caches
- Quick controls for timing, scale & randomization
- Example HIP file included
r/procedural • u/svaswani93 • Aug 10 '24
r/procedural • u/DV-Gen • Apr 17 '23
r/procedural • u/YoZaffo • May 26 '22
r/procedural • u/ScorpionVenomSG • May 13 '20
r/procedural • u/ScorpionVenomSG • May 13 '20
r/procedural • u/aloisdg • Sep 27 '15
r/procedural • u/Difficult-Priority27 • Jul 14 '26
Hi everyone!
I wanted to share a sneak peek of Monolith Engine, a project I’ve been developing. It’s a purely client-side, nodal-based procedural 3D modeling tool built completely with web standards and optimized specifically for mobile viewports.
The Vision: I wanted to create a compact, tactile environment inspired by hardware instruments (like Teenage Engineering) and classic node graphs (like Blender or Resolve Fusion), but lightweight enough to be fully usable on a phone screen.
Key Features shown in the clip:
A Random Graph Generator to test instant mutations.
On-the-fly mesh manipulation and standard generation primitives (Cube, Sphere, custom profiles).
Experimental nodes like Vinyl Chaos, an interactive scratchpad that deforms the geometry using digital bitcrush or vortex analog distortions based on your touch interactions.
A "Freeze" mechanism to cache complex nodes at 0.0ms execution time and maintain 60 FPS on mobile.
Everything is running live inside a standard mobile web browser. I spent a lot of time engineering the touch interactions (panning the graph, scaling inputs, wire routing without a mouse). Would love to get some feedback on the UI/UX layout!