Benchmarks and validation

Evidence boundary

Kiwi Grass release 26.8.0 is metadata-aligned with the accepted runtime candidate measured on Unity 6000.4.0f1 and URP 17.4.0. The accepted Player evidence predates the package-safe sample move. Treat the 300 m and 1000 m values below as disclosed reference methodology until the moved scenes receive their final Development Player rerun.

The package currently passes synchronous package reimport, static audit, release validation, and 400/400 EditMode tests on Unity 6000.4.0f1. The earlier six-editor matrix remains a separate 398/398 compatibility boundary because the two newer sample-structure tests were not rerun on the other five editors.

Unity 6000.0+ compatibility matrix

Six isolated projects used an active URP asset with rendering layers enabled. Every editor resolved the local package, compiled without C# or shader errors, passed package reimport, static audit, release validation, and all 398/398 EditMode tests.

Compatibility guards preserve the normal renderer without Automatic Hi-Z on pre-6000.3 editors. No cross-version Development Player builds were run, so performance and visual claims remain limited to the disclosed Unity 6000.4 evidence.

Metal Development Player reference

The GrassDemo300 reference used Unity 6000.4.0f1, URP 17.4.0, Apple silicon, Metal, and 1920 x 1080.

Windows Vulkan Development Player reference

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 x 1080.

Interpreting the numbers

• These are controlled references, not universal FPS or hardware-support claims.
• The 0 B result applies to the measured steady grass render-loop sweep. It does not mean the entire product or frame allocates zero bytes.
• Whole-frame timing is reported separately from grass culling, command preparation, upload, and indirect submission.
• Other Windows builds, GPU vendors, GPU models, drivers, mobile devices, and unmeasured graphics APIs are not advertised from these configurations.
• The final package-safe moved-sample Development Player rerun remains open.

Current release gates

• Repeat the Package Manager UI import and removal cycle in a clean consumer project.
• Rerun the moved 300 m and 1000 m scenes in final Development Players.
• Complete the path-compatible traditional package, official Asset Store Tools validation, and final Publisher Portal review.