Version: Unity 6.1 Alpha (6000.1)
Language : English
Control textures of the dynamic atlas
FAQ for input and event systems with UI Toolkit

Platform and mesh considerations

Things to consider when building UI(User Interface) Allows a user to interact with your application. Unity currently supports three UI systems. More info
See in Glossary
for different platforms and meshThe main graphics primitive of Unity. Meshes make up a large part of your 3D worlds. Unity supports triangulated or Quadrangulated polygon meshes. Nurbs, Nurms, Subdiv surfaces must be converted to polygons. More info
See in Glossary
tessellation.

Consider device capabilities

Some Android devices and the Web platform can’t partially patch index buffers. If your audience uses such devices or if you target the Web platform, UI Toolkit rendering is still functional but performance may be degraded. To avoid performance degradation, don’t animate too many elements at the same time and profile on device.

Avoid mesh tessellation

It’s computationally expensive to build mesh tessellation for visual elementsA node of a visual tree that instantiates or derives from the C# VisualElement class. You can style the look, define the behaviour, and display it on screen as part of the UI. More info
See in Glossary
. Any time the size (width/height) of the element changes, its geometry re-builds, which can be an issue with animations or frequent resizing.

Generally speaking, transforms and texture aren’t good choices in terms of flexibility and re-use. However, when you animate, to get better performance, do the following:

  • Use transforms instead of width or other layout properties
  • Use textures or 2D spritesA 2D graphic objects. If you are used to working in 3D, Sprites are essentially just standard textures but there are special techniques for combining and managing sprite textures for efficiency and convenience during development. More info
    See in Glossary
    instead of rounded corners and borders

Additional resources

  • Transform
  • ProfilerA window that helps you to optimize your game. It shows how much time is spent in the various areas of your game. For example, it can report the percentage of time spent rendering, animating, or in your game logic. More info
    See in Glossary
Control textures of the dynamic atlas
FAQ for input and event systems with UI Toolkit