Unity integration version shows 0.00.00

Unity
1

I’ve got FMOD Unity integration and FMOD Studio 2.01.01 installed, but I’m getting version mismatch errors. I checked FMOD > About in Unity and it shows 0.00.00. I tried reinstalling both FMOD Studio and the integration in Unity with no change. Not sure how to debug this further, any ideas?

2

Which version of the FMOD Studio unity integration are you using? And which version of Unity?

3

I’m using Unity 2020.1.2 and FMOD 2.01.01 both with the integration and studio. However, this morning I again tried uninstalling and reinstalling everything and it is finally working this time. Not sure what I did differently this time unfortunately.

4

I’m glad to hear you were able to get it working.

I’ll continue trying to reproduce the issue here.

5

So I have seen this problem occur a couple of times recently. I think I should post a info dump here in the hopes of maybe preventing this problem from occuring in the future.

After pulling switching a branch and pulling from GitHub, a unity 6000.054 / FMOD 2.03.06 project started throwing errors and the integration version in unity states that it is 0.00.00.

I tried deleting the local rep and recloning and that did not help.

I tried deleting the FMOD folder inside the plugins folder in unity and that did not help either.

I tried deleting and rebuilding the FMOD banks - still not working.

I of course closed and reopened both FMOD and unity multiple times - still broken

Finally I restarted my computuer (running windows 10) and hurray - everything works again.

In hindsight I wish I had performed my solution steps in reverse - perhaps a simple restart would have fixed the issue?

Hope this info is helpful to someone - FMOD folks, please let me know if there is anything specific I should look for the next time I encounter this issue - I teach at a school and always have lots of projects going on. I’m sure this problem will occur again. I’d like to help fix this issue.

6

Thanks for the information. I’ve yet to reproduce the issue here, but knowing that a simple restart may be enough to fix it might help narrow it down - and more importantly, might be of great help to other people who encounter the problem.