Event Browser Bug - No Events

Hey guys,

This has happened since around 1.06 (the earliest version I worked with) - I just never got around to reporting it.

Sometimes the events (and snapshots etc) disappear from the event browser within Unity. After a bit of fiddling, I found the only way to get them to come back was to temporarily select a different path type (as in single or multi-platform), then re-select the correct type. This seems to ‘refresh’ the events and works 95% of the time.

However, I am unable to reproduce the issue in the first place - it just seems to happen whenever. I am currently working with two totally separate developers and they have both also had this problem on more than a few occasions. And the solution that I discovered worked for them too.

Is this a known issue? Anyone else came across this? It’s obviously not a dev-breaking problem but it is a massive nuisance.

Thanks for reading,

Damion.

Most likely cause is the integration detecting file modifications (either exporting in the tool or syncing from source control) and trying to build the event list from files that are still being written.

We made this more robust in 1.07.07 so if you’re still seeing it in later builds let me know.

It’s definitely still happening at 1.08.

Cheers for your response!

I was working on a different machine and discovered it’s still too eager loading files from big projects or on slower machines. I’ll increase the delays in 1.08.10.

This is happening for me using Fmod 2.00 on Unity 2019.1.12f1. The workaround of temporarily selecting multi-platform, giving it a moment to try and fail, and then switching back.

Any updates on this? This still happens to me quite often when pulling FMOD project changes from our sound designer and then looking for those new events in Unity. None of the suggested workarounds seem to work for me either.

I’m on integration version 2.00.03 and Unity version 2019.1.8f1

Probably best to start a new thread and link back to this if needed, as this thread is quite old now.

Also check the console log for any errors or warnings related to FMOD.