Yesterday I updated our FMOD Unity packages and integration from 2.0.8 to 2.1.7 and noticed that something rather annoying has changed.
It would seem that our code compile times have drastically increased as a result of the [InitializeOnLoadMethod] triggering the CleanTemporaryFiles method in the Settings.cs file when significant code change has occurred and Unity recompiles.
Is there a way to safely work around this? What’s the main purpose of this happening each time the InitializeOnLoadMethod is called or can I just remove the [InitializeOnLoadMethod] to not have this slowing everything down as much.
(On a side note, we are working with a rather large project, hence the very noticable freeze when this method is called)