Unity-URP-Render-Graph

URP Renderer Features and Render Graph

Inspect the active URP asset/renderer for each quality tier, package version, graphics API, XR and Render Graph setting. Preserve the project's supported compatibility path unless migration is requested.

• Define the pass inputs, outputs and injection point before implementation. Camera color, depth, normals and intermediate textures have distinct availability and format requirements.
• Use the installed RecordRenderGraph APIs and declare texture reads, attachments and access flags. Pass data and the render callback must agree with the declared dependencies; otherwise culling or ordering can invalidate the result.
• Treat graph TextureHandle values as graph/frame-local. Do not cache them across frames; persistent external resources need deliberate lifetime, import and release through supported APIs.
• Avoid reading and writing the same texture unless the specific supported pass model permits it. Use a separate destination or the documented blit path and account for back-buffer restrictions.
• Match descriptors to camera dimensions, dynamic resolution, MSAA and XR texture layout. Avoid hardcoded screen sizes or formats that break the target graphics API.
• Guard which cameras run the effect: game, scene, preview and stacked cameras can otherwise apply it twice. Scope material/resource creation and dispose owned resources.
• Compare Render Graph Viewer/Frame Debugger and target captures. Investigate copies, bandwidth, unnecessary intermediates and pass merges before claiming an optimization.

Verify compilation on the installed URP version, camera stacking, effect toggling, resize/dynamic resolution and the intended target. Do not copy legacy cmd.Blit recipes blindly into a graph pass.

Reference: Write a URP Render Graph pass, selecting the project's Editor version.