Perforce (or other content management) best practices?

I’ve got a Perforce server set up at home for my project. I’m the only one working on it and it’s pretty light weight so easy to manage/maintain. At the moment I have the entire project folder under source control and that’s it. Since I don’t do anything besides Blueprints I don’t feel the need to keep the rest of the game files there. For the most part this is working out fine for me. However, with 4.4 I have started testing iOS from my PC and noticed that I can’t build to my devices unless I have the entire project checked out. I’m assuming there is a file somewhere that is being written to, but I have no idea what it is so I have to check out everything and then revert unchanged before checking in changes.

So, does anyone know what files are not necessary to have under source control? I see that config files don’t save editor settings like window configs and filter settings don’t warn if they aren’t able to write so I have those checked out permanently in a separate changelist. For the build to device issue I didn’t see any file that was changed so I’m unsure what the best set of files to keep under source control is.

Any help would be appreciated.

I exclude Build, Intermediate and Saved folders, or rather just don’t check them in. I also have .p4ignore.txt file that looks like this:


.p4ignore.txt
!*.*
*.sln
Intermediate

Though I don’t quite remember why to be honest.