# Step-By-Step Guides

The Workflow intended for the tool is to **test the variables** until you **reach levels that you are confortable with** and **set these values afterwards, evaluating their performance impact if needed using the STAT shortcuts buttons to quickly see the impact they have.**

**These different use-cases examples will help you understand the logic of the tool.**

<details>

<summary><strong>Example 1 - Testing &#x26; setting a new shadow resolution value</strong> <br><em>(Maximum CSM Shadow Map Resolution)</em></summary>

<figure><img src="https://2615682401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs2U3wFj2l65HdsgSwfgM%2Fuploads%2FtAoc3sxysnuDmim62Md2%2Fimage.png?alt=media&#x26;token=3c071269-8c4a-4a60-8d3c-0b1ab91a2a2b" alt=""><figcaption></figcaption></figure>

**For this example, the default values for the MAX Shadow Map Resolution are 512, 1024, 1024, and 2048 from Low to High.**\
But say we wanted to tweak the values so they could be cheaper at the low end without a significant quality loss.

I'll have to first set up an example scene to see what I'm working on, as in the example above.

Then, I can **test** a value by using the **test area, which by default shows the current value in engine.**

As shown by the numbers to the left and right, the recommended values are between **128** and **2048**. **The sliders allow to very quickly try out values, but I can also enter manually my value with the field at the right of the sliders.**

<figure><img src="https://2615682401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs2U3wFj2l65HdsgSwfgM%2Fuploads%2F4gvF9A0BVTDDEuHtPiGR%2Fezgif-74d156b76a3ecf.gif?alt=media&#x26;token=be4d1062-992c-469e-aae9-06d0229e0d41" alt=""><figcaption></figcaption></figure>

***

I tried 32, but I found it too low, even for the **low** shadow preset. I try 64 instead.

<figure><img src="https://2615682401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs2U3wFj2l65HdsgSwfgM%2Fuploads%2FI1VWXWFmE5YqBhbQ2qCo%2Fimage.png?alt=media&#x26;token=7c9063d6-202d-4a4a-8416-60fcbc26da8f" alt=""><figcaption></figcaption></figure>

***

And now say I find the result better for your project, I just have to enter this value in the field of the graphic preset I want to edit.

<figure><img src="https://2615682401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs2U3wFj2l65HdsgSwfgM%2Fuploads%2F1cbzIKWnuBh2CLrGkPfg%2Fimage.png?alt=media&#x26;token=b6f09524-7fad-4d27-ba4f-5001d3f0569d" alt=""><figcaption></figcaption></figure>

Notice that the [**restore button**](https://sylvl.gitbook.io/gpcreator/interface-overview#restore-button) is now **enabled**, meaning that this value has been overriden and will be present when [**exported**](https://sylvl.gitbook.io/gpcreator/using-the-interface/exporting-the-config-file).

<figure><img src="https://2615682401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs2U3wFj2l65HdsgSwfgM%2Fuploads%2FTIHMdNyOTDx6b57hYsaN%2Fimage.png?alt=media&#x26;token=366b9bd8-5d85-4b03-b841-57ec7b36006e" alt=""><figcaption></figcaption></figure>

Say I wanted to test out different resolutions for the other preset to see if they really make a meaningful difference, tweak out the values to increase the performance a bit or increase quality... I just have to do the same for the other values of the preset.

Basically, the workflow is **testing** & **entering the value once satisfied** with its result.

</details>

***

<details>

<summary><strong>Example 2 - Evaluating a performance impact and editing sub-variables</strong><br><em>(Use Volumetric Fog)</em></summary>

**For this example, we have a scene with volumetric fog and we want to see how much performance having it enabled costs and the difference it makes.**

<figure><img src="https://2615682401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs2U3wFj2l65HdsgSwfgM%2Fuploads%2FT9Es6tJhodrimqE9uU6m%2Fezgif-717a9c304bc5b1.gif?alt=media&#x26;token=35374404-1094-47c9-83dd-ea3762621351" alt=""><figcaption></figcaption></figure>

***

Let's say I want to keep it as much as possible, I can quickly test its performance impact with the [**STAT shortcuts buttons**](https://sylvl.gitbook.io/gpcreator/interface-overview#stat-shortcuts)**,** just having to click the one you need to show/hide the STAT.

<figure><img src="https://2615682401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs2U3wFj2l65HdsgSwfgM%2Fuploads%2FYvEWd8kosKTCEJCF8QxJ%2Fezgif-759d82713ba1d1.gif?alt=media&#x26;token=ac46591a-a62b-4dcb-aeef-5c1221de6669" alt=""><figcaption></figcaption></figure>

On the example above, I have 0.35ms taken on a 3090.

If I decide that's light enough to keep it at all presets, I can check the boxes for the Low and Med presets.

But if I want to, I can still edit more settings related to the volumetric fog with the More Setting expandable tab., to make the volumetric fog grid less dense on Low preset for example.

<figure><img src="https://2615682401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs2U3wFj2l65HdsgSwfgM%2Fuploads%2FT3W9dj1PJpn9z4yQsts4%2Fimage.png?alt=media&#x26;token=dd653587-5122-4039-a5dd-0479ea44f5e2" alt=""><figcaption></figcaption></figure>

These sub-variables work the same as their main counterpart, with the testing area, Restore button, and Low to Epic (or Cine) value inputs.

***

<figure><img src="https://2615682401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs2U3wFj2l65HdsgSwfgM%2Fuploads%2Fwa91TgWZ6bxVNfTG30R2%2Fimage.png?alt=media&#x26;token=a0201e60-9b85-4080-a7fc-0989841d30e8" alt=""><figcaption></figcaption></figure>

</details>

The examples above should give you an idea of how to use the tool!

**You should explore the available variables, hover on their top bar to see their description, test out values with scenes that showcase the differences well, evaluate the performance impact using the quick STAT buttons and replaces the values where needed.**&#x20;