Procedural generation debate
Developers on social are defending procedural generation for keeping game files small—one example cites a 250MB open‑world 'DJ Simulator'—while acknowledging longer load times. (x.com) Separate posts also show experiments parsing semantic text to GLSL for WebGL procedural visuals. (x.com)
Procedural generation is back in the feed because developers are arguing that code can replace bulky art files, shrinking some games to a few hundred megabytes. (steamdb.info) (docs.unity3d.com) The example getting passed around is “DJ SIMULATOR,” a solo-developed Early Access game from REMBOT GAMES that launched on Steam on August 7, 2024. Steam lists it at $12.99, and SteamDB shows the app first released in August 2024. (store.steampowered.com) (steamdb.info) The social posts frame that game as an open-world project packed into about 250 megabytes, with the tradeoff that players wait longer while content is generated at startup or on demand. Unity’s manual describes the same bargain in general terms: scripts that generate textures can take far less storage than bitmap files, but the engine still has to compute those textures at runtime. (x.com) (docs.unity3d.com) Procedural generation means building parts of a game from rules instead of storing every object as a finished file. Unreal Engine’s documentation says its Procedural Content Generation framework can generate anything from assets like buildings and biomes to entire worlds. (dev.epicgames.com) The file-size argument is straightforward: a formula is often smaller than the finished image, mesh, or map it produces. Unity’s documentation says runtime-generated materials can reduce storage and transmission size, while its loading guide says prebuilt textures and meshes still have to be read from disk and uploaded into memory when needed. (docs.unity3d.com 1) (docs.unity3d.com 2) The cost is time and memory. Unity says procedural textures need memory for intermediate bitmaps during generation, and it offers disk caching specifically so developers do not have to pay the same generation cost every time an app starts. (docs.unity3d.com) (docs.unity.cn) A second set of posts pushes the idea further, showing experiments that turn semantic text into GLSL, the OpenGL Shading Language used for graphics programs. In WebGL, those shaders run in the browser on the graphics processor and can draw textures and animated effects pixel by pixel instead of loading image files. (x.com) (waelyasmina.net) (pixelartcode.uk) That is why the current debate is spilling beyond games into browser graphics and creative coding. If a text prompt can be parsed into a shader, the “asset” becomes a short program, and the browser computes the final image live on the user’s machine. (x.com) (pixelartcode.uk) Developers who prefer authored assets make a different trade: bigger downloads, but more predictable load times and tighter control over exactly what players see. The posts defending procedural generation do not dispute that point; they argue that for some projects, especially small-team projects, waiting on generation is worth the smaller install. (x.com) (docs.unity3d.com) The thread running through both examples is old but current again: store the recipe, not the finished dish. In 2026, that recipe is showing up both in tiny game installs and in browser demos where text becomes graphics code. (docs.unity3d.com) (x.com)