Page locked

This page is currently locked for editing by another user. You have to wait until this user finishes editing or the lock expires.

Currently locked by: 114.119.154.207
Lock expires at: 2024/05/05 13:28 (1 min)

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== Renderer Batching ======

There are a few different ways that Unity can combine meshes together, for optimization:
  * "Static Batching" - The checkbox in the Unity Player Settings. Can be done on build or at runtime ((See ''StaticBatchingUtility.Combine'' to batch meshes at runtime.)).
  * "Dynamic Batching" - A now-outdated mode of runtime batching. Not recommended. ((I can no longer find a player settings checkbox to even enable this feature))
  * "SRP Batching" - A [[https://blogs.unity3d.com/2019/02/28/srp-batcher-speed-up-your-rendering/|new]] runtime batcher for the SRP.


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 "Combined Mesh (root: <root-game-object>)", with a [[Submesh]] for each batched renderer. Unity invokes a separate draw call for each range of indices within the combined mesh buffer.

Note that this means Unity does not actually render the entire batch in a single draw call. As they [[https://docs.unity3d.com/ScriptReference/StaticBatchingUtility.html|mention]], truly merging all meshes would make culling vastly less effective. 

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]]. 

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 if you have many scenes with heavily-batchable geometry.

==== 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 ''meshRenderer.lightmapScaleOffset'' **will** return the old scale and transform, even though it has been baked into the mesh. Technically, in the render pipeline, all of these meshes have a lightmapST (scale/transform) of '(1,1,0,0)'. ((It shows the scale and transform it loaded from the LightingDataAsset file for that renderer.))

Uninomicon

User Tools

Site Tools

Page locked

Page Tools