Hello,
After upgrading to FMOD Studio and Unity integration version 2.03 I still encounter the known issue of calling eventinstance.stop() AHDSR not honoring the release/fade out specification. In my case, i.stop(STOP_MODE.ALLOWFADEOUT); and i.stop(STOP_MODE.IMMEDIATE) sound identical in engine.
the attack, on the other hand, works as intended. Am I missing something or is this issue still ongoing ?
thank you in advance
I don’t believe this is a known issue at the moment.
Which versions of FMOD Studio and the integration are you using?
Are you seeing any errors or warnings in the logs at all?
Hello! I believe I’m also experiencing this issue. I have an event with an AHDSR modulator. The event is called and stopped via a script using StopMode.ALLOWFADEOUT, and while it has a 2s decay in the FMOD editor the decay doesn’t appear at all in Unity.
I’m on version 2.02.33 (both Studio and integration). Not seeing any errors or warnings in the console with logging set to max.
(Apologies for resurrecting this thread, let me know if I should start a fresh one)
EDIT: My bad, the issue was entirely on my end. I simply had two events with similar names and sounds. One had AHDSR correctly applied, one didn’t. I was adjusting one in FMOD Studio and had the other one assigned in-engine. Sorry for the trouble!