This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
static_batching [2021/02/11 23:29] 73.95.178.156 |
static_batching [2021/12/12 23:11] starasgames Added a bit of informaton about how static batching works in Editor |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
- | | + | There are a few different ways that Unity can combine meshes together, for optimization: |
+ | | ||
+ | * " | ||
+ | * "SRP Batching" | ||
+ | |||
+ | |||
+ | Note that none of these options actually combine meshes together. They will all result in the same number of graphics API drawcalls. Instead, the purpose of batching is to optimize the order of drawcalls to avoid changing state between calls. | ||
+ | |||
+ | ===== Static Batching ===== | ||
Static Batching in Unity creates a Read-Only mesh named " | Static Batching in Unity creates a Read-Only mesh named " | ||
Line 9: | Line 17: | ||
Instead, the performance comes from issuing fewer material / mesh change state operations (in OpenGL at least). In a lot of ways, this ends up being more similar to SRP [[Dynamic Batching]]. | Instead, the performance comes from issuing fewer material / mesh change state operations (in OpenGL at least). In a lot of ways, this ends up being more similar to SRP [[Dynamic Batching]]. | ||
- | ===== Lightmap UV Coordinates ===== | + | Static batching is done at build-time, so mobile developers should be aware that static batching can unexpectedly increase your build size. Static Batching can result in significantly more mesh data being generated, if many batch meshes are created. |
+ | |||
+ | In the Editor static batching occurs after the scene is loaded (after Awake and OnEnable). It is considered a [[https:// | ||
+ | |||
+ | ==== Lightmap UV Coordinates ==== | ||
+ | |||
+ | The lightmap coordinates from [[lightingdataasset|Lighting Data Asset]] are baked into the Combined Mesh UV coordinates when the scene loads((I think this also happens **during** standalone build, not at runtime, but I'm not sure)). Afterwards, querying '' | ||
+ | |||
+ | Static batching can actually work with manually provided lightmap scale/ | ||
+ | |||
+ | ===== Batching and MaterialPropertyBlocks ===== | ||
+ | |||
+ | Static and SRP batching is incompatible with MaterialPropertyBlocks, | ||
+ | |||
+ | This is the data sent by the SRP batcher for each draw call: https:// | ||
+ | |||
+ | This data is efficiently managed by the engine and uploaded to the GPU as fast as Unity can. The idea is to abuse some of these built-in values to pass custom data. Good candidates are '' | ||
+ | |||
+ | When using SRP batching, the recipe is following: | ||
+ | |||
+ | '' | ||
+ | |||
+ | '' | ||
+ | |||
+ | |||
+ | For custom SRPs: '' | ||
+ | |||
+ | On the GPU you should have a '' | ||
- | The lightmap coordinates from [[lightingdataasset|Lighting Data Asset]] are baked into the Combined Mesh UV coordinates when the scene loads((I think this also happens during standalone build, not during standalone runtime, but I'm not sure)). Afterwards, querying '' | ||
+ | Note that the " |