Stopping event stops all events with same path

[Lemior]

Hi,

i currently have a problem with stopping my event.
I noticed when two vehicles have the same engine sound and i stop one because its too far away my own engine sound stops too.

when i use two different vehicles with different engine sounds this does not happen.

It only happens when the fmod path of the event reference is the same.

I checked the instance handles of the events but they are different.

The function call order is:

1. data.Instance = RuntimeManager.CreateInstance(data.DataStorage.FMODPath);
2. data.Instance.start();
3. data.Instance.release();
4. x seconds later
5. data.Instance.stop(STOP_MODE.ALLOWFADEOUT);

After the fadeout is done my sounds disappear.

Thank you for your help

Edit 1: an update from 2.02.26 to 2.0.2.28 fixed it

Edit 2: it appeared again after more testing. i dont know whats going on

[li_fmod]

Hi Lemior,

Thank you for sharing the information and code snippet.

@Lemior

I noticed when two vehicles have the same engine sound and i stop one because its too far away my own engine sound stops too.

when i use two different vehicles with different engine sounds this does not happen.

Could you please check if your event is marked as persistent in FMOD Studio?

Persistent events remain active even when they aren’t producing sound, which could lead to overlapping behaviors like the one you’re experiencing.

Additionally, are you using any parameters in this event?

If possible, could you please share a screenshot of how the event is set up in FMOD Studio? This would help me better understand the structure and identify any potential issues.

[Lemior]

Hey,

thanks for the reply.

its not marked as persistent.

i have a lot of parameters for rpm engine load etc.

[ah_dzinski]

Hello, I work with @Lemior and found the source of the problem. It’s the Command Instrument that send Stop Event - Immediate targeted at this event.
I thought that it would double-proof dumping the event from game’s memory, but it kills every instance of that event - that was the problem.

[li_fmod]

Hi,

Thank you for sharing the solution here.

@ah_dzinski

It’s the Command Instrument that send Stop Event - Immediate targeted at this event.
I thought that it would double-proof dumping the event from game’s memory, but it kills every instance of that event - that was the problem.

Yes, using a Command Instrument with the Stop Event - Immediate command targeting a specific event will stop all instances of that event, not just the one intended.

Instead of stopping the event directly, you could consider using parameters to fade out sounds based on distance. This way, you avoid globally affecting all instances while still managing the sound cleanly.