The core logic of that version followed the classic Tile-based Forward+ approach: it rendered a depth pre-pass to calculate the depth range for each tile and performed light culling to reduce the cost of light loops in the fragment shader.
A selection of SmallBurger Asset Store plugins has been tested and verified with Unity 6.3 LTS.
Currently, 8 out of 21 plugins have been validated on Unity 6.3 LTS.
Additional plugins will be tested and updated progressively based on project priorities.
You can find the complete SmallBurger plugin lineup on the Unity Asset Store publisher page:
In my previous post, Simulating Ghost of Tsushima’s Iconic White Flower Field in Unity, I wrote:
“I hope it can eventually run just as smoothly on mobile devices.”
That goal was achieved sooner than expected.
And that white flower field is no longer alone.
Today, the same architecture can support twenty types of vegetation — all processed on the GPU — handling wind simulation, interaction, painting, and culling simultaneously.
This article is not merely a showcase of results, but a record of the journey — from a simple flower field experiment to a complete vegetation system.
A journey to find what I call “poetic dynamics” on the GPU.
This release focuses purely on foreground, camera-facing particle effects—such as wind swirls, impact bursts, weapon trails, magic glows, atmosphere streaks, UI-adjacent FX, and any particle that stays tightly aligned to the screen.
These particles now react to lighting in a way that matches the rest of your scene’s illumination—without losing the performance advantages of a camera-adherent GPU pipeline.
I’ve always been fascinated by the vegetation system in Ghost of Tsushima.
After finishing the grass part earlier, I finally decided to tackle the iconic white flower field.
Unlike traditional methods that rely on massive Transform Buffers or GameObject instances, this approach dynamically generates grass using ComputeShaders. For culling, I use a RenderTexture to store results (since SSBOs aren’t supported in many mobile VertexShaders), ensuring compatibility with most mobile devices.
This architecture significantly improves load times and performance, especially on mid- to low-end phones. Let’s break down the key design concepts step by step.
shader_feature and multi_compile, and when to use each one. I’ve encountered similar confusion myself, so I’ve put together this comparison table and practical guide to help everyone quickly understand the correct usage.