← Back to Game developers

Skill · Version 1.0.0

Unity rendering budgets

Allocates Unity rendering work according to measured GPU and render-thread costs. Balances shadows, transparency and texture use while preserving the visual information players need.

unity-game-rendering-budgets

Team members using this skill

See how it helps

When is it useful?

Use it when changing draw counts, quality settings or assets does not produce the expected performance improvement.

What does it help you do?

  • Separates pass structure from actual GPU timing evidence.
  • Diagnoses overdraw, shadows, bandwidth and shader-variant costs.
  • Checks real batching eligibility and target-tier texture residency.

Try asking this

A Unity forest battle slows down despite fewer draw calls. Compare the same view with particle effects, foliage shadows and transparency isolated. Measure GPU time and texture residency on the target tier, then reduce the proven cost and verify that enemy silhouettes and attack warnings remain readable.

Detailed documentation

Read the skill’s original instructions, examples and checks in their authored language.

Details…Show less

Rendering Budgets and Cost Attribution

Inspect pipeline/renderer versions, active quality assets, graphics API, resolution, target GPU and representative viewpoints. Separate CPU submission cost from GPU work.

  • Use Frame Debugger for pass/batch structure and appropriate GPU tools for timings. A lower draw count does not automatically mean a faster GPU frame.
  • Classify pixel/fill, geometry, shadow, lighting, bandwidth, synchronization and shader-variant costs. Compare controlled changes such as resolution only to answer a specific bottleneck question.
  • Verify actual batching/instancing eligibility and coverage in the installed pipeline. SRP Batcher, GPU instancing and GPU Resident Drawer have distinct constraints; a checkbox is not proof of use.
  • Inspect transparent overlap, extra passes, depth/opaque copies and camera stacking. Preserve necessary visual/gameplay signals when proposing reductions.
  • Budget texture formats/residency, mesh/LOD transitions, shadows and post-processing for target tiers. Coordinate asset changes with the relevant art role rather than globally rewriting content.
  • Separate shader compilation/warm-up hitches from steady-state GPU cost. Keep variant stripping tied to supported content and graphics APIs.

Compare identical camera, scene, device and quality settings before/after, including image output. Report CPU/GPU timings and remaining target limitations.

Reference: Unity rendering optimization. Version-specific upstream examples require verification in the actual pipeline.

Included files 2

  • LICENSE.txt
  • SKILL.md