【Unite 2017 Tokyo】Unity UI最適化ガイド 〜ベストプラクティスと新機能
22 likes•29,518 views
The document provides various tips and tricks for optimizing Unity UI, emphasizing the case-by-case nature of optimization depending on the platform, style, and genre. Key points include the importance of UI batching, effective use of layout components, and managing the rebuild process to enhance performance. Tools and resources such as the frame debugger, UI profiler, and Text Mesh Pro are also discussed to help developers create efficient UI elements.
【Unite 2017 Tokyo】Unity UI最適化ガイド 〜ベストプラクティスと新機能
- 2. Tips and Tricks for Optimising Unity UI
- 3. Andy Touch Product Content Evangelist, Unity Technologies
- 4. Unity UI
- 6. In an Ideal World…
- 7. …However, This Button Does Not Exist!
- 8. Optimising UI is Case-By-Case Dependent • Range of Platforms: Mobile, to Console, to VR. • Range of Styles: 2D, 3D, Mixed • Range of Genres: Racing, FPS, 2D Platformer, etc • Not all advice will work in all use-cases! • Always best to Profile and Test on target device.
- 9. The Balance of UI Systems Flexibility Performance
- 10. UI Batching
- 11. UI Batching Rules A UI Batch Happens When 2 or more Visual Components… • Are on the same Canvas. • Share the same Material. • Share the same Sprite Asset. • Have RectTransforms that are Co-Planar to each other (Same Z Pos) • Are clipped by the same Mask.
- 12. Frame Debugger and UI Profiler Demo!
- 14. UI Shaders • All Visual Elements: ‘UI/Default Shader’. • Supports Masking, Clipping, Vertex Coloring etc • Built-In Unity Shader Source Code: Unity Archive Page • All Shader Source Code can be customised! • Demo Time!
- 15. Text Mesh Pro • Advanced Text Customisation and Rendering System • Very Popular Unity Asset Store Package • Acquired by Unity Technologies in February 2017 • Free to Download Today! • Demo Time!
- 16. The Rebuild Process • UI Element Layout changes -> Element is set to ‘Dirty’. • UI Element Graphic changes -> Element is set to ‘Dirty’. • Rebuild Process: Recalculates the ‘Dirty’ components/objects. • This can be seen in the Profiler as ‘Canvas.SendWillRenderCanvases’
- 17. Unity UI - Source Code bitbucket.org/Unity-Technologies/ui
- 18. UI Source Code – ‘Graphic.cs’
- 19. UI Source Code – ‘Graphic.cs’
- 20. UI Source Code – ‘Graphic.cs’
- 21. UI Source Code – ‘Graphic.cs’
- 22. Layout Components • Vertical, Horizontal, Grid, Layout Element, etc • Very useful for structuring UI and setting up UI elements in order. • Child Order determines how the Layout is structured. • Related RectTransform Changes -> Layout is set to ‘Dirty’. • Layout is ‘Dirty’ -> Added to Rebuild Process
- 23. UI Source Code – ‘LayoutGroup.cs’
- 24. UI Source Code – ‘LayoutGroup.cs’
- 25. UI Source Code – ‘LayoutGroup.cs’
- 26. Layout Components • Suggestions: • Enable Layout when needed to be rebuilt. Disable when not needed. • Smaller number of child elements being rebuilt; combine UI elements. • Create own Layout Manager Script; Control ‘when’ Layout is updated. • Object-Pooled Scroll List; Reuse elements as they are scrolled.
- 27. Rebuild Process – Pixel Perfect • When RectTransform’s move, they will snap to exact pixel edges. • Pro: ‘Pixel Perfect’ visuals. • Con: Very expensive for many moving elements.
- 28. Rebuild Process – Animator • ‘Animator’ on UI – for Buttons, Transitions, etc • In ‘Graphic.cs’:
- 29. Sub Canvases • It is possible to add a ‘Canvas’ component to child UI of a Canvas. • This will create a ‘Sub-Canvas’. • Can be used to isolate Canvas rebuilds. • A Sub-Canvas will: - Have its own independent settings (Such as Pixel Perfect) - Rebuild its child batches, when required. - Can enable and disable visibility of all child elements. • Demo Time!
- 30. Unity UI - Source Code bitbucket.org/Unity-Technologies/ui
- 31. Unity UI – Best Practices Guide unity3d.com/learn/tutorials/topics/best-practices