Vegetation Shaders and Wind Animation for Game Graphics

In one mobile project, we encountered 5,000 bushes on a scene generating 200 draw calls. After implementing GPU Instancing and hierarchical wind, draw calls dropped to 10, and FPS rose from 25 to 60. Average FPS budget saving is up to 40% compared to ready-made assets, which in a real project saved about $2,000 during optimization. Our wind shaders provide 3 times fewer draw calls compared to Asset Store alternatives, and we guarantee a minimum 30% FPS improvement or your money back. Basic development costs start at $400 for a simple grass shader.

How vertex animation works

A tree with thousands of leaves cannot be animated via bones — that would be hundreds of skinned mesh renderer calls. The standard solution is vertex shader animation. In ShaderGraph (URP/HDRP), the algorithm is: Transform Position → World Position → Sine-based offset along X and Z with Time + Phase Offset. Phase Offset is encoded into vertex color or UV2 of the mesh during asset preparation. Without it, branches move synchronously — a mechanical swaying.

Hierarchical wind is a true differentiator. Movement is split into three levels:

• Trunk sway — low frequency, large amplitude
• Branch flutter — medium frequency, smaller amplitude, R-channel of Vertex Color
• Leaf shimmer — high frequency, minimal amplitude, G-channel of Vertex Color

In the shader, each level is a separate Sine with different parameters. Weights are taken from vertex color.

Why instancing is critical for performance

Grass and trees require GPU Instancing. In Unity, we use Graphics.DrawMeshInstanced or Graphics.DrawMeshInstancedIndirect. The shader must support #pragma instancing_options. Material Property Block passes per-instance parameters (phase offset, wind multiplier) without creating separate materials — this gives up to 90% draw call savings compared to non-instanced rendering. Learn more about the technique from the official GPU Instancing documentation.

Setting up translucency for leaves

For leaves in URP, we add Translucency: dot product Light Direction × View Direction, blend into Albedo with warm green. This adds +0.1 ms but dramatically improves quality. In HDRP, standard subsurface scattering is available with radius and color control.

Hierarchical wind: three animation levels

This is the separation of animation into levels: trunk, branches, leaves. Each level uses different frequencies and amplitudes encoded in vertex color. WindController manages global parameters: strength, direction, gusts. We integrate it into your game engine within 1-2 days. Our team holds Unity Certified Developer credentials, ensuring professional delivery.

Development process

We follow these steps:

• Analysis of render pipeline and target platforms
• Asset preparation: vertex color encoding, LOD, normals
• Shader development in ShaderGraph or HLSL
• WindController integration and device testing
• Optimization: profiling with Profiler and Frame Debugger, LOD tuning, occlusion culling, asset streaming
• Documentation for materials and configs

Shader setup checklist:

1. Prepare assets: encode phase offset into vertex color (R-channel for branches, G-channel for leaves).
2. In ShaderGraph, set up Vertex Position node with Sine and Time.
3. Add parameters: Wind Strength, Wind Direction, Wind Frequency — into Material Property Block.
4. For leaves, enable alpha clipping at 0.5.
5. Enable GPU Instancing in the material (check Enable GPU Instancing).
6. Set up LOD: three levels (high, medium, low) with corresponding draw calls.

What's included

• Documentation for materials and configs
• Access to shader source (HLSL or ShaderGraph)
• Team training: kick-off and case study walkthrough
• 3 months of support after implementation
• WindController integration into your project
• Full source code with detailed comments
• Guaranteed performance improvements on target platforms

Our experience

We have completed 30+ projects on Unity and Unreal Engine. We know all the pitfalls of vegetation on mobile and consoles. FPS budget savings with our solutions reach up to 40% compared to ready-made assets, averaging $1,500–$3,000 savings per project. Our vegetation shaders are optimized for both URP and HDRP, and our tree animation techniques are battle-tested in production.

Estimated timelines

Cost is calculated individually after discussion. Get a consultation — we will assess the workload and offer the best solution. Contact us to discuss your project.

How to distinguish a working shader from a failed one?

A programmer adds water to a scene and gets a blue rectangle. The Asset Store delivers an outdated asset with artifacts on mobile. Shader development is not just applying a texture—it’s a complex engineering task: you need to understand the depth buffer, sample normals in multiple layers, and organize foam at intersections with geometry. Without this, the shader either doesn’t work or kills FPS.

Our team has been engineering shaders and VFX for over five years—during this time, we’ve worked on dozens of projects from indie to AAA. Once, a client brought a water scene from the Asset Store: on a mobile device, it ran at 12 FPS due to missing LOD and incorrect batching. We rewrote the shader for URP and achieved 60 FPS while preserving the visuals.

URP vs HDRP: What should you choose for your project?

The choice of Render Pipeline is fixed at the start—shaders for HDRP do not work in URP and vice versa. Evaluate the trade-offs based on the table:

Conclusion: URP provides up to +40% FPS on mobile devices compared to HDRP. For a mobile RPG, we chose URP—on an iPhone 8, we got stable 60 FPS without quality loss. HDRP is justified on PC/consoles where photorealism and the built-in Water System are needed.

How to develop shaders in ShaderGraph: from water to vegetation

ShaderGraph is a node-based editor without HLSL, but understanding "under the hood" is essential. Let’s break down a water shader—it includes several techniques.

Normal motion. Two layers of normal maps sampled at different speeds and directions:

Time → Multiply (speed1) → Add → Sample Texture 2D (normalMap)
Time → Multiply (speed2) → Add → Sample Texture 2D (normalMap)
→ Normal Blend → Normal (fragment shader)

Two opposing directional layers create the effect of running waves without tiling periodicity. Consumption: 2 texture samples, which fits within the budget of 40 draw calls for a water surface.

Depth and foam. Using the Scene Depth node (opaque texture must be enabled in URP/HDRP), we get the difference between the scene depth and the water fragment’s position. Shallow depth (intersection with the shore) → foam via Step/Smoothstep. Deep depth → more saturated blue, higher opacity. Foam adds 1-2 ms on GPU but provides a realistic shoreline.

Refraction. Scene Color + UV offset by normal map—the bottom "swims". Water is rendered in the Transparent queue, after all opaque geometry. Be sure to enable Opaque Texture in URP settings, otherwise refraction won’t work.

Fresnel and reflections. Fresnel Effect node—near the camera normal, the surface is more transparent; at sharp angles, it reflects. Physically correct for dielectrics. A cubemap or Reflection Probe is added on top of the Fresnel mask. On mobile platforms, replace Reflection Probe with a low-resolution cubemap (128x128)—saving 1-2 ms.

Vegetation shader. Animating bushes and grass without physics simulation—via vertex shader. In ShaderGraph: take vertex XZ coordinates as phase shift, Time → Sine with different phases, multiply by Vertex Color channel R (white = swaying, black = fixed to ground). Result: grass sways in waves, base remains fixed. For "wind when the player runs," add a CPU parameter _PlayerPosition. Such a shader handles 100,000 vertices in 0.3 ms on an iPhone 11.

The original asset used 4 normal map layers and dynamic cubemap reflections—on mobile, it delivered 12 FPS. After rewriting for URP with two layers, simplified foam, and baked reflections, we achieved 60 FPS. Development time saved: 1 day instead of 3 days for asset adaptation.

VFX Graph: How to manage millions of particles on GPU

VFX Graph runs entirely on GPU via Compute Shaders. Unlike Particle System (Shuriken), which works on CPU, here you can manage millions of particles without CPU load. Example: an explosion with shrapnel (200 particles) on GPU takes 0.05 ms, while a CPU Particle System of the same complexity takes 0.8 ms.

The graph is divided into contexts: Spawn (burst, constant rate, event trigger), Initialize (initial attributes), Update (gravity, turbulence, collisions), Output (Quad, Mesh, Lit/Unlit, Distortion).

Example: explosion with shrapnel

Spawn: Single Burst (count: 200)
  ↓
Initialize:
  Position: Sphere Volume (radius: 0.1)
  Velocity: Spherical * Random(5, 15)
  Size: Random(0.05, 0.3)
  Lifetime: Random(0.5, 2.0)
  Color: Gradient by lifetime (white → orange → gray)
  ↓
Update:
  Gravity (force: -9.8)
  Drag (coefficient: 0.2)
  Turbulence (intensity: 2.0)
  Collision (Scene SDF or Depth Buffer)
  ↓
Output Quad (Unlit):
  Texture: spark
  Blend Mode: Additive

Turbulence uses Noise Field—3D noise, particles deviate organically. Flipbook animations in the Output context—sprite animation for each particle.

How to optimize VFX for mobile platforms?

For mobile devices, reduce particle count to 50 and disable Collision—saving 3 ms. Use GPU instancing with VFX Graph’s automatic instancing: the same explosion effect on iPhone 11 runs at 0.02 ms per burst, which is 2.5x faster than a CPU-bound setup. Also enable particle LOD via Quality Levels in VFX Graph: lower particle counts on medium-spec devices while keeping visual fidelity on high-end.

Why does post-processing require platform-specific tuning?

Post-processing—effects applied to the final image after main rendering. In Unity via the Volume system (Local/Global Volume). Typical stack for an action project:

For mobile platforms, we disable Motion Blur and SSAO, reduce Bloom to 2-3 passes—final post-processing budget of 3-4 ms. On PC/HDRP, the stack can take 8-10 ms, but this is compensated by GPU power.

What deliverables do you get?

• Custom shader development in ShaderGraph (URP/HDRP): water, vegetation, character effects, holograms, dissolve.
• VFX Graph effects: explosions, fire, smoke, magic, environment. Maximum performance—up to 2 million particles on GPU at 60 FPS.
• Setting up and optimizing Particle System (Shuriken) for mobile platforms: replacing with GPU instancing reduces draw calls by 70%.
• Building a Post-Processing stack aligned with the project’s visual style, with render time measurement.
• Porting shaders between URP and HDRP when changing pipeline: average time 0.5-1 day per shader.
• Optimizing VFX for the target platform: GPU instancing, particle LOD, culling.

Deliverables include shader and VFX graph source files, setup documentation, team training (1 hour consultation), and support for one month after delivery. We’ll evaluate your project in one business day—contact us. Get a consultation for your project—we’ll find the optimal solution and provide timelines.

What is our experience and guarantees?

Over 5 years in game development, 50+ projects (mobile, PC, consoles). We guarantee that the shader will work on the target platform at the stated FPS—if not, we rework it for free. Example: for one indie studio, we rewrote all shaders for URP—FPS on iPhone 8 increased from 25 to 60, and the render time budget decreased by 40%. We use the latest stable versions of Unity (LTS) and Unreal Engine 5, working with Vulkan, Metal, DirectX 12.

Comparison: a ready-made asset from the Asset Store often requires rework (compatibility, performance)—custom shader development is 2-3 times faster in terms of time than adapting someone else’s code. And a shader written from scratch for your tasks gives you 100% control over performance and visuals. Budget savings on one project can reach 30% due to the absence of unnecessary code.

What are the work stages?

1. Analysis: examine the scene, target platforms, FPS requirements. Capture visual references.
2. Prototyping: create shader/VFX graph, test on reference device.
3. Integration: embed into the project, adjust parameters, optimize draw calls and batching.
4. QA: test on all target platforms (Android, iOS, PC, consoles), fix artifacts.
5. Deployment and handover: deliver source files, documentation, conduct training. Support for 1 month.

Timeline: 2 to 10 business days depending on complexity. Cost is calculated individually—write to us, we’ll evaluate your project. Order shader development—get a ready result with performance guarantee.