FMOD.log keeps checking in ignored files in Unity PlasticSCM Source Control

[randall.c]

Hi

my other collaborators on my Unity PlasticSCM source control project have been facing the following issue:

I've already ignored the files FMOD has suggested in the documentation in my ignore.conf file but it still insists on being tracked and checked in.

Here’s the ignore.conf file::
#Common directories
Library
library
Temp
temp
Obj
obj
Build
build
Builds
builds
UserSettings
usersettings
MemoryCaptures
memorycaptures
Logs
logs
**/Assets/AssetStoreTools
**/assets/assetstoretools
*/Assets/AddressableAssetsData//.bin
*/assets/addressableassetsdata//.bin
**/Assets/StreamingAssets/aa.meta
**/assets/streamingassets//aa/
.collabignore
Builds

*.apk
*.unitypackage

#Plastic SCM related
/ignore.conf
.private
.private.meta
^.private.[0-9]+$
^.private.[0-9]+.meta$
Gradle cache directory

.gradle
Autogenerated project files

/Assets/Plugins/Editor/JetBrains*
/assets/Plugins/Editor/JetBrains*
.vs
ExportedObj
.consulo
*.csproj
*.unityproj
*.sln
*.suo
*.tmp
*.user
*.userprefs
*.pidb
*.booproj
*.svd
*.pdb
*.mdb
*.opendb
*.VC.db
Unity3D generated meta files

*.pidb.meta
*.pdb.meta
*.mdb.meta
Unity3D Generated File On Crash Reports

sysinfo.txt
Crashlytics generated file

crashlytics-build.properties

#Mac
.DS_Store*
Thumbs.db
Desktop.ini
Never ignore DLLs in the FMOD subfolder.

!/Assets/Plugins/FMOD/**/lib/*
Don’t ignore images and gizmos used by FMOD in the Unity Editor.

!/Assets/Gizmos/FMOD/*
!/Assets/Editor Default Resources/FMOD/*
Ignore the Cache folder since it is updated locally.

/Assets/Plugins/FMOD/Cache/*
Ignore bank files in the StreamingAssets folder.

/Assets/StreamingAssets//*.bank
/Assets/StreamingAssets//*.bank.meta
If the source bank files are kept outside of the StreamingAssets folder then these can be ignored.
Log files can be ignored.

fmod_editor.log

First time Unity-PlasticSCM user and really pulling my hair out on this one. Any help is greatly appreciated.

 

Really pulling my hair out on this one. Any help is greatly appreciated.

[randall.c]

Not sure if this matters, but FMOD was integrated after the very first initial check-in.

[ollieblanks]

Sorry for the delay in response!

ignore.conf, only works on private files. It sounds like the log file has been previously checked in and inherently tracked by source control.

To make this file private again. Manually delete the file from the workspace and then check-in the deletion, this will mean that the file is now private and will adhere to ignore.conf rules.

Hope this helps!