Benchmarks and validation

Release evidence

Kiwi Grass 26.9.0 was checked in fresh Unity projects using one frozen 528-file customer package. Each editor below passed 413 EditMode tests, two normal Play Mode cycles, and two cycles with Domain Reload and Scene Reload disabled. Package reimport, static checks, release validation, and post-run package-byte checks also passed.

This matrix covers the listed editors, not every Unity patch or every hardware platform. The 6000.7.0a3 result is an alpha-editor observation, not support for a future final release. No Player performance benchmark is implied by these Editor results.

Tested editor versions

Automatic Hi-Z requires Unity 6000.3 or newer. See compatibility for rendering requirements and platform limits.

Historical performance references

The following Development Player measurements predate the package-safe sample move and the 26.9.0 release. They are historical configuration-specific references, not measurements of the currently distributed package. A fresh benchmark of the moved scenes has not been established by this website update.

The GrassDemo300 reference used Unity 6000.4.0f1, URP 17.4.0, Apple silicon, Metal, and 1920 × 1080. It recorded 505,113 visible blades, 64 visible chunks, and 78 indirect commands. Whole-frame means were 4.8969 ms CPU and 5.4708 ms GPU.

The GrassDemo1000 reference used Windows 11 build 26200, Unity 6000.4.0f1, URP 17.4.0, Vulkan, an Intel Core i9-14900KF, an NVIDIA GeForce RTX 2080 Ti, driver 610.47, and 1920 × 1080. It recorded 35,557,827 generated blades, 1,335,777 visible blades, 484 visible chunks, and 89 indirect commands. Whole-frame means were 6.0587 ms CPU and 5.9741 ms GPU; grass cull and command preparation averaged 0.1201 ms.

Interpreting performance claims

• The historical steady grass render-loop sweep recorded 0 B of managed allocation. This does not mean the complete product or frame allocates zero bytes.
• Whole-frame CPU/GPU time includes other work. It is separate from grass culling, command preparation, upload, and indirect submission.
• These values do not establish universal FPS, support for untested hardware or drivers, or performance on another release.
• Compare your own scenes and hardware using the optimization guide. Editor demonstration clips show appearance and workflows, not a runtime benchmark.