Perforce source control integration

[flyinglyon]

I see Perforce listed in Options/Source Control/Add - but
picking it seems to do nothing... What does choosing a source control provider do? What do the directory associations do? Is there any documentation on this?

[Craig]

All of the documentation we have is in the new Welcome post (http://www.scootersoftware.com/ubbthreads/showflat.php?Cat=0&Number=5603) and the SCC Version Control Information (http://www.scootersoftware.com/support.php?c=kb_scc.php) knowledge base article. Let us know if you need any help past that or if there's anything special you need to do that other users should be aware of.

[kevinsikes]

Make sure P4PORT, P4CLIENT, P4USER, and P4PASSWD environment variables are set. The directory you specify to BC2 must be in the client view. For instance, if your depot root maps to c:\perforce, but your client view only maps individual projects, then you can't add c:\perforce in BC2's source control. Instead you have to add individual projects such as c:\perforce\foo, c:\perforce\bar, etc.