# Global parameter doesn't change outside Studio

**URL:** <https://qa.fmod.com/t/global-parameter-doesnt-change-outside-studio/18703>\
**Category:** Unity\
**Created:** [April 26, 2022, 11:48am UTC](https://qa.fmod.com/t/global-parameter-doesnt-change-outside-studio/18703 "2022-04-26T11:48:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sevenwordsmusic](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/sevenwordsmusic/32/3480_2.png) [@sevenwordsmusic](https://qa.fmod.com/u/sevenwordsmusic)\
**Post date:** [April 26, 2022, 11:48am UTC](https://qa.fmod.com/t/global-parameter-doesnt-change-outside-studio/18703/1 "2022-04-26T11:48:16Z")

</div>

I’ve tried to automate a parameter in a Timeline Event using Command Instruments,  
“Stinger” automates 0/1, curve, “Window” false/true.

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/0/08800b07ecd49c6a833e0f9a16e260a9dccfc067.png)

Via Unity shows always the initialized value whatever it is.

```auto
FMODUnity.RuntimeManager.StudioSystem.getParameterByName("Window", out float window);

```

At first I’ve tried to directly automate “Window”; in that case “Window” doesn’t even change inside FMOD Studio Event, only an orange dot appears.  
This way at least I’m able to see that inside Studio “Window” switches false/true.

---

<div class="post-metadata">

**Author:** ![jeff\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/jeff_fmod/32/1766_2.png) [@jeff\_fmod](https://qa.fmod.com/u/jeff_fmod)\
**Post date:** [April 29, 2022, 5:20am UTC](https://qa.fmod.com/t/global-parameter-doesnt-change-outside-studio/18703/2 "2022-04-29T05:20:51Z")

</div>

It looks like you need to use the second overload of [`Studio.System.getParameterByName`](https://fmod.com/resources/documentation-api?version=2.02&page=studio-api-system.html#studio_system_getparameterbyname) to get the `finalvalue`, I have verified this is being updated correctly when setting parameters with command instruments. The `value` parameter somewhat confusingly only tells you the parameter that has been set using calls to `setParameterByName`, `setParameterByID` etc.