# Changing input of Fmod material node crashes while saving

**URL:** <https://forums.unrealengine.com/t/changing-input-of-fmod-material-node-crashes-while-saving/322944>\
**Category:** Rendering\
**Tags:** node, fmod, unreal-engine, saving, question\
**Created:** [June 24, 2015, 11:59pm UTC](https://forums.unrealengine.com/t/changing-input-of-fmod-material-node-crashes-while-saving/322944 "2015-06-24T23:59:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Xkonti](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Xkonti](https://forums.unrealengine.com/u/Xkonti)\
**Post date:** [June 24, 2015, 11:59pm UTC](https://forums.unrealengine.com/t/changing-input-of-fmod-material-node-crashes-while-saving/322944/1 "2015-06-24T23:59:40Z")

</div>

Branch: Binary

Build version: 4.8.1

Material file (zipped:) [M\_Base\_Simple.uasset][1]

When I change second input of FMod node, shader will compile, but when I try to save material, editor stays on 50% forever and is totally unresponsive. My material looks like this:

 ![47747-bug1.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/4/4/24450edc0e0606cde6fd36e4911a9573a59d73c7.png)

To be specific it is about this FMod node:

![47748-bug.gif](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/e/c/2ec679b00ff55b06ee6600030a92739cdf7f81ac.gif)

As you can see I tried to convert into constant. It was my goal because I dont need it as parameter. The same happens if I just create new constant and connect it to FMod node. Duplicating material does not help.

---

<div class="post-metadata">

**Author:** ![Lovecraft\_K](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Lovecraft\_K](https://forums.unrealengine.com/u/Lovecraft_K)\
**Post date:** [June 25, 2015, 6:55pm UTC](https://forums.unrealengine.com/t/changing-input-of-fmod-material-node-crashes-while-saving/322944/2 "2015-06-25T18:55:48Z")

</div>

Hi Xkonti -

Thank you for your report. I have been able to reproduce the freezing issue internally and have reported the bug as UE-17714. I will keep you informed here as we investigate a solution to this issue.

Thank You Again -

Eric Ketchum
