Events went missing after saving

FMOD Studio
1

Hi,

I am using Sonoma 14.2.1 in my Mack Book. I am using the latest FMOD.

I created Events, created a sheet, an audio track, loaded the audio unto the track, assign the Event to a bank, made the necessary adjustment in the audio track then SAVED and then move on to create another Event. I think I did about 30 Events. I saved each time I created an Event. I closed FMOD and worked on something else and re-opened it when I wanted to add more files. But all the Events were gone. The Assets and the Bank was there, but the Events were all gone. Not once, but twice this happened. One with the latest version and with the version before.

Can I know why is this happening?

2

Unfortunately, I haven’t been able to reproduce the issue on my end on Sonoma 14.1.1 using 2.03.00 and 2.02.21.

Are you using source control with your project, either an internal FMOD Studio integration, or an external solution? Additionally, what destination were you saving to? Other Mac users have reported that saving to a project located in iCloud folder can cause saved changes being deleted - if this is the case with you too, I would recommend saving your project elsewhere and seeing whether that resolves the issue.

3

I’ve been having this exact problem on Sonoma 14.5 and found that creating FMOD Studio files in a location that isn’t automatically uploaded to iCloud fixed it!

Weirdly, the events would disappear after saving and reopening the file in FMOD Studio but were visible in Unity using FMOD for Unity, and the nonexistent events would even be visible and function as expected in game.

Regardless, thanks Leah.

1 Like
4

No problem, happy to hear you resolved the issue!

5

I’ve just discovered this issue too; my assets are there but the events have disappeared. I will the suggestions listed in this thread, but FMOD might want to investigate this issue further.

6

Yes, that worked for me too, thanks libby! :pray:

1 Like
7

Glad to hear you were able to work around it - I’ve noted your interest in a fix on our internal improvement tracker.

1 Like
8

Resurrecting an old thread. If you’re using iCloud Desktop, Apple’s versioning going on behind the scenes is clearly conflicting with fmod’s pointers for file access in one form or another.

Adding “.nosync” to the name of a folder will selectively stop iCloud from tracking it. For example, a folder named “FMOD” will become “FMOD.nosync”, and that will solve the problem for that folder’s contents.

2 Likes