# LogFMOD:Warning: Failed to set initial parameter Direction

**URL:** <https://qa.fmod.com/t/logfmod-failed-to-set-initial-parameter-direction/13494>\
**Category:** Unreal Engine\
**Created:** [October 17, 2017, 12:45am UTC](https://qa.fmod.com/t/logfmod-failed-to-set-initial-parameter-direction/13494 "2017-10-17T00:45:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![AlecB](https://avatars.discourse-cdn.com/v4/letter/a/e9a140/32.png) [@AlecB](https://qa.fmod.com/u/AlecB)\
**Post date:** [October 17, 2017, 12:45am UTC](https://qa.fmod.com/t/logfmod-failed-to-set-initial-parameter-direction/13494/1 "2017-10-17T00:45:13Z")

</div>

We are getting the following warning logged after an upgrade to UE 4.16 + FMOD 1.10:

LogFMOD:Warning: Failed to set initial parameter Direction

The error gets logged each time an event with the built in FMOD ‘Direction’ parameter is triggered.

These have remained unchanged since our 1.09 build, so I am unsure what this message means. Is there a way to define the initial parameter? In FMOD Studio, this value is defaulted to 0.0.

We also make use of the built in ‘Distance’ parameter which is not exhibiting the same warnings…

Let me know if I’ve missed something!

Thanks,  
Alec

---

<div class="post-metadata">

**Author:** ![cameron-fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/cameron-fmod/32/261_2.png) [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)\
**Post date:** [October 19, 2017, 3:25am UTC](https://qa.fmod.com/t/logfmod-failed-to-set-initial-parameter-direction/13494/2 "2017-10-19T03:25:03Z")

</div>

Thanks for reporting this Alec, it is indeed a bug.  
The integration should be ignoring the built in parameters because they don’t get set using setParameterValue().

I will make sure this is fixed for the next release (1.10.01).