One way to decide how to split them up is based on how frequently they need to be refreshed. They maintain their own geometry and perform their own batching. Child Canvases also isolate content from both their parent and sibling Canvases. You can also nest Canvases, which allows designers to create large hierarchical UIs, without having to think about where different elements are onscreen across Canvases. Take advantage of UGUI’s ability to support multiple Canvases by slicing up your Canvases to solve the batching problems with Unity UI. To learn more about why rebuilding is so expensive, go to the 24:55 mark in this Unite session.Įach Canvas is an island that isolates its elements from those of other Canvases. When they change one element, they can experience a CPU spike costing multiple milliseconds.
Many users build their entire game’s UI on a single Canvas with thousands of elements. The issue is that, when one or more elements change on a Canvas, the whole Canvas has to be analyzed once again, to figure out how to optimally draw its elements. Because batch generation is expensive, we only want to regenerate them when necessary. UI Elements need to be collected into batches so that they’re drawn in as few draw calls as possible. Generating these meshes can be expensive. It generates meshes that represent the UI Elements placed on it, regenerates the meshes when UI Elements change, and issues draw calls to the GPU so that the UI is actually displayed. The Canvas is the basic component of Unity UI. Problem: When a single element changes on the UI Canvas, it dirties the whole Canvas.
0 kommentar(er)
