Project building/compiling suddenly fails due to FMOD binaries issues

We’ve been using FMOD for quite a while, plugin version 1.08. No issues what so ever, can compile, package and play the game. Then suddenly tonight everything is going wrong. Neither the engine nor the plugin were updated or changed prior to that.

Symptoms:

  1. First, I tried packaging development build as usual. In-editor build was successful, but starting the game.exe led to this error:

We have not added any reference to FMOD in code, we only use it in BPs except for one code pre-load that was added weeks ago and worked fine.

  1. I then tried building the development again, thinking something went wrong. The exactly same build failed this time with following errors: http:///2uRfpXaj

  2. Lastly I decided to try deleting all binaries in project/plugin folder, re-generating project VS files and recompile it through Visual Studio. Rebuilding the game project in VS now gives this error:

Nothing works any longer, although I can still play game in edtor, and for some reason compile project in debug config but not development. Any ideas what on earth went wrong there?

Hello Araklaj,

I’ve never seen this particular problem before but it does definitely seem like a problem where the plugin is having issues compiling. Have you checked for the file that is mentioned in that first error listed in your picture? fmodL64_vc.lib

First just check if it exists, if it does, be sure that it isn’t set to read-only. Also, check the output log itself in Visual Studio to see if there may be more details about these errors or what’s going wrong in the compilation process.

Hi Matthew. The file does exist and wasn’t set to read-only. We were unable to solve this issue, so I just started going through revisions of source C++ files. All of them, including newest one worked.

Still no idea what happened there as I previously pulled latest versions multiple times, but it seems to be working again. Sometimes, it’s like FMOD is running on black magic or something…

We were unable to solve this issue, so I just started going through revisions of source C++ files. All of them, including newest one worked. Still no idea what happened there as I previously pulled latest versions multiple times, but it seems to be working again.