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

**URL:** <https://qa.fmod.com/t/fmod-log-keeps-checking-in-ignored-files-in-unity-plasticscm-source-control/19359>\
**Category:** Unity\
**Tags:** unity\
**Created:** [October 4, 2022, 5:07am UTC](https://qa.fmod.com/t/fmod-log-keeps-checking-in-ignored-files-in-unity-plasticscm-source-control/19359 "2022-10-04T05:07:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![R4N4W4Y](https://avatars.discourse-cdn.com/v4/letter/r/49beb7/32.png) [@R4N4W4Y](https://qa.fmod.com/u/R4N4W4Y)\
**Post date:** [October 4, 2022, 5:07am UTC](https://qa.fmod.com/t/fmod-log-keeps-checking-in-ignored-files-in-unity-plasticscm-source-control/19359/1 "2022-10-04T05:07:08Z")

</div>

Hi

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

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/5/502b599e0ec81525f7c0635b6bacf3813ad7b1f8.png)

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.

---

<div class="post-metadata">

**Author:** ![R4N4W4Y](https://avatars.discourse-cdn.com/v4/letter/r/49beb7/32.png) [@R4N4W4Y](https://qa.fmod.com/u/R4N4W4Y)\
**Post date:** [October 4, 2022, 5:09am UTC](https://qa.fmod.com/t/fmod-log-keeps-checking-in-ignored-files-in-unity-plasticscm-source-control/19359/2 "2022-10-04T05:09:37Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\
**Post date:** [October 11, 2022, 12:04am UTC](https://qa.fmod.com/t/fmod-log-keeps-checking-in-ignored-files-in-unity-plasticscm-source-control/19359/3 "2022-10-11T00:04:46Z")

</div>

Hi,

Did you have the `ignore.conf` file set up before FMOD was checked-in or was it added after?

If a file is already under version control the `ignore.conf` file won’t work.

An option is deleting the file in Plastic SCM and checking in the deletion. This will stop the file from being tracked and remove it from your repo. Run Unity again, which will create a new `.log` file on your disk but it should now be ignored. Once it has been successfully ignored have all your collaborators update their workspaces with the file removed.

Hope this helps.