Graphics researchers have created a GPU-run procedural algorithm for creating an equivalent 35.6 GB worth of trees, leaves, and brushes from just 52 kB of data

Real-Time GPU Tree Generation - Supplemental - YouTube Real-Time GPU Tree Generation - Supplemental - YouTube
Watch On

Anyone who is interested in realistic real-time graphics, be it in games or animation, will know that dense vegetation can be very costly on GPU resources. They either eat up lots of VRAM or shader time, or both. A team of university researchers and AMD staff have come up with a solution, though, that procedurally generates almost 36 GBs worth of realistic trees, branches, and leaves from just 52 kB of data.

The work of the team was submitted to the Eurographics Association's High-Performance Graphics 2025 Symposium (via Compusemble), and naturally for such an audience, it's a very complex read. But the gist of it goes like this: the algorithm uses work graphs on the GPU to procedurally generate realistic vegetation from just a tiny block of starting data. Specifically, 52 kB of data—less than a quarter of the size of a single L1 cache block of the GPU, a Radeon RX 7900 XTX, which the research group used to test their code.

Work graphs are a fairly recent addition to graphics APIs such as Direct3D and Vulkan, and it's basically a system that allows GPUs to manage their own workload, even going as far as invoking the shaders it needs for rendering, without having to wait for the CPU to send the instructions across.

However, procedural generation is anything but new, and the demo scene of the late 1990s and early 2000s was filled with incredible-looking graphics routines that were all microscopic in size, such as the fantastic .fr08 .the .product demo, tipping the scale at 64 kB.

What this team of researchers from Coburg University in Germany, along with some bright lights from AMD, has achieved, though, is just as impressive, if not more so. It's not just that the algorithm has produced all the trees, leaves, and bushes you can see in the above video from a tiny 52 kB of VRAM, it's the fact that the RX 7900 XTX only takes an average of 7.7 milliseconds to generate and then render everything.

That almost puts it into the realm of possibility for use in a real game. If one is targeting a mean frame rate of 60 fps, for example, then you've no more than 16.7 milliseconds to get everything done. It's not ideal to take up half that time for rendering nothing more than a short view distance, full of trees and bushes, but the work clearly has potential.

Minecraft seeds - a mansion in a dark oak valley ringed by a pale garden ridge

The most famous procedurally generated game. (Image credit: Mojang)

Not least being the fact that creating all that vegetation from traditional polygon meshes and texture maps would require almost 36 GB of VRAM. Yes, you read that right: 36 gigabytes of memory. Admittedly, that's a theoretical figure calculated by the research group, and in reality, compression and mesh optimisation would bring it right down, but certainly not to 52 kB.

Procedural generation is how the likes of No Man's Sky and Minecraft have vast, almost infinite, play areas but only have install sizes of a few GBs. Now that developers have GPU work graphs to speed up the process even more, research like this might be procedurally popping up to say hello in games sooner than you might think.

AMD Ryzen 9 9800X3D processor
Best PC build 2025

👉Check out our list of guides👈

1. Best CPU: AMD Ryzen 7 9800X3D

2. Best motherboard: MSI MAG X870 Tomahawk WiFi

3. Best RAM: G.Skill Trident Z5 RGB 32 GB DDR5-7200

4. Best SSD: WD_Black SN7100

5. Best graphics card: RTX 5070 Ti or RX 9070 XT (whichever is cheaper)

TOPICS
Nick Evanson
Hardware Writer

Nick, gaming, and computers all first met in 1981, with the love affair starting on a Sinclair ZX81 in kit form and a book on ZX Basic. He ended up becoming a physics and IT teacher, but by the late 1990s decided it was time to cut his teeth writing for a long defunct UK tech site. He went on to do the same at Madonion, helping to write the help files for 3DMark and PCMark. After a short stint working at Beyond3D.com, Nick joined Futuremark (MadOnion rebranded) full-time, as editor-in-chief for its gaming and hardware section, YouGamers. After the site shutdown, he became an engineering and computing lecturer for many years, but missed the writing bug. Cue four years at TechSpot.com and over 100 long articles on anything and everything. He freely admits to being far too obsessed with GPUs and open world grindy RPGs, but who isn't these days? 

You must confirm your public display name before commenting

Please logout and then login again, you will then be prompted to enter your display name.