Introduction to Optimization with Unity - 2019.3

Diagnosing Performance Problems

Fixing Performance Problems - 2019.3

Challenge - Optimize the Project Scripts

Introduction to Lighting and Rendering - 2019.3

Challenge - Bake the Scene Lighting

Working with Occlusion Culling

Challenge - Configure Occlusion Culling

Live Session Recording - How to Profile and Optimize a Game

LearnLive_OptimizationAssets.zip

In this simple maze game, the player has to navigate through the maze, while avoiding enemy NPCs. The application is experiencing some performance issues, that you will need to address. The optimization routes taken in this project are common throughout many Unity projects and understanding these techniques will allow you to optimize your own projects. 

Optimizing for Performance

d6a3456b-a64d-5841-9c0b-b868f5a92740:zx7pohSEomVRos4yXEp8Oj

Introduction

Preparing for Occlusion Culling

Baking Occlusion Culling Data

Visualizing Overdraw

Conclusion

In this tutorial, you’ll learn to use occlusion culling to optimize rendering and performance of your 3D Unity projects. 

Games

Film

Automotive

VR Curricular Framework Resources

AR Curricular Framework Resources 

Architecture, Engineering and Construction Curricular Framework Resources

In this tutorial, you’ll learn to use Occlusion Culling to optimize rendering and performance of your 3D Unity projects. Occlusion Culling disable GameObjects that are fully hidden (occluded) by other GameObjects. This means CPU and GPU time isn’t wasted rendering objects that will never be seen by the Camera.

Because Occlusion Culling is calculated in a pre-pass, it’s not a good fit for projects where Scene geometry is instantiated or generated at runtime. An ideal use case for Occlusion Culling is a Scene with distinct zones or areas that are hidden from each other by corridors, walls, mountains, or buildings.

1. Identify GameObjects in your Scene that should be considered Static Occluders (GameObjects that can block other GameObjects) and/or Static Occludees (GameObjects that can be blocked by other GameObjects).

Static Occluders have either a Mesh or Terrain Renderer, are opaque, and do not move at runtime. Examples include walls, buildings, and mountains. If using LOD groups with a GameObject designated as a Static Occluder, the base LOD (LOD0) is used in the calculation.

Static Occludees have any type of Renderer and do not move at runtime. Examples include level decor, like shrubs, or any GameObject that is likely to be occluded.

A GameObject can be both. Dynamic GameObjects can be occluded but can’t occlude other GameObjects. 

2. Select all GameObjects that you wish to be Static Occluders. Using the Static Editor Flags drop-down in the upper right, set the Occluder Static property (Figure 01). 

3. Repeat the process for Static Occludees. For GameObjects that are Occluders and Occludees, set both flags. 

4. For each Camera in the Scene, ensure Occlusion Culling is enabled in its Inspector (Figure 02). 

Figure 01: Setting SouthWall to be a Static Occluder

Figure 02: Enabling Occlusion Culling for a Camera

1. To open the Occlusion Culling window, use the Window drop-down and select Rendering > Occlusion Culling. 

2. The Occlusion Culling window has three views: Object, Bake, and Visualization. 

Object view allows you to quickly filter the Hierarchy view to show only relevant GameObjects or Occlusion Areas, as well as create Occlusion Areas (Figure 03). By default, the entire Scene is treated as a global Occlusion Area. Depending on the layout of your Scene, it may make sense to have individual Occlusion Areas. 

Bake view allows the user to set default values for occlusion culling calculation (Figure 04).

Bake view allows the user to set default values for Occlusion Culling calculation (Figure 04).

Smallest Occluder is the minimum size an object should be to be considered a possible occluder.

Smallest Hole is the minimum diameter that’s considered a possible space between occluders. Holes and gaps smaller than this setting are ignored.

Backface Threshold determines the degree to which backfaces are tested and removed. The default value of 100 leaves all backfaces, and the ideal value for this setting will vary from project to project. 

Visualization allows the user to see Camera Volumes, Visibility Lines, and Portals to better understand how the occlusion data is calculated (Figure 05).  

3. Available in all views is the option to Clear or Bake the Occlusion Culling data. 

4. Click Bake. The amount of time it takes to prepare the occlusion data depends on the complexity of your Scene and your Occlusion Culling settings.  

Figure 03: Creating a new Occlusion Area

Figure 04: Setting default parameters for Occlusion Culling

Figure 05: Visualizing the occlusion data based on the selected Camera

The 3D rendering process in 3D starts with the geometry farthest from the camera. This is known as Overdraw. In the Scene view, the user can enable Overdraw mode to visualize this (Figure 06).  

Figure 06: Visualizing Overdraw

Occlusion Culling is an easy way to optimize performance by limiting rendering to only GameObjects in Camera view. With this being just one way to optimize performance, check out our Optimizing for Performance project to learn about additional ways that you can optimize your project. 

Working with Occlusion Culling

1. Introduction

2. Preparing for Occlusion Culling

3. Baking Occlusion Culling Data

4. Visualizing Overdraw

5. Conclusion

Complete this tutorial