Unity\u2019s profiling best practices guide<\/a>\u00a0is a great place to start, which includes a handy flowchart that provides guidance on the often mysterious process of profiling.<\/p>\n\u201cI have to do a lot of profiling,\u201d says Liam. \u201cI can tell when the CPU is doing a lot, and the GPU isn’t, and vice versa. Really, our worst bottleneck has been both of them at different times.\u201d<\/p>\n
We included a slew of our favorite resources at the end of this post to help you on your own profiling journey.<\/p>\n
And with that disclaimer out of the way, let\u2019s explore optimizations.<\/p>\n
Simplifying and culling<\/h2>\n
When rendering, we need to determine which meshes to render and where.<\/p>\n
The more meshes we have and the more draw calls we need, the more the CPU has to keep figuring out what to do while the GPU waits for its next job.<\/p>\n
We could speed up the process by rendering fewer meshes. For example, you could swap complex meshes with imposters, billboards, or low-poly versions; or you could break up a sprawling world into smaller levels with less to render at once. These are tried-and-true solutions you should use when you can, but they limit the level of detail in your environments.<\/p>\n
One optimization that avoids this, and is simple to implement, is occlusion culling, where the camera checks what\u2019s within its field of view and avoids rendering what the player can\u2019t see. This saves time at the cost of increased memory usage, but it\u2019s often worth it in environments with many stationary meshes, like detailed rooms in an office building. This optimization is an industry standard, but it\u2019s often not enough on its own.<\/p>\n
Static batching<\/h2>\n
Another way we can limit the number of meshes we render without sacrificing variety is by combining them into a single mesh.<\/p>\n
You can do this yourself manually. Or, so long as the meshes share the same material, Unity can do this for you in a process called batching. Set a game object to static, and Unity will automatically batch all of the meshes with the same material together to cut down the draw calls. Use this option on anything that stays static, like trees and walls.<\/p>\n
This drastically reduces RAM usage and CPU overhead, allowing the GPU to render more content at once. But keep in mind, more GPU memory will be used to store the combined meshes.<\/p>\n
Static batching is often our #1 key optimization process, particularly for Backyard Baseball<\/em>. Using URP\u2019s batching system is simple, so the most challenging part is figuring out how to use as few materials as possible across as many models as possible. That balancing act is why we have some of the most creative cats on our optimization and art teams.<\/p>\nGPU instancing<\/h2>\n
This is a good time to start distinguishing between a thing\u2026 versus an instance of that thing.<\/p>\n
Let\u2019s say you have a mesh. A mesh is an asset. And its material is an asset. They are single files that exist in your file structure. For every object with a 3D appearance in your game, a mesh describes its shape, and then a material describes how its surface looks.<\/p>\n
But because Unity simplifies its details, some developers don\u2019t realize that when their game is running, they actually have multiple copies of these things instantiated into their game world. When your player explores a forest, they\u2019re moving through many copies of that one tree stored as an asset in their game\u2019s files.<\/p>\n
This is why we used GPU instancing for the foliage in Backyard Baseball<\/em>. Instead of rendering each copy of the tree with unique calls to the GPU, the CPU instead asks the GPU to render all identical models at once. If you\u2019re not careful, this could result in every tree in the forest looking identical. But, with some effective parameters in the material\u2019s shader, for example, a value to customize the color of the leaves, you can pass to the GPU one model and material, along with the unique colors for each tree, rather than asking for each tree individually.<\/p>\n<\/div>\n
\n
Source link <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"Investigate what\u2019s causing rendering issues and then optimize Rendering is a collaboration between your CPU…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1018","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/x.sheep-mine.ts.net\/index.php\/wp-json\/wp\/v2\/posts\/1018","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/x.sheep-mine.ts.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/x.sheep-mine.ts.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/x.sheep-mine.ts.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/x.sheep-mine.ts.net\/index.php\/wp-json\/wp\/v2\/comments?post=1018"}],"version-history":[{"count":0,"href":"https:\/\/x.sheep-mine.ts.net\/index.php\/wp-json\/wp\/v2\/posts\/1018\/revisions"}],"wp:attachment":[{"href":"https:\/\/x.sheep-mine.ts.net\/index.php\/wp-json\/wp\/v2\/media?parent=1018"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/x.sheep-mine.ts.net\/index.php\/wp-json\/wp\/v2\/categories?post=1018"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/x.sheep-mine.ts.net\/index.php\/wp-json\/wp\/v2\/tags?post=1018"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}