Error when importing Fmod in Unity 6000.0.34f1

Unity
1

When I import Fmod in the new Unity 6 version, I instantly errors like:

Assets\Plugins\FMOD\src\EventHandler.cs(2,19): error CS0234: The type or namespace name 'EventSystems' does not exist in the namespace 'UnityEngine' (are you missing an assembly reference?)

I uploaded a screenshot with the rest of the errors:

image
image1474Ă—344 96 KB

I tried installing from the asset store and from the official website, but I get the same errors.

How do I fix this? Is my Unity version too early? Do I have to install something? Thanks in advance.

2

Hi,

Thank you for bringing this to our attention. Unfortunately I was not able to reproduce the behavior. What version of the FMOD integration are you trying to add? Have you disabled and Unity modules on the project?

Thank you for the information

3

Hi there, just to add, I am also getting this series of errors:

image
image1175Ă—254 96 KB

I am using Unity 6000.0.42f1 and FMOD 2.03.06

Here’s a google drive link to an 87MB repro project:
https://drive.google.com/file/d/1TWjLXXf43HC-adDZkzjfM-otNJuQ-H_X/view?usp=sharing

One thing that may have caused this issue is this FMOD package not being able to added to a completely plain Unity Project (as opposed to a project template that the Unity Hub use to create a “new project”).

To create a so called “Plain Unity Project”, create a folder called Assets, and a folder called ProjectSettings and then add that project from disk in the unity hub and open it with your version of choice.

This will give you a de-bloated, blank project, including the bare-minimum of packages. Doing this can be useful if you’re making repros for bugs, or if you just want to be more deliberate about which packages you’re adding to your project.

On the other hand, the “new project” templates add a bunch of optional packages (probably intended to give unity users the best new experience etc). It appears that FMOD relies on one of these optional packages, and doesn’t specify it as a dependency.

If this is the cause of the bug (and not just a 2.03.06 + Unity 6 issue) then the FMOD plugin probably needs to specify that as a dependency.

4

not sure if this is a bit late, but I can confirm adding the “Unity UI package” to the project fixes those specific FMOD errors (and at least for me, FMOD then had no further errors).

1 Like
5

Thank you for the information and sharing the solution. I will make a note to update the integration and it’s dependencies.