Foliage & Vegetation

Every distinct object the engine draws costs a draw call - a message from the CPU telling the GPU to render that thing. Draw calls are one of the first bottlenecks you hit in real time, and vegetation is the fastest way to blow the budget: a wood might want tens of thousands of plants, and ten thousand separate tree actors means ten thousand draw calls, which no CPU will feed smoothly.

Instancing is the escape. Instead of ten thousand independent objects, you send the tree mesh to the GPU once, together with a list of ten thousand transforms - a position, rotation and scale for each copy. The GPU then stamps that mesh out at every transform in effectively a single batched draw call. The saving is enormous, and it is the only reason dense real-time vegetation is possible at all.

Unreal wraps this in the Foliage system, which uses Hierarchical Instanced Static Meshes (HISM) under the hood. You do not hand-write transforms - you paint foliage onto surfaces with a brush, and Unreal stores each dab as another instance in the batch. So the moment you use the Foliage tool rather than dragging in individual meshes, you are automatically getting the instancing that keeps the scene alive. Using individual actors for a forest is the classic beginner mistake this system exists to prevent.

One nuance worth knowing: instancing batches copies of the same mesh. Ten thousand identical trees cost roughly one draw call, but ten thousand trees made of five different species cost about five - one batch per unique mesh (times its material sections). That is usually fine and even desirable for variety, but it means the lever for draw calls is the number of distinct foliage assets, not the number of plants. A convincing wood built from three or four well-chosen tree meshes, varied by random scale and rotation, is both richer-looking and cheaper than a dozen near-identical species each in its own batch. Restraint in the palette pays twice.

Switch to Foliage mode (the leaf icon) and you get a brush much like the Landscape paint brush. Drag your tree, shrub and grass Static Meshes into the Foliage palette, set each type's density, scale range and alignment, then paint them onto the Landscape or any surface. Because you set a random scale and rotation range, no two stamped copies look identical - the natural variation that stops planting looking like wallpaper.

Useful controls: density governs how many instances per area the brush lays down; random scale and random yaw give variety; align to normal lays grass and ground cover flat against a slope; and a paint distance/collision filter can keep foliage off roofs, paths or water. You erase with the same brush holding Shift, and you can select and adjust placed instances afterward.

For two special cases Unreal has smarter automation. A Landscape Grass Type attached to a Landscape Material layer scatters grass and small plants automatically wherever that layer is painted - so grass appears exactly where you painted the grass surface, updates when you repaint, and is generated on the fly rather than stored. And the Procedural Foliage tool can grow a believable ecosystem across an area using simulated competition between species - good for naturalistic woodland where hand-painting every tree would be tedious. Hand-paint the trees you care about (the specimen by the entrance); let automation fill the mass behind.

Instancing gets you in the door, but dense foliage still needs discipline to stay smooth - especially in VR, which renders everything twice and wants ~90fps. Three levers matter most.

LODs (levels of detail): each foliage mesh should carry several simpler versions of itself, and Unreal swaps to a cheaper one as the plant recedes, dropping to a flat billboard or imposter far away. A distant hillside of trees can be almost all billboards and still look convincing. Cull distance: set a maximum distance beyond which an instance simply is not drawn - grass invisible at fifty metres should not be rendered at all. Tuning per-foliage-type cull distances is one of the highest-value optimisations in an outdoor scene. This is the same LOD-and-culling thinking Module 9 covers in depth for the whole scene.

Wind brings the planting alive. Unreal's foliage and tree materials support a SpeedTree-style wind that gently sways trunks, branches and leaves; a Wind Directional Source actor drives it. A touch of movement reads as life and hides the repetition of instanced copies - but keep it subtle, because heavy per-vertex wind on a whole forest has its own cost. The craft is layering: full-detail hero plants near the camera, LOD-reduced mid-ground, billboards and culled emptiness beyond - a planted site that looks lush from the path yet never overruns the frame budget.

Great foliage starts with good source meshes. The richest free library is Quixel Megascans, now delivered through Epic's Fab marketplace, which offers photoscanned trees, shrubs, grasses and ground scatter built with LODs and wind ready to go - we cover Megascans and asset discipline in the next lesson. Twinmotion also ships a generous library of ready vegetation, and dedicated tools like SpeedTree model bespoke species. Whatever the source, prefer assets that already include proper LODs; retrofitting them is painful.

Use plants that belong to the place. A row of temperate oaks around a building meant for a hot, dry Indian site is a small lie that a local reviewer will catch instantly - match species, density and seasonality to the real climate and region. Planting is also a design discipline, not just set-dressing: the tree that shades a west window, the hedge that screens a boundary, the avenue that frames the approach are architectural decisions your visualization should represent truthfully, not just prettify.

Finally, be honest about maturity and time. Showing a scheme wrapped in twenty-year-old canopy on day one oversells it. If the planting is a future state, it is fair to say so - or to show both the just-planted and the mature condition. Real-time makes that easy, because you can toggle foliage density or swap young for mature meshes live in front of the client.

Instancing solves the CPU cost of many objects, but foliage hides a second, GPU-side cost that surprises people: overdraw. Tree leaves and grass blades are not solid - they are flat cards with a masked or translucent texture, mostly transparent, that fake a complex shape cheaply. The catch is that the GPU still has to process every pixel of every card, including the see-through parts, and when dozens of leaf cards overlap in front of the camera the same screen pixel gets shaded over and over. A single bush right against the lens can cost more than a whole distant hillside, because the near cards pile up and each demands its share of shading.

This is why dense foliage can run fine in the mid-ground yet tank the frame the moment you push the camera into a bush - and why VR, which shades everything twice, is so unforgiving of it. The fixes are practical: keep near-camera foliage density sensible rather than maximal; use foliage meshes whose leaf cards are trimmed tightly to the silhouette (less wasted transparent area); and prefer masked materials over true translucency where you can, since sorted translucency is costlier still.

Diagnosing it is a Module 9 skill worth previewing here. Turn on stat Unit to see whether you are CPU-bound (too many draw calls - reduce distinct foliage types) or GPU-bound (heavy overdraw - thin out or trim the near foliage). Unreal's shader-complexity and quad-overdraw view modes literally colour the screen red where overdraw is worst, usually lighting up exactly the clumps of grass and leaves nearest the camera. Learn to read that, and you will place lush planting that stays smooth instead of guessing why a green scene stutters.