Create and use such containers carefully because too many unnecessary objects will make the hierarchy overly complicated and leave a mark on the performance.ĭo not use textures for white squares Design 16.

This is useful when a group of entities should be turned on or off according to the logic of the game. Groups of entities that share a visibility state could also be put into an empty gameObject container with a consistent name, “Content” for instance. Health Bar, Ammo counter, Stamina Bar etc.) can be organized inside an empty gameObject. Organize smarterĮvery separate UI entity (e.g. Stick to whatever naming format you chose internally and follow it across all projects. Just like objects in the scene or files in the hierarchy, UI elements should be named sensibly with an indicator of the element type. So if you are uncertain about anything you are dealing with, a thorough research is the best place to start. There is no use in blindly following any advice whatsoever unless you understand where it comes from and what an underlying basis of the advice is. Moreover not every practice will work for you. Of course, the situations vary from project to project and goal to goal, but general principles remain the same.

This will be helpful if there is a team working on UI, including visual and game designers, programmers and any other stakeholders. This list will walk you through UI-specific best practices when working with Unity engine and UI in general.

Walks left unity pc build