Watcher warnings and weird path issues in 6.2.3f1

These issues weren’t happing on 6.2.2f1. Now I get a lot of spam:

Error watching /home/brandon/deadmoney/hommlet/Library/PackageCache/com.unity.inputsystem@be6c4fd0abf5/InputSystem/Editor/FMod/AOR/Build/Desktop: The directory name ‘/home/brandon/deadmoney/hommlet/Library/PackageCache/com.unity.inputsystem@be6c4fd0abf5/InputSystem/Editor/FMod/AOR/Build/Desktop’ does not exist.
Parameter name: Path
UnityEngine.Debug:LogWarningFormat (string,object)
FMODUnity.RuntimeUtils:DebugLogWarningFormat (string,object) (at Assets/Plugins/FMOD/src/RuntimeUtils.cs:588)
FMODUnity.BankRefresher:UpdateFileWatcherPath () (at Assets/Plugins/FMOD/src/Editor/BankRefresher.cs:81)
FMODUnity.BankRefresher:Update () (at Assets/Plugins/FMOD/src/Editor/BankRefresher.cs:44)
UnityEditor.EditorApplication:Internal_CallUpdateFunctions () (at /home/bokken/build/output/unity/unity/Editor/Mono/EditorApplication.cs:384)

In addition, I sometimes get very catastrophic build errors saying my project working directory has changed to some random directory inside FMOD.

This looks to me like relative paths aren’t being handled correctly in EditorUtils.cs and if Unity internally changed how the CWD is set, this seems like risky code? (lines 90-115).

Hi,

Thank you for sharing the information.

I was not able to reproduce the warnings on my end in 6.2.3f1.

Could I please grab more info:

  • What version of FMOD Unity integration you’re using?
  • Could you please elaborate more on the reproduction steps?

I’m currently on Unity 6000.2.4f1 using FMod for Unity 2.03.08. I’m on Linux (Ubuntu).

My source type is set to “Single Platform Build” and the Build Path is “FMod/AOR/Build/Desktop”

We keep our fmod banks in source control, but outside of the Assets directory, so that path is relative to the base Unity project folder. This worked up and until Unity 6000.2.3f1 when we started to see the path being appended in weird ways. See below where the path is appended to an unrelated path. I don’t know where that’s coming from. As far as I can tell, nothing else changed that would cause this kind of behavior.

I’m not convinced this is an fmod issue, exactly, but haven’t been able to find anything in Unity’s changelists that suggested something with path resolution changed. I’ve seen other plugins act similarly oddly. I’m on Linux, so maybe there’s some issue with that platform, but its not just on my dev machine, but other dev’s machines (also linux) with the same issue).

Error watching /home/brandon/deadmoney/hommlet/Library/PackageCache/com.unity.2d.tilemap.extras@2338d989ff2a/FMod/AOR/Build/Desktop: The directory name ‘/home/brandon/deadmoney/hommlet/Library/PackageCache/com.unity.2d.tilemap.extras@2338d989ff2a/FMod/AOR/Build/Desktop’ does not exist.
Parameter name: Path
UnityEngine.Debug:LogWarningFormat (string,object)
FMODUnity.RuntimeUtils:DebugLogWarningFormat (string,object) (at Assets/Plugins/FMOD/src/RuntimeUtils.cs:588)
FMODUnity.BankRefresher:UpdateFileWatcherPath () (at Assets/Plugins/FMOD/src/Editor/BankRefresher.cs:81)
FMODUnity.BankRefresher:Update () (at Assets/Plugins/FMOD/src/Editor/BankRefresher.cs:44)
UnityEditor.EditorApplication:Internal_CallUpdateFunctions () (at /home/bokken/build/output/unity/unity/Editor/Mono/EditorApplication.cs:384)

I figured out the problem. Unity installed the collab package by default. This is the package that drives unity’s source control interface. This package will appear on Linux even though it isn’t supported. It seems to instrument a large number of file system interactions, maybe to check if files should be checked out in source control (plastic). Around the same time that 6.2.3 came out, this package also got updated. In that update, it completely broke on linux and was causing these problems. I had ignored the package in the past, but disabling it resolved the problems.

1 Like

Thank you for sharing the solution here!