> For the complete documentation index, see [llms.txt](https://teogames.gitbook.io/dynamic-mesh-combiner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://teogames.gitbook.io/dynamic-mesh-combiner/components/profile.md).

# Profile

To profile various metrics and track the performance impact of mesh combining, you can use the profiling feature. Follow these steps to set up and enable profiling:

1. Open the profile modules settings: In the Unity Editor, navigate to "Window" > "Analysis" > "Profiler" to open the Profiler window. Then, click on the gear icon in the Profiler window toolbar to access the settings:&#x20;

   <figure><img src="/files/4k2RDUtkqJ6YXsWwNq9I" alt="" width="155"><figcaption></figcaption></figure>
2. Add the MC metrics module: In the Profiler settings, click the "Add" button to add a new module. Search for "MC metrics" in the module list and select it:

   <figure><img src="/files/QViuDgKQC4mU33Rt4rE3" alt="" width="375"><figcaption></figcaption></figure>
3. Save the profile settings: Click the "Save" button to save the profile settings with the added MC metrics module.
4. Enter Play mode: To start the profiling, enter Play mode by clicking the Play button in the Unity Editor toolbar or by using the shortcut Ctrl + P:

   <figure><img src="/files/E2s3Pq2ecb3dtRPKvy5C" alt="" width="375"><figcaption></figcaption></figure>

During Play mode, the Profiler window will display the performance metrics related to mesh combining, allowing you to analyze the impact on CPU usage, rendering, and other relevant metrics.

{% hint style="info" %}
The provided screenshots are for illustrative purposes only. The actual appearance of the Profiler window and settings may vary based on your Unity Editor version and configuration.
{% endhint %}

By using the profiling feature, you can gain insights into the performance characteristics of mesh combining and optimize your project accordingly. Analyzing the metrics can help you identify potential bottlenecks, optimize your resource usage, and achieve optimal performance in your Unity project.

## Disable profiler

If you prefer to disable the profiler feature, there are a few scenarios where you might want to do so. For example, you may not want to include dependent packages.

To disable the profiler, you can add a scripting define symbol named `DISABLE_PROFILE`. This can be done in the Unity Editor by following these steps:

1. Open the Unity Editor.
2. Go to "Edit" → "Project Settings" → "Player".
3. In the "Player Settings" inspector, scroll down to the "Other Settings" section.
4. In the "Scripting Define Symbols" field, add `DISABLE_PROFILE` as a new symbol.

Adding this define symbol will disable the profiler functionality, allowing you to exclude the dependent packages or work with older Unity versions without any profiler-related features.

<figure><img src="/files/8M0IaGJMkEDmN3uvL4RH" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://teogames.gitbook.io/dynamic-mesh-combiner/components/profile.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
