Version control documentation needs to be improved

As I’m a freelancer, I’m usually the one hooking up middleware to projects, and every time I do, it never seems to integrate correctly across version control; it will work perfectly on my end, but on the client’s end, there are a host of errors, usually relating to missing files, and I don’t understand why it ends up being an easter egg hunt every single time. If I integrate it, then push it, why isn’t everything contained in the Unity project folder?

I’ve routed the banks to be in that folder, but there are core integration files missing on the client’s end (they specifically mentioned “com.unity.fmod”), which shouldn’t be happening. All documentation seems to assume that all files will be on the same machine, including FMOD Studio, but client shouldn’t need all the FMOD Studio files to get it working. This whole process is incredibly frustrating, and adequate documentation would help immensely.

I’m not sure what “com.unity.fmod” is referring to, possibly a package that is kept outside of the Unity Project but it’s not something in our integration.

How are you importing the integration into your project? Through the UPM (Unity Package Manager) or from our website?

If it is through the UPM it will need to be added to either the project or to the package manifest in the project, this way it knows the packages required by the project.

Otherwise the integration files will be inside the project directory and will need to be added to source control.

Can you confirm where the integration files are on disk?