Compatibility

Unity 6000.0+ editor matrix

Six isolated URP projects resolved the local package, compiled the runtime, editor, and test assemblies without C# or shader errors, passed package reimport, static audit, and release validation, and passed the complete 398/398 EditMode assembly:

The disposable projects used Metal, a real URP asset, and rendering layers so the two pixel-level renderer tests executed rather than becoming inconclusive. This matrix proves package resolution, Editor compilation, shader import, and EditMode behavior on the named editors. It does not replace Development Player performance and visual measurements, which remain tied to the documented Unity 6000.4.0f1 configurations.

Supported release-candidate configuration

The manifest declares Unity 6000.0.0f1, Collections 2.2.0, and URP/Core RP 17.0.3 as compatible minimums. Unity resolves the compatible built-in package versions shown above. Pre-6000.3 code uses instance IDs, the older object-search overload, the older depth-normal packing and shadow-clamping contracts, and the normal renderer without Hi-Z. Unity 6000.3 and newer use EntityId, newer RenderGraph Hi-Z APIs, and the newer shader helpers. Unity 6000.5 and newer use the transposed TerrainData.GetHoles array order observed in those editors.

Automatic Hi-Z compatibility

Automatic mode requires compute shaders, asynchronous GPU readback, R32_SFloat load/store, a supported non-mobile target, and a profitable stable view. Unsupported, unavailable, moving, or unprofitable conditions fall back to normal rendering without false depth culling. Explicit Hi-Z remains a controlled diagnostic mode.

Unity versions before 6000.3 do not expose the RenderGraph texture-origin and asynchronous-readback APIs required by this implementation, so they use the normal renderer without Hi-Z suppression. The Metal and measured Vulkan self-depth paths are validated on Unity 6000.4. On the named RTX 2080 Ti host, controlled Hi-Z culls remained stable, a camera move greater than 2 m cleared stale history within one rendered frame, and explicit Off retained every valid blade.

Motion vectors and temporal antialiasing

Standard quality emits camera-only motion vectors. Cinematic can emit procedural previous-frame wind, gust, terrain-offset, and stomp history through the URP MotionVectors pass. Use TAA or another suitable temporal path when the target presentation needs stable subpixel mid/far blades.

Shadows and additional lights

The package receives the URP main-light shadow map and supports its documented additional-light modes. Standard desktop presentation does not cast every blade into cascades. Cinematic and custom profiles can opt into the heavier paths, which must be measured on the target renderer and API.

Renderer feature expectations

No custom URP renderer feature is required. The package uses indirect rendering, compute resources, package shaders, and runtime callbacks. Project depth, opaque texture, post-processing, and TAA settings remain project-owned and should be recorded with visual evidence.